Synctrayzor displays "Syncthing starting" with white screen
See original GitHub issueSynctrayzor version: 1.1.24 Syncthing version: v1.10.0, Windows (64 bit) “Fermium Flea” Windows version: Windows 10 x64 Version 2004 Build 19041.508 Sidenote: I don’t recall Windows, Synctrayzor, Syncthing, to have been updated recently, everything was normal this morning, and after a reboot, this problem appeared. I haven’t changed any folder settings recently either.
- Open Synctrayzor
- Synctrayzor starts, displays “Syncthing starting” and stays like this for 10 minutes or so until error (below)
- In the meantime, all menu bar items under “Syncthing” are greyed out except “Kill all syncthing processes”
- Tray icon: Grey, tasks relating to syncthing greyed out
- Check syncthing is running normally: Change GUI listen address to 0.0.0.0:8384 from default localhost:8384 (File/Settings/Syncthing), syncthing now accessible in browser and appears to be running normally (I don’t know why localhost doesn’t work and 0.0.0.0 does)
- After a while Synctrayzor opens error message "Unable to start Syncthing: Unexpected exception while starting Syncthing: Syncthing didn’t connect after 00:10:00. Please see Syncthing’s console output for clues. (This doesn’t always appear after 10 minutes, sometimes it doesn’t appear)
[monitor] 19:21:28 INFO: Log output saved to file "C:\Users\**\AppData\Local\Syncthing\syncthing.log"
[start] 19:21:28 INFO: syncthing v1.10.0 "Fermium Flea" (go1.15.2 windows-amd64) teamcity@build.syncthing.net 2020-09-15 17:38:23 UTC
[start] 19:21:28 INFO: Using large-database tuning
[**] 19:21:28 INFO: My ID: **
[**] 19:21:29 INFO: Single thread SHA256 performance is 1695 MB/s using minio/sha256-simd (404 MB/s using crypto/sha256).
[**] 19:21:29 INFO: Hashing performance is 986.66 MB/s
[**] 19:21:29 INFO: Overall send rate is unlimited, receive rate is unlimited
[**] 19:21:29 INFO: Using discovery mechanism: global discovery server https://discovery.syncthing.net/v2/?noannounce&id=LYXKCHX
[**] 19:21:29 INFO: Using discovery mechanism: global discovery server https://discovery-v4.syncthing.net/v2/?nolookup&id=LYXKCHX
[**] 19:21:29 INFO: Using discovery mechanism: global discovery server https://discovery-v6.syncthing.net/v2/?nolookup&id=LYXKCHX
[**] 19:21:29 INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint) starting
[**] 19:21:29 INFO: Using discovery mechanism: IPv4 local broadcast discovery on port 21027
[**] 19:21:29 INFO: Using discovery mechanism: IPv6 local multicast discovery on address [ff12::8384]:21027
[**] 19:21:29 INFO: Ready to synchronize "**"
[**] 19:21:29 INFO: Ready to synchronize "**"
[**] 19:21:29 INFO: GUI and API listening on [::]:8384
[**] 19:21:29 INFO: Access the GUI via the following URL: http://127.0.0.1:8384/
[**] 19:21:29 INFO: My name is "**"
[**] 19:21:29 INFO: Device ** is "**" at [dynamic]
[**] 19:21:29 INFO: Device ** is "**" at [dynamic]
[**] 19:21:29 INFO: Device ** is "**" at [dynamic]
[**] 19:21:29 INFO: QUIC listener ([::]:22000) starting
[**] 19:21:29 INFO: TCP listener ([::]:22000) starting
[**] 19:21:37 INFO: Completed initial scan of sendreceive folder "**"
[**] 19:21:40 INFO: New NAT port mapping: external TCP address ** to local address 0.0.0.0:22000.
[**] 19:21:40 INFO: New NAT port mapping: external TCP address ** to local address 0.0.0.0:22000.
[**] 19:21:40 INFO: New NAT port mapping: external TCP address ** to local address 0.0.0.0:22000.
[**] 19:21:40 INFO: Detected 3 NAT services
[**] 19:21:42 INFO: Completed initial scan of sendreceive folder "**"
[**] 19:21:44 INFO: Established secure connection to ** at **/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256
[**] 19:21:44 INFO: Device ** client is "syncthing v1.10.0" named "**" at **/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256
[**] 19:21:49 INFO: quic://0.0.0.0:22000 detected NAT type: Port restricted NAT
[**] 19:21:49 INFO: quic://0.0.0.0:22000 resolved external address quic://** (via stun.syncthing.net:3478)
[**] 19:22:02 INFO: Established secure connection to ** at **/relay-client/TLS1.3-TLS_AES_128_GCM_SHA256
[**] 19:22:02 INFO: Device ** client is "syncthing v1.10.0" named "**" at **/relay-client/TLS1.3-TLS_AES_128_GCM_SHA256
[**] 19:23:24 INFO: Joined relay relay://218.72.124.179:22067
[**] 19:44:19 INFO: Connection to ** at **/relay-client/TLS1.3-TLS_AES_128_GCM_SHA256 closed: reading length: EOF
Let me know what more information I need to provide to contribute
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
WebUI is sometimes blank · Issue #292
Occasionally (after a long syncthrayzor's uptime period), opening main UI shows blank white page. Waiting a long period does nothing, ...
Read more >Blank SyncTrayzor GUI Windows 10
On Box #2, the SyncTrazor GUI is entirely blank. Syncthing is still running (files are syncing in the background), but the main GUI...
Read more >Synctrayzor displays "Syncthing starting" with white screen
Synctrayzor displays "Syncthing starting" with white screen · Open Synctrayzor · Synctrayzor starts, displays "Syncthing starting" and stays ...
Read more >Has anyone experienced this behavior from SyncTrayzor in ...
From time to time it pops up on the upper-left corner of the screen, stays in front of other open apps and you...
Read more >SyncTrayzor is an open source Syncthing client for Windows
The Syncthing console is displayed at the bottom of the SyncTrayzor interface, maintains a log of all events that have been recorded.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
And it’s working again. What other information would you have asked me to provide in order to troubleshoot more effectively?
Closing as explained