1008 error with tailscale serve
✅Solved
I changed my config to use tailscale serve and while the gateway is running and the agent is available on telegram, I cannot get the dashboard to go online. I can connect to it with my tailscale full domain name, but I am getting a 1008 pairing required error.
The gateway is showing these errors:
14:31:49 [ws] Proxy headers detected from untrusted address. Connection will not be treated as local. Configure gateway.trustedProxies to restore local client detection behind your proxy.
14:31:50 [ws] closed before connect conn=d7130b6c-0569-4cb6-a78f-ff3737699ac2 remote=127.0.0.1 fwd=redacted origin=<redacted> host=<redacted> ua=Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Safari/537.36 code=1008 reason=pairing required
here is my current config:
"gateway": {
"port": 18789,
"bind": "loopback",
"mode": "local",
"tailscale": {
"mode": "serve"
},
"auth": {
"mode": "token",
"token": "redacted",
"allowTailscale": true
},
"trustedProxies": [
"redacted"
]
},
The gateway is showing these errors:
14:31:49 [ws] Proxy headers detected from untrusted address. Connection will not be treated as local. Configure gateway.trustedProxies to restore local client detection behind your proxy.
14:31:50 [ws] closed before connect conn=d7130b6c-0569-4cb6-a78f-ff3737699ac2 remote=127.0.0.1 fwd=redacted origin=<redacted> host=<redacted> ua=Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Safari/537.36 code=1008 reason=pairing required
here is my current config:
"gateway": {
"port": 18789,
"bind": "loopback",
"mode": "local",
"tailscale": {
"mode": "serve"
},
"auth": {
"mode": "token",
"token": "redacted",
"allowTailscale": true
},
"trustedProxies": [
"redacted"
]
},
Solution
That
Also, the “proxy headers detected from untrusted address” warning is because with Tailscale Serve the Gateway sees the connection coming from localhost (
1) Fix
For Serve, the proxy is on the same machine, so set:
(Your current “redacted” entry is likely the MagicDNS name or a Tailnet IP — but the Gateway log shows the proxy hop is actually
Restart the gateway after changing it.
disconnected (1008): pairing requiredAlso, the “proxy headers detected from untrusted address” warning is because with Tailscale Serve the Gateway sees the connection coming from localhost (
remote=127.0.0.11) Fix trustedProxies
for Tailscale Serve
For Serve, the proxy is on the same machine, so set:trustedProxies(Your current “redacted” entry is likely the MagicDNS name or a Tailnet IP — but the Gateway log shows the proxy hop is actually
127.0.0.1Restart the gateway after changing it.
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
131,281Members
Resources
Was this page helpful?
