search

Martchus / syncthingtray

Tray application and Dolphin/Plasma integration for Syncthing
https://martchus.github.io/syncthingtray/
Other
1.5k stars 42 forks source link

Syncthing Tray is in a perma state of reconnecting #253

Closed trdemoss closed 1 week ago

trdemoss commented 2 months ago

Syncthing Tray is in a perma state of reconnecting. The main sync thing application is running out of this Windows folder, C:\Users\RDeMoss\AppData\Local\Syncthing. This is running normally and syncs with my devices as it should. In settings for the "Startup" navigation | "Syncthing launcher" tab, I have the Syncthing executable pointing directly at the Windows folder and exe file. The arguments are "-no-browser -no-restart -logflags=3". In the Syncthing log view, I can see that Syncthing is running and looks happy.

When I look at "Tray" navigation | Connections, I see the Syncthing URL which works and connects; the API Key which is also correct; the HTTPS certificate is set to Auto-detect and HTTPS is enabled; The selected Overall Status is checked, but the reconnection status is "reconnecting" and has been like that for days.

Any suggestions to debug the perma reconnecting state would be much appreciated. I have set this to HTTP mode and that did not fix it. I've added the https-cert.pem to the HTTPS line and that didn't do anything. I've stopped and started syncing many times and the same with the tray application. I've imported the syncthing configuration settings and that seems to work fine but the parameters don't change because I believe they are correct. I do see these

I do see these events in the logs, but they appear to be devices that are offline or unresponsive from a polling cycle.


[B4DX5] 2024/04/18 17:31:30 INFO: Lost primary connection to GNF4YE4 at 10.xxx.10.236:22000-10.xxx.10.135:22000/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256/LAN-P10-5U7GETSGKVDD64O9MIKOE8UBM2: reading length: read tcp 10.xxx.10.236:22000->10.xxx.10.135:22000: wsarecv: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (0 remain)
[B4DX5] 2024/04/18 17:31:30 INFO: Connection to GNF4YE4 at 10.xxx.10.236:22000-10.xxx.10.135:22000/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256/LAN-P10-5U7GETSGKVDD64O9MIKOE8UBM2 closed: reading length: read tcp 10.xxx.10.236:22000->10.xxx.10.135:22000: wsarecv: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.```
Martchus commented 2 months ago

So this doesn't work at all? Or is this state only reached after a while?

Are there some log messages or errors from Syncthing Tray itself? See https://github.com/Martchus/syncthingtray/issues/252#issuecomment-2063325731 for how to get those.

trdemoss commented 2 months ago

Thanks for the reply @Martchus. Syncthing itself is running normally. I added a screenshot of the synching webUI and the Syncthing Tray into the attached support bundle. Only the Tray software is saying that it's reconnecting. When I first installed the tray, it was working fine. I added my devices and folders and made other changes like enabling HTTPS. Later, after a reboot, the Tray is stuck on reconnecting. I checked the obvious settings like the API key, HTTPS settings, etc and those seem to be set properly. I'm sure this will work, but can't find logs for the Tray or any debug settings. I've also tried selecting and deselecting the Overall status options and clicking the "apply" button. It never changes from "reconnecting."

support-bundle-B4DX5M6-2024-04-22T163034.zip

Martchus commented 2 months ago

It looks really like things are broken on Syncthing Tray's side but it is hard to tell why. So reading the logs from stdout as described in https://github.com/Martchus/syncthingtray/issues/252#issuecomment-2063325731 and my next comment is not possible?

stale[bot] commented 2 weeks ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.