r/zerotier • u/catastrophize13 • 18h ago
Question Diagnostic guidance requested: intermittent ZeroTier connection timeouts on Windows–Linux connection
We use ZeroTier for remote access to a Fieldbot agricultural controller. I believe our account is on the free plan and understand direct support may be limited. Could you provide diagnostic guidance or or documentation resource?
We are investigating intermittent connection failures between a Windows laptop on home Wi-Fi and a Linux controller connected through a cellular gateway. Both endpoints run ZeroTier 1.16.2.
We completed an eight-hour observation on November 20–21, 2026, with no application-file transfers or camera retrieval running. We made no repairs, service restarts, or configuration changes during the observation.
Results
- Remote SSH and dashboard requests each passed 473 of 477 attempts. Both services failed during the same four samples, at TCP connection establishment.
- The controller’s local dashboard and local SSH-banner checks passed in all 480 aligned samples.
- Laptop public-internet checks passed 238 of 238 attempts.
- Both ZeroTier processes and the controller’s boot identity remained unchanged.
Two distinct failure patterns
- After disconnecting laptop Ethernet: Initial remote checks failed, and both endpoints retained their previous wired peer paths. Windows then selected its ordinary Wi-Fi default route for the controller’s virtual address during three samples. Approximately five minutes after unplugging, the ZeroTier route was selected again and both services responded without intervention.
- Later, with Ethernet remaining disconnected: At 11:10 PM November 20 and 1:30 AM November 21, both remote services timed out during TCP connection establishment. The expected ZeroTier route remained selected. Both services passed at the following minute’s check and continued passing at the next check, without intervention.
Before, during, and after the later failures, the exact-peer records at both endpoints had empty direct-path lists and latency -1. TCP fallback was not active in the recorded status samples. Root-contact activity was recorded over IPv4 on the laptop and IPv6 on the controller, but we could not identify the actual forwarding path for the application traffic.
Measurement limitations
- Checks ran once per minute, so exact outage durations are unknown.
- After accounting for clock differences, the nearest controller-local checks began approximately 14 seconds after the laptop checks.
- Laptop public-internet checks passed immediately before and after the later failures, but were not scheduled in the exact failing minutes.
- The controller has two IPv4 default routes. Its public IPv4 TCP control to
1.1.1.1:443failed throughout the observation—including during successful remote access and during preflight—through either selected gateway. We therefore cannot use that control to establish controller-side internet health. - We had no independent public IPv6 control or packet capture during this run.
Our question
What supported diagnostic should we collect at both endpoints during a recurrence to identify the actual forwarding path and distinguish endpoint handling from packet loss in transit?
Specific commands or trace points, guidance on correlating the two endpoints, and advice on which output is appropriate to share would be helpful. We are not assuming ZeroTier itself is the cause; we want evidence that identifies where the connection fails.
I’ve also emailed ZeroTier support. I’m looking for diagnostic guidance, not assuming ZeroTier is the cause.

