Arch Linux User Repository

I'm not sure how to implement that. I wouldn't want to do a static password in the git repo. I'd prefer disabling the encryption by default rather than doing a static password.

Is there a reason why you couldn't add "SETTINGS_ENCRYPTION_KEY=<your_password_here>" to the '/etc/default/duplicati' file?

I think this should be reported upstream to Duplicati. I am not seeing this error, so presumably the dependencies are correct... Could you post the link to the issue here so I can follow along?

Thanks!

Hi @valandil, thanks for the update!

I updated to 2.0.9.107-1. I was able to configure the encryption key, etc. But I keep getting this .NET error when starting the application. No matter which commandline options I give. Is this something to do with the package, or should this be raised with Duplicati itself?

Unhandled exception. Unhandled exception. System.NullReferenceException: Object reference not set to an instance of an object. at Duplicati.GUI.TrayIcon.HostedInstanceKeeper.<>c__DisplayClass5_0.<.ctor>b__0(Object dummy_arg) Aborted (core dumped)

Asked about in the Forum: https://forum.duplicati.com/t/linux-duplicati-does-not-start-unhandled-exception-2-0-9-107-canary-2024-09-11/19054

Ever since 2.0.9.102, I reverted to 2.0.9.101 decided to sit this out for awhile until the dust settles. Checked in to see how things were going and after reading @valandil's comment and some of the duplicati forum discussions on 2.0.9.106, I think I'm going to wait it out for a few more versions. Thanks for the update information.

Updating to 2.0.9.106 will be a fairly manual process: they implemented encryption for the local database, and in 2.0.9.105 defaulted to generating a key for each device. This turned out not to be secure enough, so they removed that feature in .106. Here's the procedure, from the releases:

Note for users of 2.0.9.105: The method for extracting an encryption key from the machine seriail number did not produce secure results. This feature has now been removed, and will prevent you from upgrading. To upgrade from 2.0.9.105, start with --disable-db-encryption, then exit, then upgrade to 2.0.9.106+. Users from other versions than 2.0.9.105 will not have difficulties, and Docker users should not see any issues either.

I will let this comment sit for a few days, then push the update.

@valandil The issue was I already had a password from before the update. I thought it would carry over. But I kept getting connection refused until I forced the password to reset.

Thanks for adding the details here. The install script should have printed a link to the GitHub release announcement with the same information though.

I figured it out via this post. https://forum.duplicati.com/t/release-2-0-9-102-canary-2024-08-02/18777/3

It seems like Duplicati switched over to forcing passwords for the webUI and this seems to have wiped out the last password I used. I fixed it first by stopping all instances of Duplicati on my system and setting a new password up. Since I run Duplicati as the user 'Duplicati' I had to run this. sudo -H -u duplicati bash -c '/opt/duplicati/duplicati-server --webservice-port=8200 --webservice-password=<new password>'

Once a new password is setup, it saves that password, then you can just run it headless as normal again via the systemd unit.

I'm not sure how to deal with the latest change. If I VNC into the remote desktop I have I can access the webUI by starting the tray icon. But I was using duplicati as the "duplicati" user in a headless style by port forwarding it over SSH.

Port forwarding doesn't work and I get "Duplicati.WebserverCore.Exceptions.UnauthorizedException: Authorization failed due to missing cookie."