[SOLVED] Win 10 x64: Connection to server was rejected due to invalid authentication

Dear forum!

My System:
Windows 10 x64 with latest updates.
Browser: Firefox

I’ve installed the new version from MSI-package today:
duplicati-2.1.0.2_beta_2024-11-29-win-x64-gui.msi
over a previously working version - don’t know the exact version.
was primary from
duplicati-2.0.5.1_beta_2020-01-18-x64.msi
and updated to 2.0.X.X before today.

Afterwards I’ve tried to open the Duplicati-login

  1. from my existing bookmark
    http://localhost:8200/
  2. from the Duplicati tray bar icon

Both give the error:
Connection to server was rejected due to invalid authentication.
Log in again, or re-open the page from the TrayIcon (if applicable)
[Log in] [Reload]

Decision [Reload] gives the same error again.

Decision [Log in] opens the Duplicati Login-Page BUT:
After entering my password I get the error-PopUp:
localhost:8200
Failed to get nonce: Not Found

Then I’ve tried with Browser Edge:

Same error but [Log in] seems to let me in
and I can see Duplicatis Home and my Profiles again.

But when clicking for a manual backup for one of my profiles
nothing seems to happen: The Duplicati progress tray bar on top of the page stays empty with no message.

And in Firefox (deleting cookies for localhost and last try for this…) the error stays the same.

Can anybody help?

Here is an update:

With Edge-Browser the start of manual backup produces new *.aes files.

But they are not shown as new successful backup with Date/Time in the Duplicati-browser GUI

Do you mean status under the job on home screen? I think it updates on success. Did it succeed?
Status/info is also on the status bar, the job log and the server log at About → Show log → Stored.
Restore menu should also show the backup you just made (assuming it has finished successfully).

My use of the GUI will sometimes act up. Maybe yours is as well. Sometimes a page reload helps.

Thank you very much for your answer.
Today the problem has disappeared and everything works fine as expected.

I did a test backup and restore successfully and while backup the status bar in Duplicati-GUI shows the actions again as before.

I don’t know why and what’s happened, because yesterday I also rebooted but without luck (my Windows is set to do NOT a Quickstart).

Yes: that’s what I meant, but the DateTime has stayed at an old old backup time.
Today it’s fine again :slight_smile:

Yes: That was also the case yesterday.

This is solved without clarify the reason - maybe this helps someone else not to fall into panic too early. :wink:

An update again:

  1. It’s working in Firefox and Edge as well now
  2. When opening only the servername-URL
    http://localhost:8200
    this leads to
    http://localhost:8200/ngax/index.html
    which produces the error
    Connection to server was rejected due to invalid authentication.
    Log in again, or re-open the page from the TrayIcon (if applicable)
    [Log in] [Reload]

And [Log in] leads to URL
http://localhost:8200/login.html
which works fine and now is stored in my bookmarks.
:wink:

Thanks for the repro. I think I’ve had to type in the login.html page before.
Not sure why. I think that 2.0.8.1 also sometimes had to be coaxed to login.
I didn’t use a password then, so I never had a good handle on this problem.

I’m experiencing this error, but in my case I just installed duplicati on a Debian 12 and I hadn’t registered any password yet. Does anyone have any idea how to proceed?

I tried using the option: duplicati-server --webservice-password=password

But he came back to me: No database encryption key was found. The database will be stored unencrypted. Supply an encryption key via the environment variable SETTINGS_ENCRYPTION_KEY or disable database encryption with the option --disable-db-encryption
Inside getter
Server has started and is listening on port 8200

And when I tried to log in it didn’t work

I managed to resolve it with: duplicati-server --webservice-password=password --disable-db-encryption

After that, I logged into the web panel and changed the password! The database may not be encrypted, but in this environment I believe it will not be a problem.

1 Like