Upgraded from 2.0.8 to 2.1.0 and messed with encryption

1

I did something stupid and messed up with my duplicati instance on a server.

A few weeks ago I asked this question: After update to 2.0.8 Error-Duplicati.Library.Main.Operation.BackupHandler-FatalError

And the solution worked fine for me on my first server (Server 1).

Now, I upgraded duplicati on my other Server (Server 2), but instead of doing this …

Open Duplicati, edit the configurations of your backup, then go to Destination and hit Test connection, you will get a modal that offers to change the host key, hit OK and save the settings. Manually trigger a backup job and everything should work again.

… I added the env var SETTINGS_ENCRYPTION_KEY=<value> and restarted the container. I think this was a mistake, even if I don’t know what exactly happened. I am not sure if the env var here is related to my issue …

However, now I don’t see my backup job and after a while I get this screen:

issue
issue2396×1458 137 KB

How can I fix this? Your help is much appreciated, thank you!

2

How did you get a screen originally? Did you open one or was it sitting there?

How long (seconds, minutes?) before seeing connection error? Will it refresh?

https://hub.docker.com/r/linuxserver/duplicati (not produced by Duplicati team)
has “Support info”. You can check your logs, or go in and check the processes.

If you can’t connect at all, you might be lacking a duplicati-server process.
Logs may say why.

You can also consider if you are using /config folder per the LSIO directions.
That’s what keeps your config stored when you change to a different container.
If you did set one up, you can look at it from the host, to look at files and dates.

Using Duplicati from Docker has notes on Duplicati’s image. Some may fit LSIO.

I don’t use Docker. Anybody who does is more than welcome to suggest things.

1 Like
3

@ts678 Thank you so much for your answer. I just found a solution: I had to turn on websockets! :see_no_evil_monkey: Found an entry in the logs, that I must have overseen, when I created this thread.

Thank you!

1 Like