Edge Connectivity and Local Network Issues
Troubleshoot common local network issues that may cause the Edge device to disconnect or show unstable connectivity.
| Scenario or error | Likely meaning | Recommended next steps |
|---|---|---|
| Firewall, web filter, or security gateway is in the traffic path | A security appliance between the Edge device and the internet may be interfering with the connection. | Confirm whether there is a firewall or gateway such as Fortinet, Palo Alto, Check Point, Sophos, SonicWall, Cisco, Meraki, Zscaler, Netskope, or Cloudflare Gateway between the Edge device and the internet. |
| SSL / TLS inspection, HTTPS decryption, or DPI is enabled | Traffic inspection may be breaking or interfering with the long-running secure connection to Xyte cloud. | If any of these features are enabled, add *.xyte.io and specifically eu1.edge.xyte.io to the bypass / exclusion list so this traffic is not inspected. |
| Outbound idle-connection timeout is too short | The firewall or router may be closing long-running secure TCP / HTTPS connections after a few minutes of inactivity. | Check whether there is an outbound idle-timeout setting. If so, increase it to at least 1 hour for traffic to *.xyte.io, or exempt that destination from the timeout. |
| NAT / shared public IP exhaustion | If many devices share the same public IP, the firewall may occasionally run out of outbound ports under load. | Check firewall logs for messages such as NAT pool exhausted, no source port available, or similar, and share them if found. |
| DNS resolution may be inconsistent | DNS for eu1.edge.xyte.io may be returning different or unexpected addresses. | From the Edge device network, run the lookup several times and confirm whether the result stays consistent. Windows: nslookup eu1.edge.xyte.io Mac/Linux: dig eu1.edge.xyte.io or host eu1.edge.xyte.io |
| Host clock / time sync issue | If the host clock is inaccurate, or NTP is blocked, secure connections may fail intermittently. | Confirm that the host clock is accurate within a few seconds of real time and that outbound NTP traffic is not blocked. |
Updated about 3 hours ago