Support
This guide covers the issues that come up most often when running tunnels and endpoints.
Endpoint health status
The Endpoint Health card on the Overview tab shows a status badge for the latest probe (health checks are off by default and enabled per-endpoint):
- Healthy — the last probe returned 2xx, 401, or 403 (401/403 still count as up — the endpoint is reachable, it just requires auth).
- Unhealthy — the last probe returned a 4xx (other than 401/403) or 5xx.
- Error — the probe got no HTTP response (connection refused, TLS error, or timeout).
- No Agent Connected — no tunnel agent is online for this endpoint; probing is paused until an agent reconnects.
- Awaiting first probe — health checks were just enabled and the first probe has not run yet.
My tunnel keeps disconnecting
Check your internet connection stability, make sure the agent is up to date, and review the agent logs for specific error messages. The agent also reconnects through fallback tunnel-servers automatically if its region becomes unreachable. If the issue persists, create a support ticket.
My custom domain is not working
A custom domain must reach active status before an endpoint can use it. For a manual domain, confirm the * CNAME record is in place at your DNS provider and click Validate CNAME; DNS changes can take a few minutes to propagate, so retry if it is not yet resolving. See Use a custom domain.
Still need help?
If none of the above resolves your issue, open a ticket from the support center and our team will assist you.