The problem
You have accidentally run a chown -R / or a chmod -R / instead of specifying the good path.
The proper way, in this case should be to restore your backup, but i know some of you doesn’t have made backup…
A kind of solution
- reinstall a yunohost B on the same architecture with the same app and same user created in the same order
- use getacl to backup permission from this new server B
getfacl -R / > permissions_backup
- If you have just change owner, and have access to a shell on the broken server A, restore permissions
setfacl --restore=permissions_backup /
- If you have not access in shell, you can mount the disk of your yunohost (for example in rescue mode, or using an iso), next go on your mounted path and apply permission
cd /mnt/disk
setfacl --restore=/root/permissions_backup .
It’s not tested, i wrote this to help an ARN member, but you can try this.
After that your server should be “better”. But, it’s not a super solution cause you can have some files in server A not existing in your new server B…
To repair a bit better, you could try to make backup, and force the upgrade of your apps:
yunohost app upgrade -F nextcloud
After what, you should search for files in you system with the wrong user (or permission), maybe you could repair it manually…
At this step trying to make backup and restore it on a fresh yunohost, could be a good idea.