ngrok browser warning: what it is and how to skip it

The page that says "You are about to visit … This website is served for free through ngrok.com" is ngrok's interstitial, error code ERR_NGROK_6024. ngrok shows it in front of HTML browser traffic on free accounts, to deter phishing. Skip it by sending the ngrok-skip-browser-warning request header with any value, by using a non-standard User-Agent, or with any paid ngrok plan. Webhooks and other programmatic clients don't get it.

Sources: ngrok's free plan limits and ERR_NGROK_6024 pages, checked November 16, 2026.

Skip it: copy-paste fixes

From the command line:

curl -H "ngrok-skip-browser-warning: true" https://your-assigned-name.ngrok-free.dev/api/items

From JavaScript in the browser, with fetch or Axios:

const res = await fetch('https://your-assigned-name.ngrok-free.dev/api/items', {
  headers: { 'ngrok-skip-browser-warning': 'true' },
})

// Axios
axios.get('https://your-assigned-name.ngrok-free.dev/api/items', {
  headers: { 'ngrok-skip-browser-warning': 'true' },
})

From a server-side client, a User-Agent of your own works too:

import requests

requests.get(
    "https://your-assigned-name.ngrok-free.dev/api/items",
    headers={"User-Agent": "MyApp/0.0.1"},
)

ngrok accepts any value for the header.

If your front end is on another origin

A custom header such as ngrok-skip-browser-warning makes a cross-origin request "non-simple", so the browser first sends a CORS preflight (OPTIONS) and only sends the real request if your API allows that header. Add it to the allowed headers, for example with the Express cors package:

app.use(cors({
  origin: 'http://localhost:5173',
  allowedHeaders: ['Content-Type', 'ngrok-skip-browser-warning'],
}))

Without that, the browser reports a CORS error rather than the warning page. MDN explains preflights.

Who sees it

According to ngrok's docs:

  • Only free accounts. Any paid plan removes the page.
  • Only HTML browser traffic. ngrok says it "does not impact users serving APIs or accessing ngrok endpoints programmatically."
  • Once per visitor, per domain, for 7 days. After the visitor clicks Visit, a cookie suppresses it for that domain for a week.

ngrok doesn't publish exactly how it tells browser traffic apart. Its docs give two ways to opt out, the header and a non-standard User-Agent, and they show the header in fetch, Axios, SuperAgent and jQuery examples, which is where people usually meet it: a page's JavaScript calling an API on an ngrok URL.

Why it usually doesn't affect webhooks

Stripe, GitHub, Slack and other webhook senders post from their servers with their own User-Agent, not from a browser. That is the programmatic traffic ngrok's docs exclude, so the interstitial isn't what stops a webhook. If deliveries fail, look at the endpoint being offline (ERR_NGROK_3200), a monthly usage limit, or your handler's response. Our webhook testing guide covers those.

Where the page does get in the way is browser code: a front end calling your API on the ngrok URL with fetch or Axios, before anyone has clicked through in that browser. The header, or a paid plan, fixes that.

tunnl.gg has a similar page

To be clear about our own service: tunnl.gg's free tier also shows a warning page to browsers, for the same reason, phishing. Here's how the two compare, based on ngrok's docs and tunnl.gg's open-source server code:

ngrok freetunnl.gg free
Who gets itHTML browser trafficRequests whose User-Agent contains Mozilla, Chrome, Safari, Firefox, Edge or Opera, whatever the method
What happensInterstitial pageRedirect to a warning page on tunnl.gg, then back to your URL
Acknowledgement lasts7 days per domain1 day per subdomain; 7 days on stable URLs
Skip headerngrok-skip-browser-warningtunnl-skip-browser-warning
Other way to skipNon-standard User-AgentA User-Agent without those browser names
Webhooks, curl, SDKsNot affectedNot affected, unless they send a browser-like User-Agent
Removed byAny paid planPro, $6/month or $60/year

The practical difference: tunnl.gg decides by User-Agent alone, so browser fetch and WebSocket requests are redirected too until the visitor has accepted the page in that browser. After that, requests from pages on the tunnel URL itself carry the cookie; for calls from another origin, send the header:

fetch('https://brave-fox-7c41e09b.tunnl.gg/api/items', {
  headers: { 'tunnl-skip-browser-warning': '1' },
})

The same CORS rule applies: your API has to allow tunnl-skip-browser-warning in its allowed headers. Free tunnl.gg tunnels also close after 2 hours idle or 24 hours in all, which ngrok's free endpoints don't. For a broader comparison, see tunnl.gg as an ngrok alternative and compare localhost tunnels.

Common questions

Does the ngrok browser warning affect webhooks?

No. ngrok shows the interstitial in front of HTML browser traffic on free accounts and says it doesn't affect APIs or programmatic access. Webhook senders such as Stripe and GitHub call your URL from their servers, so they reach your app directly.

Why does my fetch call return HTML instead of JSON?

On a free ngrok URL, a request from browser JavaScript can get the interstitial's HTML instead of your API's response, which then fails to parse as JSON. Send the ngrok-skip-browser-warning header with the request, and allow that header in your API's CORS settings if the page is on a different origin.

What value should ngrok-skip-browser-warning have?

Any value. ngrok's docs say to send the header with any value, so "true" or "1" both work.

How often will visitors see the ngrok warning page?

Once per domain every 7 days. After a visitor clicks Visit, ngrok sets a cookie that suppresses the page for that domain for a week, in that browser.

Can I remove the ngrok warning page without paying?

Not for everyone who visits. The header and a custom User-Agent only help clients you control, such as your own front end or scripts. Removing it for all visitors needs a paid ngrok plan, which starts with Hobbyist at $8/month billed yearly or $10 month to month, as listed on ngrok's pricing page on November 16, 2026.

Last updated