Hello everyone,
I used restic happily with Proton Drive for some time. However, some months ago I decided to encrypt the configuration for rclone, as I felt more secure. Unfortunately, I did not think of the implications it has with restic.
Disclaimer: did not use restic for a few months now.
The command I previously used was:
restic backup /home/manuel/ --one-file-system --repo rclone:PD:ResticBackup
restic backup /home/manuel/ --one-file-system --repo rclone:PD:ResticBackup
rclone: Enter configuration password:
rclone: password:2025/04/18 10:06:20 ERROR : Couldnât decrypt configuration, most likely wrong password.
rclone: Enter configuration password:
âXXXXXXXâ # I used â â because my password starts with ?
rclone: password:
Fatal: unable to open repository at rclone:PD:ResticBackup: error talking HTTP to rclone: Get âhttp://localhost/file-17205766766146446417â: context deadline exceeded (Client.Timeout exceeded while awaiting headers)
[manuel@linny ~]$ âXXXXXXXâ
bash: ?a(kM0b$5O13i27c: Befehl nicht gefundenâŚ(process:16936): GLib-GIO-CRITICAL **: 10:11:53.565: g_task_return_error: assertion âerror != NULLâ failed
(process:16936): GLib-GIO-CRITICAL **: 10:11:53.565: GTask 0x55b8a8fd0840 (source object: 0x55b8a8fbd440, source tag: 0x7f227dbcc8c0) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program.
Could anyone help me getting restic up and running again?
Some facts:
OS: Linux Fedora 41
Restic version: restic 0.17.3 compiled with go1.23.2 on linux/amd64