Yeah, which makes sense, unfortunately. I have a hunch what it might be, a possibly fixed build is brewing, if anyone is willing to test that build (once done) to confirm or deny that would be great.
It should in either case also provide more information when running with API tracing, so might help in that respect even if I didn’t guess the bug correctly…
Linux packages here if anyone can please test: https://github.com/syncthing/syncthing/actions/runs/12697423438/artifacts/2409369053
Windows packages: https://github.com/syncthing/syncthing/actions/runs/12697605514/artifacts/2409419624
404 Not Found for linux packages
Got them now. And they work a treat. Thanks for the fast work.
(I can’t post a new reply because I’m new here.)
Keith
You probably need to be logged in on Github 
Here are URLs without auth:
can confirm it’s working for Windows as well
Fantastic, thanks guys. I’ll prep a release with the fixes.
i am not much of a developer but I would like to understand how this bug manifested into the new release. you stated before you have no clue since nothing (much?) changed from 1.28.x to 1.29.0
so what exactly changed outside of the code? some compilter stuff, some buildsystems or some tools or anything?
then again why does a change in sourcecode fix this to begin with? thanks for explaining about more about this.
would like to learn about this stuff.
It’s an interesting confluence of a couple of things.
We changed the protobuf library; it has a different behaviour than the previous one. We unmarshal session tokens from the database into a token set. Previously, when unmarshalling no tokens into an empty map, it would leave an empty map. Now, it sets the map itself to nil instead. We then tried to access this, “knowing” it would not be nil, and the request panicked (=> connection reset).
The Go HTTP server by default does a bunch of unnecessary logging on it’s own; we squash that. But that also means we didn’t get any debug logs for this. I added that so we at least see something on the console when this happens and debugging is enabled.
v1.29.1 fixed my SyncTrayzor install and can now use Edge to set the user and password in the GUI. Thanks for your fast action on this.
v1.29.1 fixed my install, thanks to the fast help
Hey folks, on v1.29.2, still encountering this issue. Removing the password from config.xml and re-setting the password via the GUI does not result in a change of behavior. Once the password is set, I’m unable to log in.
EDIT: Switching the GUI from HTTP → HTTPS resolved the issue. Very strange, but I have basic login working again.