Help configuring restic - rclone - ProtonDrive WITH encrypted configuration

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

Remove rclone config encryption or provide password using environment variable.

Thank you for your answer. Could you help me out how to provide the password using an environment variable? Not sure about this…

It looks like it might be RCLONE_CONFIG_PASS

If that doesn’t work, I’d approach this from a slightly different angle.
The error looks (to me) to be rclone-specific, rather than an error message generated by restic.
I’d personally start by checking if you able to use rclone to open the remote directly (without using restic).

1 Like

Thank you! By using ChatGPT I solved the issue!

Glad to hear it!

Would you mind sharing what the solution was, for future people that might find this thread after encountering the same (or a similar) issue?

Basically, before I execute the restic backup command I execute (on Linux) export RCLONE_CONFIG_PASS=“your_password”` in order to supply the password via the environment variable :slight_smile:

1 Like

Thanks for sharing!

Also, full credit to @kapitainsky for suggesting the environment variable idea in the first place :slight_smile:

1 Like