Only one tunnel runs at a time
Multiple agents trying to connect on an account limited to a single concurrent session, usually because a stale ngrok process is still running on a forgotten machine.
Session cleaned up, tunnels stable
Running ngrok tunnels?
ngrok started life as a developer tool for exposing a local port and has grown into a full ingress platform with edges, reserved domains, OAuth, mTLS and traffic policy. That shift means a lot of teams are using it for production webhooks, demos, and B2B integrations without really planning for what happens when a tunnel drops or a policy change silently breaks auth.
What it is
ngrok is an ingress-as-a-service platform. A small agent process establishes an outbound tunnel to ngrok's edge, and inbound HTTPS, TCP or TLS traffic on a public hostname is routed back down that tunnel to a local service. You get a public URL without touching firewalls, DNS or load balancers.
The platform has grown well beyond the free single-tunnel sweet spot. It now covers reserved domains, traffic policy rules, OAuth and SAML enforcement, IP restrictions, mTLS, and stable regional edges. That makes it useful not just for webhook development but also for production ingress to on-prem or edge devices that cannot easily expose a public endpoint on their own.
The honest version
No technology is all upside. This is where ngrok earns its place and where it tends to cause trouble.
Sound familiar?
The ngrok problems that bring people to us, and what you have once each one is fixed.
Multiple agents trying to connect on an account limited to a single concurrent session, usually because a stale ngrok process is still running on a forgotten machine.
Session cleaned up, tunnels stable
A reserved hostname that is not currently claimed by a running agent, either because the agent is down or because the hostname in the tunnel config was mis-typed.
Reserved domain bound correctly
ngrok connects fine, but the upstream port is not listening, often because the dev server crashed or the agent is pointed at the wrong port after a config change.
Agent and app aligned
A newly added require-oauth or ip-restriction rule misordered against a bypass rule, so legitimate traffic is denied before the allow rule evaluates.
Policy order corrected
A chatty webhook provider bursting more connections than the current plan allows, surfacing as intermittent 429-shaped failures that are actually ngrok tier limits.
Plan or policy sized to real load
A client certificate that was renewed on one side and not published on the other, or an edge expecting a CA that was rotated without updating the trust bundle.
mTLS trust aligned
A video or file transfer through the tunnel burning quota far faster than webhook traffic, pushing the account over its monthly cap mid-cycle.
Traffic classified and plan sized
What we do
Call us for one dropping tunnel, or hand us the whole ingress setup.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
For the right workloads, yes. B2B webhooks, admin tools, IoT ingress and remote support flows are common production uses. For public consumer traffic at scale it is less typical. The real questions are compliance posture, acceptable extra latency, and whether a tunnel-based ingress is a dependency your business is comfortable having.
The usual suspects are an aggressive local firewall killing the long-lived outbound connection, a plan that limits concurrent sessions, or a flaky residential network. Running the agent on a small stable host with a reserved domain and clear logs usually turns a flaky integration into a boring one.
Yes. Paid tiers let you point your own domain at an ngrok edge with a CNAME, and reserved domains hold the mapping even when the agent restarts. Setting that up properly, including the TLS certificate side, is one of the most common bits of help we are asked for.
Traffic policy is ngrok's rule engine for inbound and outbound requests at the edge: auth enforcement, IP restrictions, rate limits, transformations. Not every account needs it, but if your integration demands OAuth, SAML or hard rate limits before traffic touches your app, it is cleaner than writing it yourself.
Both are serious options. ngrok has richer traffic policy and request inspection. Cloudflare Tunnel integrates tightly with the rest of Cloudflare's security and performance products, and the bandwidth story is often better for high-volume traffic. The choice usually comes down to the rest of your stack rather than the tunnel features themselves.
First estimates are complimentary. Describe what you are tunnelling, how much traffic it sees and what is going wrong, and you get a quote before any agent configuration is touched.
Free estimate
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: