mrmarkuz
(Markus Neuberger)
April 17, 2025, 6:58am
11
Maybe it’s a corrupted lockfile?
runagent -m rustdesk1 restic-wrapper unlock --remove-all
Let’s check the snapshots:
runagent -m rustdesk1 restic-wrapper snapshots
Let’s try to list the keys:
runagent -m rustdesk1 restic-wrapper key list
You have the same destination for 2 backups, maybe they use different keys for the same destination which confuses restic? Maybe it’s necessary to remove the whole destination and recreate it also on the NAS or create a new destination on the NAS (other directory)
Links to check:
That usually means that the password for the key is the correct one, but the key doesn’t match the config file. The password also works for that key, and restic got one step further: it could also successfully decrypt the config file. So this is...
Hi guys, with every command i try i get: config or key 71d8f23f6f1a9ff026a903d66545053234435afaa83b4d8118cfe88f4ca6e125 is damaged: ciphertext verification failed. Try again restic version restic 0.17.3 compiled with go1.23.3 on linux/amd64 ...
Reading time: 1 mins 🕑
Likes: 4 ❤
2 Likes