Tailscale service unavailable

Insight & Feedback
, ,
1

image
image2394×1692 205 KB

IMG_20260711_085553
IMG_20260711_0855531920×818 406 KB

2

I have the same issue, problem starts yesterday (jul 10th) after upgrading zigmaos

3

I tested this on my own ZimaCube using the standard Tailscale app from the main ZimaOS/CasaOS App Store:

Image: tailscale/tailscale:v1.98.3
App ID: org.icewhale.tailscale

This is the Tailscale app with the normal Tailscale icon, not the separate BigBear package.

I confirmed the /etc/resolv.conf message is not the actual failure. Tailscale falls back to another method and still reaches the Running state.

The real issue is the current App Store container command:

tailscaled --state=/var/lib/tailscale/tailscaled.state & sleep 10; tailscale web --listen 0.0.0.0:5252

If the built-in Tailscale web client is already enabled, tailscaled is already listening on port 5252 through the Tailscale IP. The second tailscale web process then also tries to bind port 5252, causing:

listen tcp 0.0.0.0:5252: bind: address already in use

The container then restarts repeatedly, while the ZimaOS tile remains on Starting up or Service unavailable.

You do not need to log in again if this command already shows your device connected:

docker exec tailscale tailscale status

I fixed the App Store compose by binding the separate web interface only to the ZimaOS LAN IP instead of 0.0.0.0.

First back up the compose file:

cp /var/lib/casaos/apps/tailscale/docker-compose.yml /var/lib/casaos/apps/tailscale/docker-compose.yml.backup

Replace YOUR-ZIMA-IP with the LAN IP of your ZimaOS device:

python3 - <<'PY'
from pathlib import Path

path = Path("/var/lib/casaos/apps/tailscale/docker-compose.yml")
text = path.read_text()

old = "tailscaled --state=/var/lib/tailscale/tailscaled.state & sleep 10; tailscale web --listen 0.0.0.0:5252"
new = "tailscaled --state=/var/lib/tailscale/tailscaled.state & sleep 10; exec tailscale web --listen YOUR-ZIMA-IP:5252"

if old not in text:
    raise SystemExit("Expected entrypoint was not found. No changes made.")

path.write_text(text.replace(old, new))
PY

Then recreate only the Tailscale container:

cd /var/lib/casaos/apps/tailscale
docker compose up -d --force-recreate

Verify it is stable:

docker inspect tailscale --format 'Status={{.State.Status}} RestartCount={{.RestartCount}}'

Check the listener:

ss -lntp | grep ':5252'

On my ZimaCube, the container then stayed at:

Status=running
RestartCount=0

and the web interface worked directly at:

http://YOUR-ZIMA-IP:5252/

The ZimaOS tile itself still did not open correctly, but the direct LAN URL worked immediately. I believe the current App Store package needs its startup command and launcher handling corrected.

Do not install the BigBear Tailscale package alongside this one, as both could compete for TUN access, host networking, DNS and routes.

1 Like