OpenClaw gateway.tailscale_funnel: What It Means and How to Switch to Serve
Published 2026-10-20 · Updated 2026-10-20 · By The Is My Agent Safe team
Short answer
OpenClaw is publishing your Gateway to the public internet through Tailscale Funnel. Fix it first if you don't need public access: stop the Gateway, set gateway.tailscale.mode to serve (tailnet only) or off, start the Gateway, check tailscale funnel status and run openclaw security audit --deep again.
- OpenClaw rates gateway.tailscale_funnel critical: "Public internet exposure".
- Fix: set gateway.tailscale.mode to serve (tailnet-only) or off, then check tailscale funnel status for any Funnel route OpenClaw doesn't manage.
- gateway.tailscale_serve is info only. It tells you the Gateway is reachable from your tailnet.
- If you keep Funnel, OpenClaw requires password auth and its docs say to avoid Funnel for browser control.
Paste your audit: run openclaw security audit --deep and paste the output into our free check for a red/amber/green result with the most important finding first (Limits of the check).
What should I do first?
If you don't need people outside your tailnet to reach the Gateway, switch to Serve:
openclaw gateway stop openclaw config set gateway.tailscale.mode serve # or: off openclaw config validate openclaw gateway start tailscale funnel status openclaw security audit --deep
OpenClaw's Tailscale docs describe the modes:
| Mode | Behavior |
|---|---|
serve | "Tailnet-only Serve via tailscale serve. The gateway stays on 127.0.0.1." |
funnel | "Public HTTPS via tailscale funnel. Requires a shared password." |
off (default) | "No Tailscale automation." |
OpenClaw's config docs say config set needs the Gateway stopped, which is why the commands stop it first. The same Tailscale docs say OpenClaw holds Funnel as a foreground claim and "stopping or losing the Gateway releases it automatically".
tailscale funnel status comes from Tailscale's own docs. Use it to confirm nothing is still public. OpenClaw's docs say off "means OpenClaw is not managing Serve or Funnel. It does not mean the local Tailscale daemon is stopped or logged out." A Funnel route set up outside OpenClaw can still point at the Gateway, and this finding won't show it.
When the audit comes back without gateway.tailscale_funnel, you're done with this finding. With serve you'll see gateway.tailscale_serve instead, which is info only.
What changes for you after switching?
The public Funnel URL stops working for anyone outside your tailnet. Devices on your tailnet open the Gateway at https://<magicdns>/, as the Tailscale docs show. Anyone who used the public URL needs to join your tailnet, or you need another way in that you've chosen on purpose.
With Serve, OpenClaw can let tailnet users sign in to the Control UI using Tailscale identity instead of a token. The same docs say "if untrusted local code may run on the same host, set gateway.auth.allowTailscale: false and require token/password auth instead."
What does gateway.tailscale_funnel mean?
OpenClaw's security audit checks page lists it as critical: "Public internet exposure". The setting it points to is gateway.tailscale.mode.
In OpenClaw 2026.10.5's source, the finding appears whenever gateway.tailscale.mode is funnel. Its detail line is fixed text:
gateway.tailscale.mode="funnel" exposes the Gateway publicly; keep auth strict and treat it as internet-facing.
OpenClaw's own suggested fix is:
“Prefer tailscale.mode="serve" (tailnet-only) or set tailscale.mode="off".”
If you need Funnel on purpose
Some setups need a public URL. In that case, keep this finding and follow OpenClaw's Tailscale docs:
- Funnel "refuses to start unless auth mode is
password". OpenClaw's docs say to "preferOPENCLAW_GATEWAY_PASSWORDover committing a password to disk". - "Avoid Funnel for browser control."
- Funnel needs Tailscale v1.38.3+, MagicDNS, HTTPS enabled and a funnel node attribute.
OpenClaw still rates it critical, so the audit will keep reporting it. Our guide to audit false alarms covers how to record a deliberate choice instead of hiding it.
What if someone may have used the public URL?
The finding describes your config, not an event. If you think someone reached the Gateway through Funnel, follow the rollback plan in OpenClaw's exposure runbook in full. It starts with a config that puts the Gateway back on loopback, turns off DMs on chat channels, and denies host exec and elevated tools. Then:
- Stop public forwarding, Tailscale Funnel, or reverse proxy routes.
- Rotate Gateway tokens and passwords and affected integration credentials.
- Remove
"*"and unexpected senders from allowlists. - Review recent audit logs, run history, tool calls and config changes.
- Re-run
openclaw security audit --deep. - Re-enable access with the narrowest pattern that works.
Could it be a false alarm?
The check reads one setting, so it's rarely wrong. Confirm it:
openclaw config get gateway.tailscale tailscale funnel status
If mode is funnel, the finding matches your config.
The opposite case is more likely. Because the check only reads OpenClaw's config, a Funnel route someone set up by hand doesn't produce this finding. tailscale funnel status shows those.
What our free check covers
The free check at /check is paste-only. We check the text you paste: your openclaw security audit output. The check never connects to your Gateway or your tailnet, so it can't see Funnel routes that OpenClaw doesn't manage. Nothing is installed into the agent you're checking. Green means no issues found in the checks we ran.
The free check puts the most important finding first, in plain English. The full report explains every finding and lists the fixes in order. The check doesn't detect malicious skills. We don't review the code inside skills or MCP servers ourselves, beyond what OpenClaw's own audit reports. The check is free, and a full report is $29. See Limits of the check.
Frequently asked questions
What does gateway.tailscale_funnel mean?
gateway.tailscale.mode is funnel, so OpenClaw is using Tailscale Funnel to put the Gateway on the public internet. The audit detail says it "exposes the Gateway publicly". OpenClaw rates it critical.
How do I fix gateway.tailscale_funnel?
Stop the Gateway, run openclaw config set gateway.tailscale.mode serve (or off), start the Gateway and re-run openclaw security audit --deep. Then run tailscale funnel status to confirm no other Funnel route still points at the Gateway.
What does gateway.tailscale_serve mean?
It's an info finding. gateway.tailscale.mode is serve, so OpenClaw serves the Gateway over HTTPS to devices on your tailnet, not through Funnel. Nothing needs fixing unless you didn't mean to turn it on. tailscale funnel status shows any public route set up outside OpenClaw.
What if someone may have used the public URL?
Follow the full rollback plan in OpenClaw's exposure runbook. Its steps include putting the Gateway back on loopback, turning off direct messages on your chat channels, denying host exec and elevated tools, stopping public forwarding and Tailscale Funnel, rotating Gateway tokens, passwords and affected integration credentials, removing "*" and unexpected senders from allowlists, reviewing audit logs, run history, tool calls and config changes, re-running the audit, and re-enabling access with the narrowest pattern that works.
Can your free check see my Tailscale setup?
No. We check the text you paste, which is where this finding comes from. The check never connects to your Gateway or your tailnet, so it can't see Funnel routes that OpenClaw doesn't manage.
Sources
- OpenClaw docs: security audit checks (checkId catalog)
- OpenClaw docs: Tailscale (Serve and Funnel)
- OpenClaw docs: exposure runbook (rollback plan)
- OpenClaw docs: openclaw config (CLI)
- Tailscale docs: tailscale funnel command
- OpenClaw source v2026.10.5: src/security/audit-gateway-config.ts (where the check is defined)
Get the plain-English agent security brief
Agents & AI Security, explained: a short, plain-English email when we have something useful. Free. Unsubscribe any time.
We'll only use your email to send the newsletter. The newsletter is sent by beehiiv, which records opens and link clicks. Privacy policy.