Tunnel troubleshooting

Run dockhive doctor 3000 (with your app’s port) first: it checks your sign-in, every region and your local app, and tells you what to fix.

Visitors see “The tunnel is up, but the local service isn’t answering”

The tunnel is connected but nothing answered on the address you exposed. Start your app (or check the port) and reload. For a server that only listens on another interface, expose host:port; for a local HTTPS server, expose https://localhost:<port>.

The app shows “Invalid host header” or the wrong site

Your dev server checks the Host header. Run with --host-header rewrite.

“Connection lost. Reconnecting…”

Your network dropped or the region went away. The CLI reconnects on its own and keeps your URL; if your region stays down it moves to the next-fastest region automatically (turn that off with --no-failover). dockhive regions shows each region’s status.

Not signed in, or the wrong account

Run dockhive whoami. Sign in again with dockhive login. If DOCKHIVE_TOKEN is set in your environment, it’s used instead of your stored sign-in.

“command not found: dockhive” right after installing

Open a new terminal so it picks up the PATH change, or run the export PATH=... line the installer printed.

A limit was reached

Stop a running tunnel, release a name with dockhive names release <name>, or upgrade your plan.

Visitors see “Nothing is live here”

The name isn’t connected to a tunnel: it may have been released, or never existed. See Limits and troubleshooting.

Collect logs

Run with --log stderr --log-level debug (or --log tunnel.log) to capture connection logs.

Still stuck?

Include the output of dockhive doctor and dockhive version when you contact us.