mrmarkuz
(Markus Neuberger)
April 14, 2025, 6:53pm
1
RustDesk is an open source remote support software.
A RustDesk server is used to manage connections between RustDesk clients.
RustDesk documentation: Docs of RustDesk :: Documentation for RustDesk
App Documentation: GitHub - mrmarkuz/ns8-rustdesk
After installation and choosing a FQDN, a RustDesk client can be downloaded and configured to use the app as server, see also ns8-rustdesk/README.md at main · mrmarkuz/ns8-rustdesk · GitHub
Thanks in advance for testing.
9 Likes
Great Job @mrmarkuz
This works perfectly. Thank you…
1 Like
I just noticed that no HTTP route was created after the installation. Does this have to be done manually now?)
mrmarkuz
(Markus Neuberger)
April 15, 2025, 1:51pm
5
No, it has no web UI so no route needed.
1 Like
Then I don’t need a certificate?
1 Like
mrmarkuz
(Markus Neuberger)
April 15, 2025, 1:53pm
7
Right, no certificate needed.
1 Like
capote
(Marko)
April 16, 2025, 7:08am
8
I Confirm, it works fine.
But I have issues with Backup on a SMB-Share.
Error1
Task module/rustdesk1/run-backup run failed: {‘output’: ‘’, ‘error’: “restic --option=rclone.program=/usr/local/bin/rclone-wrapper snapshots\nFatal: config or key 3b212a84676cdb6e935108238a1fd6b61476058376ac84f0127946bbdc778531 is damaged: ciphertext verification failed\nInitializing repository cfd9b78e-86e5-5840-98d5-f82acb89f127 at path rustdesk/3c0a663e-d0b1-44b9-9bbe-0a84ed3a1683\nrestic --option=rclone.program=/usr/local/bin/rclone-wrapper init\nFatal: create repository at rclone::smb:DAHO-NS8-BAK/rustdesk/3c0a663e-d0b1-44b9-9bbe-0a84ed3a1683 failed: Fatal: unable to open repository at rclone::smb:DAHO-NS8-BAK/rustdesk/3c0a663e-d0b1-44b9-9bbe-0a84ed3a1683: config file already exists\n\n[ERROR] restic init failed. Command ‘[‘podman’, ‘run’, ‘-i’, ‘–rm’, ‘–name=restic-rustdesk1-1371372’, ‘–privileged’, ‘–network=host’, ‘–volume=restic-cache:/var/cache/restic’, ‘–log-driver=none’, ‘-e’, ‘RESTIC_PASSWORD’, ‘-e’, ‘RESTIC_CACHE_DIR’, ‘-e’, ‘RESTIC_REPOSITORY’, ‘-e’, ‘RCLONE_SMB_HOST’, ‘-e’, ‘RCLONE_SMB_USER’, ‘-e’, ‘RCLONE_SMB_PASS’, ‘-e’, ‘RCLONE_SMB_DOMAIN’, ‘Package restic · GitHub ’, ‘–option=rclone.program=/usr/local/bin/rclone-wrapper’, ‘init’]’ returned non-zero exit status 1.\n”, ‘exit_code’: 1}
1
Error2
restic --option=rclone.program=/usr/local/bin/rclone-wrapper snapshots
Fatal: config or key 3b212a84676cdb6e935108238a1fd6b61476058376ac84f0127946bbdc778531 is damaged: ciphertext verification failed
Initializing repository cfd9b78e-86e5-5840-98d5-f82acb89f127 at path rustdesk/3c0a663e-d0b1-44b9-9bbe-0a84ed3a1683
restic --option=rclone.program=/usr/local/bin/rclone-wrapper init
Fatal: create repository at rclone::smb:DAHO-NS8-BAK/rustdesk/3c0a663e-d0b1-44b9-9bbe-0a84ed3a1683 failed: Fatal: unable to open repository at rclone::smb:DAHO-NS8-BAK/rustdesk/3c0a663e-d0b1-44b9-9bbe-0a84ed3a1683: config file already exists
[ERROR] restic init failed. Command ‘[‘podman’, ‘run’, ‘-i’, ‘–rm’, ‘–name=restic-rustdesk1-1371372’, ‘–privileged’, ‘–network=host’, ‘–volume=restic-cache:/var/cache/restic’, ‘–log-driver=none’, ‘-e’, ‘RESTIC_PASSWORD’, ‘-e’, ‘RESTIC_CACHE_DIR’, ‘-e’, ‘RESTIC_REPOSITORY’, ‘-e’, ‘RCLONE_SMB_HOST’, ‘-e’, ‘RCLONE_SMB_USER’, ‘-e’, ‘RCLONE_SMB_PASS’, ‘-e’, ‘RCLONE_SMB_DOMAIN’, ‘Package restic · GitHub ’, ‘–option=rclone.program=/usr/local/bin/rclone-wrapper’, ‘init’]’ returned non-zero exit status 1.
1 Like
mrmarkuz
(Markus Neuberger)
April 16, 2025, 7:12am
9
Thanks, I’m going to check that later.
EDIT:
I can’t reproduce, rustdesk backup and restore works on my servers.
Seems like the config/key isn’t working or damaged:
Assuming the rustdesk instance is named rustdesk1.
Show backups:
runagent -m rustdesk1 restic-wrapper --show
This leads to following result, get the backup number, 6 in this example:
Scheduled backups:
- 6 Backup to Contabo S3, destination UUID 9a76...
Check the backup number 6:
runagent -m rustdesk1 restic-wrapper --backup 6 check
Maybe it also helps to just remove rustdesk1 backup from the storage and run a new backup.
1 Like
capote
(Marko)
April 16, 2025, 9:28pm
10
~# runagent -m rustdesk1 restic-wrapper --show
Destinations:
- cfd9b78e-86e5-5840-98d5-f82acb89f127 SMB-Syno [DAHO-NS8-BAK] (smb:DAHO-NS8-BAK)
Scheduled backups:
- 4 Sicherung nach SMB-Syno [DAHO-NS8-BAK], destination UUID cfd9b78e-86e5-5840-98d5-f82acb89f127
- 5 RustDesk > SMB-Syno [DAHO-NS8-BAK] (2), destination UUID cfd9b78e-86e5-5840-98d5-f82acb89f127
~# runagent -m rustdesk1 restic-wrapper --backup 5 check
restic --option=rclone.program=/usr/local/bin/rclone-wrapper check
using temporary cache in /var/cache/restic/restic-check-cache-3499753513
create exclusive lock for repository
Fatal: config or key 3b212a84676cdb6e935108238a1fd6b61476058376ac84f0127946bbdc778531 is damaged: ciphertext verification failed
Maybe it also helps to just remove rustdesk1 backup from the storage and run a new backup.
I did it before.
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
capote
(Marko)
April 17, 2025, 7:13am
12
:~# runagent -m rustdesk1 restic-wrapper unlock --remove-all
restic --option=rclone.program=/usr/local/bin/rclone-wrapper unlock --remove-all
Fatal: config or key 3b212a84676cdb6e935108238a1fd6b61476058376ac84f0127946bbdc778531 is damaged: ciphertext verification failed
~# runagent -m rustdesk1 restic-wrapper snapshots
restic --option=rclone.program=/usr/local/bin/rclone-wrapper snapshots
Fatal: config or key 3b212a84676cdb6e935108238a1fd6b61476058376ac84f0127946bbdc778531 is damaged: ciphertext verification faile
~# runagent -m rustdesk1 restic-wrapper key list
restic --option=rclone.program=/usr/local/bin/rclone-wrapper key list
Fatal: config or key 3b212a84676cdb6e935108238a1fd6b61476058376ac84f0127946bbdc778531 is damaged: ciphertext verification failed
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)
I’ll try it.
Thank you Markus
1 Like
capote
(Marko)
April 17, 2025, 7:25am
13
capote:
I’ll try it.
I deleted all files within the SMB share on my DiskStation.
The backup is now running without any problems.
thank you, Markus
2 Likes