Web (Gateway)
The Gateway serves its browser surfaces from the same port as the Gateway WebSocket:- Control UI v2, the operator console, at the root (
/) by default (gateway.controlUiV2.basePathremounts it) - the web client at
/v2/clientwhengateway.webClient.enabled: true(gateway.webClient.basePathremounts it)
Webhooks
Whenhooks.enabled=true, the Gateway also exposes a small webhook endpoint on the same HTTP server.
See Gateway configuration → hooks for auth + payloads.
Config (default-on)
The operator console is served by default. Control it via config:Tailscale access
Integrated Serve (recommended)
Keep the Gateway on loopback and let Tailscale Serve proxy it:https://<magicdns>/(or your configured console path)
Tailnet bind + token
http://<tailscale-ip>:18789/(or your configured console path)
Public internet (Funnel)
Security notes
- Gateway auth is required by default (token/password or Tailscale identity headers).
- Non-loopback binds still require a shared token/password (
gateway.author env). - The wizard generates a gateway token by default (even on loopback).
- The UI sends
connect.params.auth.tokenorconnect.params.auth.password. - For non-loopback console deployments, set
gateway.controlUi.allowedOriginsexplicitly (full origins). Without it, gateway startup is refused by default. This covers the Control UI v2 console. gateway.controlUi.dangerouslyAllowHostHeaderOriginFallback=trueenables Host-header origin fallback mode, but is a dangerous security downgrade.- With Serve, Tailscale identity headers can satisfy Control UI/WebSocket auth
when
gateway.auth.allowTailscaleistrue(no token/password required). HTTP API endpoints still require token/password. Setgateway.auth.allowTailscale: falseto require explicit credentials. See Tailscale and Security. This tokenless flow assumes the gateway host is trusted. gateway.tailscale.mode: "funnel"requiresgateway.auth.mode: "password"(shared password).