I had been using Syncthing on my work computer for the past few months without issue. When I came back from the holiday break, I was unable to log into the app’s config screen in my browser. I get the error message “Login failed, see Syncthing logs for details.” I’ve reinstalled the app and I run into the same issue. I’ve double-checked and Synthing is running. It should be the right username and password too, as I get a different error message if I try a different password.
This is version 1.28 on Windows 11 Professional.
I’ve found the log but there’s nothing I can understand in it. I’m attaching the log file, I can’t copy/paste its content because of issues with @ing (mentioning) users. Thank you!
The log you’ve uploaded is for the database and it’s not useful for the problem at hand.
As long as Synthing has been installed as a user application (and not as a service, etc.), the “normal” log will be located in %LOCALAPPDATA%\Syncthing (copy and paste the path into the address field in the Windows Explorer, then press “Enter”).
You could also edit the config.xml file and remove the password from there completely. Just make sure to shut Syncthing down before doing so (or kill the process if you cannot access the GUI).
Remove the “user” and “password” lines in their entirety, and restart Syncthing. That should remove the GUI login credentials, which will allow you to access the GUI with no login needed. It will restore access, but not actually fix the problem.
I have had the same issue develop on Syncthing running on a Synology DS218+, on v1.29. Tried this manual “reset” process several times, but I can never get it to do a valid login (with a username and password set). Curiously, if you knowingly enter an incorrect username or password, it should return “Incorrect user name or password,” which mine does when I do that. Only when I enter the correct username and password does it return “Login failed, see Syncthing logs for details.”
What is even more curious is that I have an identical Synology DS218+ at another location, running an identical Syncthing setup on v1.29, and it does not present this issue. So it seems like v1.29 itself is not the culprit. Something else about our respective Syncthing setups, perhaps combined with v1.29, may be the problem.