2.2.0.0 Signin Token and Windows Desktop

I just upgraded a Windows 11 desktop to version 2.2.0.0 from 2.1.0.5, and am having problems making access around a prompt for a JWT Signin Token that I don’t know how to find.

I’m running this as a desktop application, where I’m making access from the TrayIcon, and not as a system service. When I attempt to start the Duplicati server, I get “Connection to server was rejected due to invalid authentication”. If I click on the offer of “Log in”, I get taken to http://localhost:8200/login.html and a request for a password that I don’t have, and a Reload merely repeats the process.

I’ve followed the documentation links in Help, but so far, I’m not finding how to clear this problem. Much of the Windows-specific documentation is focused on installations that run as a system service, or specific detail that only applies to a bash command prompt in either Linux or MacOS. There is something small that I’m missing, but I can’t find it.

I will note that I have both a box that runs Ubuntu 22.04 (actually, Mint from Ubuntu repositories), and MacOS 15.7. I did similar upgrades on both of those boxes, and haven’t had problems - both are handling 2.2.0.0 without issue.

Any pointers on how to find how to resolve this question?

TIA

You can read the developer’s comment on what sounds like a similar case starting at below. Unfortunately we never heard back on the resolution, but there are some suggestions given.

Similar usage too? Some Linux systems run as systemd service instead of user tray icon start.

Problem appears to be solved.

I followed that link, and it looks like the description of how signin.html is handled is what I needed to know. I did make sure that scripting was enabled for 127.0.0.1 (I had had it blocked) . From there, I deleted the signin token portion of the URL, and after I refreshed the screen, I got a prompt for create/update of password. I put in a password that I know that I can remember, and I’m now into the updated UI, and as I write a missed scheduled backup job is now catching up.

wagner:

I did similar upgrades on both of those boxes, and haven’t had
problems - both are handling 2.2.0.0 without issue.

Similar usage too? Some Linux systems run as systemd service instead of user tray icon start.

A good question, but yes. All three platforms have been configured to work through TrayIcon, and not running as daemons.

Thanks for the feedback.