Password-Protect a Local TCP Service with Ngrok Authtunnel
Use Ngrok Authtunnel to require HTTP Basic Auth at the edge before forwarding TCP traffic to a local service, keeping unauthenticated clients off your local port.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Use Ngrok Authtunnel to require HTTP Basic Auth at the edge before forwarding TCP traffic to a local service, keeping unauthenticated clients off your local port.
Ngrok TCP tunneling lets you expose local SSH or database services to the internet via encrypted tunnels, but free-tier limits and firewall exposure require careful handling.
TCP Session Management The ngrok agent establishes a persistent connection to the cloud service to route traffic to a local TCP port. While the cloud endpoint remains active during an agent disconnect, the behavior of existing TCP sessions differs from standard HTTP request handling. Session Continuity Constraints When the ngrok agent is restarted or the loc
ngrok tunnels establish a persistent connection between the local agent and the ngrok cloud service to route traffic to local endpoints. While the agent includes automatic reconnection logic to restore tunnels after network loss, the behavior during silent timeouts—such as those caused by intermediate firewalls or proxy drops—remains ambiguous. In TCP tunnel