I’m unsure when it started since I haven’t logged into my Duplicati instance in a few weeks (it’s been pretty solid for me). However, today when I tried to log into my duplicati instance through the web interface it comes to a the password screen (just the password with login in the middle, duplicati logo in upper left) and when I enter my password and click "login” nothing happens. I’m on Tumbleweed running the docker container duplicati/duplicati:latest but also tried switching to the lscr.io/linuxserver/duplicati:latest build too and it does the same thing. I do use watchtower so I’m certain it was an update. I do recall using the 2.x version and did see a UI change a while back but the login screen today does look different than what I recall.
On a side note I have two backup machines, one is a Windows PC and it is working when I log in, but the Tumbleweed Docker container one isn’t letting me in. I use the DUPLICATI__WEBSERVICE_PASSWORD= option to declare my password (I have always done this) and I’m certain I’m typing it correctly (it’s saved, used 100 times, and I copy/pasted from my compose file in case something was wrong). It’s just not going past that page.
Do you see any logs or similar that could explain it?
You can try the (very old) login page that is /login.html which works slightly different from the current login page (at /ngclient/login).
Otherwise, could you try to restart the Docker container? Since you provide the password via the Docker config, it is re-applied on each startup, so if it somehow changed in the meantime, a reboot will reset it.
Thanks! Interstingly /login.html worked. I’m not sure what is wrong with the other login method as my Windows duplicati instance works fine with it. Hmmm… Well for now I’m happy, and it does appear backups are working.
So on a whim I decided to change my password (using the Docker compose file). Previously it was 24-characters and contained upper case, lower case, numbers and special characters. I revised it to be 10-characters just upper case, lower case and numbers and it worked. Then I wondered if it was the special characters I use (which are basic ASCII as far as I’m aware) or perhaps the length. So, I modified the compose file password to be 14-characters but contain the exact same special characters and it let me in. So, my guess is it’s something to do with the password length.
Thanks for helping me sort this. For now, 14-characters is sufficient since this is only available on my local network 24 characters was perhaps a bit overkill anyway.
Okay, that’s odd. Are you using native install, or docker install? I’m using duplicati/duplicati:latest . I’m not at home right now, but I do have a local windows install which didn’t have the same issue. Perhaps it’s something with the docker tooling?
I am using a developer setup, so the latest code for both Duplicati and ngclient.
It is possible that something was fixed, but I do not see that change.
Could this be a case where a password manager plugin overrides the password somehow? I think there were reports of this happening on some other browser.
Just downloaded duplicati-2.2.0.3_stable_2026-01-06-linux-x64-gui.deb and installed.
Firefox 146.0.1 (64 bit)
Linux Mint 22.1 Xia (Ububtu)
Nothing happens when you click the Login button, viewing the password shows its correct. Don’t even get any pop up error messages on the page when you type an incorrect password. There’s no console or download errors in the FF Inspector. There are no ajax network calls and therefore it appears the login isn’t running a fetch to check the password. Disabling Add Ons has no effect.
Works in Chrome including pop up messages. Chrome runs an AJAX call to http://localhost:8200/api/v1/auth/login which return a 401 for an incorrect password and a 200 for a correct password.
