This should work with an API key alone. If you want to use a login and password instead, then you also need to enable basic authentication in the advanced GUI configuration in Syncthing. Otherwise they won’t work. If you use an API key already though, then there should be no need for a login and password in that situation.
Thank you for the message. I’ve been using Syncthing Tray without problems for a long time. Following the reinstallation of my laptop and the enablement of the login/password in the GUI the popups started to appear.
I checked the API key but it is the right one.
Is there a way I can debug this further?(to get some more verbose logs maybe?)
There is an error log in Syncthing Tray itself. Does it say anything more than just the error message as seen in the screenshot? Also, if you have enabled the HTTPS-only mode in the Web GUI, then you need to use https:// in Syncthing Tray as well.
Can you post a screenshot of your Syncthing Tray configuration? I’ve also been using Syncthing Tray for years now, but I haven’t noticed any special changes or breakages in the newest version.
I had a hard look at my settings and found a setup that works (but is not ideal for me).
With the new laptop I use Tailscale, a Wireguard-based meshed network. I forced the GUI to bind to its 100.x IP - mostly because this IP is reverse-proxied under a predictable name (the_device.syncthing.mydomain.com).
This setup was causing the issues.
I switched to a 127.0.0.1 binding for the GUI and Syncthing Tray is now happy. I am a bit less but at least I do not get the constant popups anymore.
I will now try to move back to the tailscale based network and check what is wrong (I vaguely suspect a DNS issue with Syncthing Tray trying to resolve the tailscale name in the address (https://thedevice.mytailsclaename.ts.net)