FAQ
Answers to common setup, access, connection and configuration questions.
Do I need a VPN, public IP, inbound firewall rules, or port forwarding?
No. The publisher opens an outbound connection to the relay. It needs outbound network access and a reachable target service. See How it works.
Where do I get an API key?
Verify your account, then save the key shown after registration or create one in your account. Key secrets are shown only when created. Supply it through TUBU_TOKEN, YAML authtoken or --authtoken. See credential precedence.
Does my API key protect the public service?
No. It authorizes the publisher. HTTP tunnels are publicly accessible unless you configure a shared secret or application authentication. TCP callers do not need a Tubu key; the target protocol must authenticate them.
Why do I get 401 on a protected HTTP URL?
Send exactly one X-Tubu-Auth header containing the original secret, not its SHA-256 digest. Check the tunnel secret override and root secret. Browser WebSocket and EventSource clients cannot set this custom header. See HTTP secrets.
What if reservation times out while waiting for HTTPS?
The reservation remains in place. Rerun the same reserve command to resume the HTTPS check. If the relay reports that provisioning is unavailable, certificate provisioning must be available before a fourth level reservation can succeed.
Why does the public URL return 404?
Check the domain and confirm the publisher printed Tunnel ready and is still running. A disconnected or unknown tunnel is unavailable. A TCP tunnel does not serve application HTTP requests. If the tunnel is connected, the target application may also be the source of a 404.
Why do I get 502 or a failed TCP connection?
Check that the target is running and reachable from the publisher machine at the configured address and port. Test the target directly there. For HTTPS targets, check the certificate and hostname. The publisher uses a four second timeout while waiting for an HTTP target response or TCP target connection.
Can I connect SSH or a database directly to the public domain?
Run npx tubu-cli forward on the caller machine first, then connect your application to its 127.0.0.1 listener. Tubu does not expose a public raw TCP port. The SSH and database guides show both sides.
Why can the caller not bind its listener?
Another process may already use the port. Choose an available port from 1 through 65535 and use the same value in your application connection settings. The listener address must be 127.0.0.1, not localhost or 0.0.0.0.
Do file changes reload automatically?
No. Stop and restart the publisher after changing YAML. The CLI reads the file once. A lost publisher connection exits with an error and requires a restart; interrupted application sessions are not replayed.
Why does my API still receive the route prefix?
A route selects a destination but does not strip its prefix. Add a rewrite on that route. See Rewrite request paths.
What happens when I reach my limits?
New tunnels or reservations can be rejected when account limits are full. Monthly upload and download both count toward traffic. Exhausting traffic closes tunnels and prevents new tunnels until the quota resets or increases. Traffic resets on the first day of the month at 00:00 UTC. View current usage in your account.
How long does a reservation last?
A domain expires after more than 90 days from the last tunnel opening or reconnection, or the reservation date if never opened. Repeating reserve does not extend that period. A continuously open tunnel does not refresh the timestamp. Released names can be claimed by other accounts.
Why are --token and --tunnel rejected?
The current CLI uses --authtoken and explicit http or tcp commands, or --config for YAML. See CLI reference for supported syntax.