@nebulon Unfortunately that's not the case. I had fixed that file myself after I accidentally deleted it with the wrong understanding, recreating the file and filling in the content by grabbing it directly from the git.cloudron.io repository for the /etc/sudoers.d/yellowtent file and that file was apparently last edited quite a while ago, nothing recently changed to it. There was also no Cloudron update during my testing time as this was all the same day. The file btw I grabbed the contents from is this one: https://git.cloudron.io/cloudron/box/-/blob/master/setup/start/sudoers
I wonder if it'd be reproducible by setting up a fresh instance again with the same setup, because that's essentially what occurred for me and it only seemed to be fixed after editing the sudoers.d/yellowtent file. Not sure if a coincidence though or something different. Perhaps there was a discrepancy between what Cloudron setup versus what's in the Cloudron git directory?
Here is the exact steps I took to get to that issue before which seems to no longer be impacting me:
Setup a new public cloud instance at OVH
Create a block storage disk and attach it to the public instance created in step 1
Format the block storage disk and mount it according to this article: https://docs.ovh.com/ca/en/public-cloud/create_and_configure_an_additional_disk_on_an_instance/#using-linux
Install and restore Cloudron from old server via DigitalOcean Spaces latest Cloudron backup ID
Once Cloudron is running off latest backup, change backup configuration to file system using rsync non-encrypted with hardlinks, then initiate the first backup to the new location. This is where it failed for me.
In addition to the steps above, I then tried adding the yellowtent user to have sudo privileges by running sudo usermod -aG sudo yellowtent however this did not work, so I then created a file in /etc/sudoers.d/yellowtent (which strangely enough didn't tell me it already existed, so it was almost like that file didn't exist previously). I then deleted the file afterwards as it still did not work, and then later on found the file contents that should have been there in the Cloudron/box git repository, manually created the file again and added in the contents. This then immediately resolved the issue for the sudo concern and backups continued again and also were fully successful rather than hitting the "operation not permitted" error.
The more I think about it, I'm starting to wonder if the yellowtent sudoers file even existed when installing Cloudron and restoring from backup, is it possible any of those tasks may have modified it or prevented it from being added?
EDIT: Interestingly, I got collectd errors while running into the sudo issues prior to resolving it, and I see in your latest update to 5.1.1 changelog that you fixed collectd installation issue, I doubt it's related but is that possible in this case as well as the possibilities above?
