First time posting here, hope this is the correct place to ask this since I’m desperate for some help!
After formatting and installing a new fresh version of Windows 10 on my PC, installed Syncthing and linked everything with my mobile and the folders correctly.
Everything worked great at this point, but that was yesterday. Today, for some unknown and bizarre reason, the GUI in the browser doesn’t load, it shows this typical message of “Connection lost, too much time waiting for a response”, but, the sync indeed works. After some tests, files are being synchronized between my mobile and the PC.
What’s happening, and how do i fix the browser issue?
Open the dev console (F12) and check if there are any errors logged at the bottom. And/or in the network tab. If you don’t know what to look for, make/post screenshots. Also addons may be interfering.
Well, Private browsing didnt help since i also use a lot of addons in there, but using a new profile worked.
The issue is that before formatting the PC, I had approximately the same amount of addons… Isn`t other way to see what is exactly messing with Syncthing?
The bad ones are that after checking every add-on nothing changed, even seeing everything correct in the other profile or in other browsers.
So I gave up and erased this profile, created another new with all the bookmarks and add-ons and after booting up the system, everything seemed to be ok.
I still don’t know what caused that bizarre behavior, but now it works fine, so i’d call it a success.
This reminds me of a problem I once had with various random websites. The internal database for “site storage” (similar to cookies I believe, but for arbitrary data) had become corrupted in my Firefox profile. Deleting some SQLite file or directory within the profile recovered from the error. It manifested as various sites (such as this forum IIRC) not loading but staying at a blank page. If the page JavaScript code assumes that some value can be read from / written to the site-specific storage, then it might not get over a failure to actually loading the page content.