Has anyone been able to get Tailscale Serve working on StartOS 0.4?

General
1

Has anyone successfully used Tailscale Serve on StartOS 0.4?

I’m testing the new Tailscale integration with Tailscale 1.98.9:1.

The node connects correctly, MagicDNS works, HTTPS certificates work and
https://startos..ts.net reaches Tailscale Serve, but Serve returns HTTP 502.

StartOS creates:

Tailscale Serve
→ http://localhost:20000
→ socat
→ 10.0.3.1:53632
→ StartOS UI

What’s strange is that from inside the Tailscale container both backend URLs work:

wget http://10.0.3.1:53632
→ HTTP 200

wget http://127.0.0.1:20000
→ HTTP 200

But accessing the same backend through Tailscale Serve returns 502.

Has anyone confirmed Tailscale Serve working on StartOS 0.4?

I’m wondering if this could be an interaction between the StartOS integration,
Tailscale 1.98.9 and userspace-networking mode rather than a normal Tailscale
configuration issue.

2

hi anyone can provide some guidance?

3

Confirming the same on Tailscale 1.98.9:2 (so the newer package revision doesn’t fix it), StartOS 0.4.0.

Same symptom: node signs in fine, MagicDNS resolves, HTTPS certificates enabled, HTTPS serve on the StartOS UI returns 502. HTTP-mode serve on the StartOS UI stalls rather than 502ing. Restarting the Tailscale service doesn’t help.

One data point that may help isolate it: serving the Tailscale package’s own admin interface over HTTP works fine — that page loads normally over the tailnet. So Serve itself is functional; the failure is specific to proxying the StartOS UI through the socat hop.

Also worth noting for anyone searching: Tailscale doesn’t appear under System → Gateways at all, so there’s no gateway-level config to check.

4

Thanks for confirming, maybe who prepared the community package can provide some guidance