My Android phone is running the latest GrapheneOS and my computer is fully up-to-date Windows 10 Pro x64. This morning, I updated the phone to the latest Syncthing (1.19.0) and now I can’t sync to/from my Windows 10 device (SyncTrayzor v 1.1.28 Syncthing v1.19.0). On each device, the other shows as Disconnected.
On Android, the app has full access to local storage and the network. On Windows, the Windows Defender Firewall shows Syncthing.exe is allowed all TCP/UDP connections.
And, perhaps I should stop here? Could this be a SyncTrayzor issue since it hasn’t updated and Syncthing has?
But, just in case, I’ll include more details here:
The Syncthing log on Windows since starting up this morning (with one reboot) looks like:
[start] 06:26:15 INFO: syncthing v1.19.0 "Fermium Flea" (go1.17.6 windows-amd64) teamcity@build.syncthing.net 2022-01-24 03:45:54 UTC
[EMG2L] 06:26:16 INFO: My ID: [redacted]
[EMG2L] 06:26:17 INFO: Single thread SHA256 performance is 2047 MB/s using minio/sha256-simd (505 MB/s using crypto/sha256).
[EMG2L] 06:26:17 INFO: Hashing performance is 1247.89 MB/s
[EMG2L] 06:26:17 INFO: Overall send rate is unlimited, receive rate is unlimited
[EMG2L] 06:26:17 INFO: Using discovery mechanism: IPv4 local broadcast discovery on port 21027
[EMG2L] 06:26:17 INFO: Using discovery mechanism: IPv6 local multicast discovery on address [ff12::8384]:21027
[EMG2L] 06:26:17 INFO: QUIC listener ([::]:22000) starting
[EMG2L] 06:26:17 INFO: TCP listener ([::]:22000) starting
[EMG2L] 06:26:17 INFO: Ready to synchronize "Pixel 3 XL Main" ([redacted]) (sendreceive)
[EMG2L] 06:26:17 INFO: GUI and API listening on 127.0.0.1:8384
[EMG2L] 06:26:17 INFO: Access the GUI via the following URL: https://localhost:8384/
[EMG2L] 06:26:17 INFO: My name is "WIN10-DAVE-X570"
[EMG2L] 06:26:17 INFO: Device [redacted] is "Pixel 3 XL" at [dynamic]
[EMG2L] 06:26:18 INFO: Completed initial scan of sendreceive folder "Pixel 3 XL Main" ([redacted])
[EMG2L] 06:29:09 INFO: Pausing [redacted]
[EMG2L] 06:29:14 INFO: Resuming [redacted]
[EMG2L] 06:37:42 INFO: QUIC listener ([::]:22000) shutting down
[EMG2L] 06:37:42 INFO: TCP listener ([::]:22000) shutting down
[EMG2L] 06:37:42 INFO: Exiting
[start] 06:37:42 INFO: syncthing v1.19.0 "Fermium Flea" (go1.17.6 windows-amd64) teamcity@build.syncthing.net 2022-01-24 03:45:54 UTC
[EMG2L] 06:37:43 INFO: My ID: [redacted]
[EMG2L] 06:37:44 INFO: Single thread SHA256 performance is 2068 MB/s using minio/sha256-simd (509 MB/s using crypto/sha256).
[EMG2L] 06:37:44 INFO: Hashing performance is 1252.15 MB/s
[EMG2L] 06:37:44 INFO: Overall send rate is unlimited, receive rate is unlimited
[EMG2L] 06:37:44 INFO: Using discovery mechanism: IPv4 local broadcast discovery on port 21027
[EMG2L] 06:37:44 INFO: Using discovery mechanism: IPv6 local multicast discovery on address [ff12::8384]:21027
[EMG2L] 06:37:44 INFO: TCP listener ([::]:22000) starting
[EMG2L] 06:37:44 INFO: QUIC listener ([::]:22000) starting
[EMG2L] 06:37:44 INFO: Ready to synchronize "Pixel 3 XL Main" ([redacted]) (sendreceive)
[EMG2L] 06:37:44 INFO: GUI and API listening on 127.0.0.1:8384
[EMG2L] 06:37:44 INFO: Access the GUI via the following URL: https://localhost:8384/
[EMG2L] 06:37:44 INFO: My name is "WIN10-DAVE-X570"
[EMG2L] 06:37:44 INFO: Device [redacted] is "Pixel 3 XL" at [dynamic]
[EMG2L] 06:37:45 INFO: Completed initial scan of sendreceive folder "Pixel 3 XL Main" ([redacted])
From earlier in the log, it looks like the next thing that should be happening is “Established secure connection to…” But, it’s not.
The SyncTrayzor log on Windows is:
2022-02-07 08:08:55.2427 #11392 [Warn] SyncTrayzor.Services.UpdateManagement.UpdateChecker: Fetching updates failed with an error RestEase.ApiException GET "https://synctrayzor.antonymale.co.uk/version-check?version=1.1.28&arch=x64&variant=installed" failed because response status code does not indicate success: 404 (Not Found). Void MoveNext() at RestEase.Implementation.Requester.<SendRequestAsync>d__37.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at RestEase.Implementation.Requester.<RequestAsync>d__41`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at SyncTrayzor.Services.UpdateManagement.UpdateNotificationClient.<FetchUpdateAsync>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at SyncTrayzor.Services.UpdateManagement.UpdateChecker.<FetchUpdateAsync>d__7.MoveNext() RestEase.ApiException: GET "https://synctrayzor.antonymale.co.uk/version-check?version=1.1.28&arch=x64&variant=installed" failed because response status code does not indicate success: 404 (Not Found).
at RestEase.Implementation.Requester.<SendRequestAsync>d__37.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at RestEase.Implementation.Requester.<RequestAsync>d__41`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at SyncTrayzor.Services.UpdateManagement.UpdateNotificationClient.<FetchUpdateAsync>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at SyncTrayzor.Services.UpdateManagement.UpdateChecker.<FetchUpdateAsync>d__7.MoveNext()
2022-02-07 08:11:14.5881 #11392 [Info] SyncTrayzor.Services.MemoryUsageLogger: Working Set: 192MiB. Private Memory Size: 149MiB. GC Total Memory: 11MiB
2022-02-07 08:16:14.5872 #11392 [Info] SyncTrayzor.Services.MemoryUsageLogger: Working Set: 192MiB. Private Memory Size: 149MiB. GC Total Memory: 12MiB
2022-02-07 08:21:14.6000 #11392 [Info] SyncTrayzor.Services.MemoryUsageLogger: Working Set: 192MiB. Private Memory Size: 149MiB. GC Total Memory: 12MiB
2022-02-07 08:26:14.5997 #11392 [Info] SyncTrayzor.Services.MemoryUsageLogger: Working Set: 192MiB. Private Memory Size: 149MiB. GC Total Memory: 12MiB
2022-02-07 08:29:38.2359 #11392 [Warn] SyncTrayzor.Syncthing.Folders.FolderStateTransformer: Unknown folder sync state scan-waiting. Defaulting to Idle
2022-02-07 08:29:38.2359 #11392 [Warn] SyncTrayzor.Syncthing.Folders.FolderStateTransformer: Unknown folder sync state scan-waiting. Defaulting to Idle
2022-02-07 08:31:14.5911 #11392 [Info] SyncTrayzor.Services.MemoryUsageLogger: Working Set: 192MiB. Private Memory Size: 149MiB. GC Total Memory: 12MiB
2022-02-07 08:36:14.5995 #11392 [Info] SyncTrayzor.Services.MemoryUsageLogger: Working Set: 192MiB. Private Memory Size: 149MiB. GC Total Memory: 12MiB
2022-02-07 08:37:44.8597 #11392 [Warn] SyncTrayzor.Syncthing.Folders.FolderStateTransformer: Unknown folder sync state clean-waiting. Defaulting to Idle
2022-02-07 08:37:44.8597 #11392 [Warn] SyncTrayzor.Syncthing.Folders.FolderStateTransformer: Unknown folder sync state cleaning. Defaulting to Idle
2022-02-07 08:37:44.8597 #11392 [Warn] SyncTrayzor.Syncthing.Folders.FolderStateTransformer: Unknown folder sync state clean-waiting. Defaulting to Idle
2022-02-07 08:37:44.8597 #11392 [Warn] SyncTrayzor.Syncthing.Folders.FolderStateTransformer: Unknown folder sync state cleaning. Defaulting to Idle
The change log for the latest version of SyncTrayzor says it’s so minor that the update doesn’t happen automatically. I’m going to download the update manually and see if installing it helps.
I’ve updated SyncTrayzor to its latest version and even booted both devices into Safe Mode and back. Still doesn’t work. My next thing will be to try the official Syncthing application (if I can figure out how to work it).
Let me also add that the only means of discovery I’ve got turned on is “Local Discovery.” Nothing shows up in my pfSense log, either. But, then it shouldn’t since nothing should ever leave my local network.
I can’t figure out how to do a scrolling screenshot and I’m not sure how much you need. So, here’s 3 shots showing everything. I’m using only Local Discovery to make sure everything happens purely over my local network and nothing leaks out.
It does appear to be a local discovery issue. I re-read the documentation on Global Discovery and it seems safe enough. So, I enabled it on the phone and my computer. The devices found each other and synced.
It’s odd, though. My wife’s setup is still on purely local discovery and on her Pixel 4 XL has the Syncthing v1.18.3 and it continues to work.
EDIT: She’s on plain ol’ Google Android 12. But only the January update. Not February’s yet.
Might have to do with the app version, because v1.19.0 started targeting a new API level for Android. Maybe they keep old behavior for apps still targeting the older API.
