It sounds to me like you’re barking up the wrong tree. The gui is there and loads, just the JavaScript doesn’t run? Browser develop console, settings and plugins is where I would start looking.
1 Like
What about trying a different browser? Installing something other than the default? No extensions or plugins.
1 Like
This might have been overlooked, but the message about “another instance already running” is about the database being locked, no? In that case, the one you just started from the command line quits after the message. So you need to find out whether another instance is in fact running and how it is being started. Two instances cannot run simultaneously on the same database (thus, same home directory).
Once you are certain that exactly one instance of Syncthing is really running, the GUI should work. If it still doesn’t, I agree with @calmh that the browser is where you should start looking for the broken JavaScript stuff.
From @ Finn1sher
I ended up removing both the gzip download for syncthing and the rpm package (which has now updated to 1.24) and reinstalling syncthing through dnf (the rpm package again).
In this case, the system should now be running only one instance of Syncthing. So, @ Finn1sher should look closer at the browser and possibly try installing a different one.
At this point it’s worth trying.
If it were me, I would install open SSH server on the machine that is not able to successfully run the admin console.
Then, from any other computer on the local network I would run an SSH client and open a tunnel to port 8384 on the syncthing server.
Whether or not that computer can bring up the admin console should be a clear indicator of whether the problem is related to the server, the browser, or the program.
Or, temporarily let 0.0.0.0 access the admin console. This would be simpler, faster, and less complicated.
At this point I’m very curious to see if any other computers on the network can open the admin console on that machine.
Oh my god.
You’re absolutely right. I just disabled Ublock origin for the site and the interface is functional now. Who added 127.0.0.1 to a blocklist?!!!
Thank you all for your help, it’s been resolved now. For future reference: if the web UI is a garbled string of text, check if your browser is blocking anything.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.