Debugging

Tools and techniques for diagnosing tunnel issues.

Local Inspector

Run the CLI with --inspect:

binboi http 3000 --inspect

Open http://localhost:4040. You'll see every request, response, header, and body in real time.

Verbose Mode

binboi http 3000 --verbose

Prints connection events, retries, and protocol-level errors to stderr.

Web Dashboard

The dashboard shows:

• Tunnels — currently active tunnels and their endpoints
• Requests — last 24h of captured requests (longer on Pro+)
• Logs — control-plane events (connect, disconnect, errors)

Common Issues

error: connection refused — your local server isn't running on the port you specified. Start it first, then run binboi.

error: failed to authenticate — your token is missing or revoked. Run binboi login --token ... again.

error: tunnel limit reached — your plan caps concurrent tunnels. Close existing tunnels or upgrade.

error: subdomain taken — someone else is using that reserved subdomain. Pick another or upgrade to reserve it permanently.

No requests in dashboard — open the public URL in a private browser window (caches can hide requests) and check the response code.

See Also

• Troubleshooting — known errors and fixes
• Bugs — report a problem