Troubleshooting
Separate target reachability, endpoint state, Relay availability, browser policy, WebSocket upgrade, TCP authentication, and plan limits before changing application code.
Before you begin
Collect the endpoint type, source target, current status, selected Relay region, public address, expected client, and exact error without including passwords, tokens, or private credentials.
Shortest path
pubto status
pubto listCheck the source first
Confirm that the publishing computer can reach the selected port, file, directory, or service. A stopped process, changed port, sleeping computer, or inaccessible LAN target cannot be repaired by the public address.
Check endpoint state
Verify that the endpoint is Running, has not expired, still uses the intended address, and has remaining request, traffic, visitor, duration, and connection allowance.
Check the client policy
For browser APIs, inspect CORS and CSRF responses; for WebSockets, inspect the Origin and 101 upgrade; for TCP, use the correct host, allocated port, TLS mode, and application credentials.
Before you share
- Source works from the publishing computer
- Endpoint is running and within limits
- Correct protocol and client are used
- No secret was included in diagnostics
If a public HTTP address returns an application 4xx or 5xx, the publication path may be working and the source application may be rejecting the request.