Connection troubleshooting
Diagnose a RepoTunnel connection without weakening the local security boundary.
Guides follow the current project source. Check the release notes for your installed version.
Public connection is not Ready
- Check Internet connectivity
- Check provider configuration
- Restart the configured connection from RepoTunnel
- Confirm the public health endpoint where applicable
- Run a real authenticated MCP tool call after transport health is restored
ChatGPT asks to reconnect
Use ChatGPT's reconnect/reauthorize flow and approve the RepoTunnel authorization request. A normal reconnect should not require deleting your approved project state.
Tools look stale
Refresh or rescan the RepoTunnel app/actions in the MCP client if RepoTunnel's MCP schema changed.
Diagnose each layer separately
First establish that RepoTunnel itself is running and has an approved workspace. Next inspect gateway/provider readiness, the exact public HTTPS endpoint, and OAuth authorization. Finally verify MCP tool discovery and a real workspace call.
If a public /health endpoint responds but tool discovery fails, inspect OAuth/DCR/PKCE and client configuration rather than assuming a working end-to-end connection.
Avoid an unsafe quick fix
Never bind the raw MCP gateway to a public interface or disable Host validation to work around a connection problem. Direct HTTPS reverse proxy configuration must adapt forwarded Host headers without weakening the local loopback guard.
After upgrading RepoTunnel
A client can keep an older cached MCP schema. Refresh or rescan actions after upgrading or switching the connector and then retest with list_workspaces. A missing action does not automatically mean the server failed to start.