Remove(<snapshot/026a010db0>) returned error, retrying after 720.254544ms: blob not removed, server response: 403 Forbidden (403)
Remove(<snapshot/1d99f80bcd>) returned error, retrying after 873.42004ms: blob not removed, server response: 403 Forbidden (403)
Presumably you have incorrect permissions on those files on the Linux server. Make sure that all of the files and folders are read- and writeable by the user that rest-server runs as.
Not really sure what to say. REST-server just tries to read and write those files. If it fails to do that then you need to look closer at the permissions etc. Have you for starters verified that those snapshots exist in the snapshots/ folder?
some time ago I did the check of screenshots. After that episode I had to fix the permissions, because it couldn’t make backups. It can be related to that?
It’s a bit unclear what you mean. Again; Verify that the files mentioned in the error message are actually present, then check the permissions on those files and the folders as well.
Which rest-server version do you use? How do you start the rest-server?
For somewhat recent rest-server versions, the --append-only flag is the only way to cause a 403 error. So the error is either caused by that flag, a very old rest-server version (just maybe, haven’t checked those) or there is some proxy/webserver running in from of rest-server which forbids deleting.
Yes. The rest-server program is just one single binary/executable, which means that you can put it anywhere you want and run it, it really doesn’t care where it is placed/located on your file system.
What you want to make sure however is that when you have downloaded the latest rest-server release, and you run it the usual way, the copy you downloaded is the one that is actually being used (instead of the old one you installed via scoop).
I would suggest that you uninstall the one from scoop to make sure that you don’t accidentally execute that instead of the new one you downloaded from the link above.