Troubleshooting
Fix a tunnel that is not working
Match what you see to a cause and a fix.
- Applies to
- Connector 0.2.0; all plans
- Time
- About 10 minutes
- What it changes
- Restarting the connector briefly disconnects the tunnel.
- Last reviewed
- , by Product documentation
What to know before you start
- Run Tunnel Doctor first when you can. It names the failing layer, and the steps below follow its codes.
You are done when
- The public address shows your app, and the tunnel shows Live in the dashboard.
If something goes wrong
- The address answers 404 with no page.
- No connector is serving this address. Check the tunnel in the dashboard: if it is paused or stopped choose Resume, and start the connector with the command under Connect an app. If you ran the connector with only a port, the address is temporary and changes each time.
- The address answers 502 or 503.
- The connector is connected but could not reach your app. Make sure your app is running and that the --origin address matches the port it listens on, for example 127.0.0.1:3000. A local server that only accepts HTTPS is not supported.
- The address times out.
- Your app is slow to answer. By default the connector waits up to 10 minutes for a response to start and 2 minutes with no data. Check whether your app is stuck, or raise the wait with --origin-timeout.
- The page loads but looks unstyled, or says Blocked request.
- Your development server may be refusing the tunnel's address. Run Tunnel Doctor; it shows the line to add for Vite or Next.js with your address filled in. See the framework guides.
- The address asks for a password you did not expect.
- The tunnel has a password or token. Open the address in a private window and sign in, or send the token header. Tunnel Doctor reports this as checked up to the password prompt.
- The address answers 429.
- A tunnel is limited to its plan's requests a minute (120 on Free) and the workspace to its monthly transfer. The relay answers 429. Wait a minute, or see Plans and limits for the allowance.
- The address answers 410 and says it was disabled.
- The tunnel's own address was disabled for violating the Acceptable Use Policy. If you think this is a mistake, contact support with the tunnel address.
- The connector fails to start or says it is not signed in.
- The connector is signed out, or it cannot reach the service. Run the doctor command and the status command, then sign in again with the login command.
Undo or clean up
- None.
Related
This page is part of Diagnose and fix. Still stuck? Contact support.