Restic with wasabi repository - Issues after init and first backup

I’ve reformatted your messages, there’s an icon labelled with </> in the editor that you can click after marking several lines, it’ll mark the text as verbatim.

First: which version of restic is that (run restic version)?

What’s happening here is that the service apparently lists a file that could not be accessed with the account (and the policy) you’re using. Restic was able to create a lock file, but it is unable to read it afterwards. That’s what the errors say. For safety reasons, restic unlock won’t remove locks it cannot read and check. There’s restic unlock --force, but that’s not a solution. You need to find out what’s wrong.

I’m guessing (I don’t have any experience with Wasabi) that the policy isn’t quite right yet. Can you try reading the file with an s3 client, e.g. mc?