Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Gateway restart nukes all Tailscale Serve bindings, not just its own [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#60482•Fetched 2026-04-08 02:50:33
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
arvindvenkataramaniarvindvenkataramani
Participants
arvindvenkataramaniarvindvenkataramani

When the gateway restarts, it resets all Tailscale Serve bindings and only re-adds its own. This silently breaks other services on the same machine that rely on Tailscale Serve on different ports.

Root Cause

When the gateway restarts, it resets all Tailscale Serve bindings and only re-adds its own. This silently breaks other services on the same machine that rely on Tailscale Serve on different ports.

Code Example

tailscale serve --bg --http=[myport] localhost:[myport]

---

tailscale serve status
   # shows port `myport` and the gateway's UI port (e.g. `18789`)

---

openclaw gateway restart

---

tailscale serve status
   # port [myport] is gone — only the gateway's binding remains
RAW_BUFFERClick to expand / collapse

Summary

When the gateway restarts, it resets all Tailscale Serve bindings and only re-adds its own. This silently breaks other services on the same machine that rely on Tailscale Serve on different ports.

Repro

  1. Set up Tailscale Serve for another service on the same host: 
    tailscale serve --bg --http=[myport] localhost:[myport]
  2. Confirm both bindings exist: 
    tailscale serve status
# shows port `myport` and the gateway's UI port (e.g. `18789`)
  3. Restart the gateway: 
    openclaw gateway restart
  4. Check serve status again: 
    tailscale serve status
# port [myport] is gone — only the gateway's binding remains

Expected

The gateway should only manage its own Tailscale Serve binding. It should not call tailscale serve reset or otherwise clear bindings it doesn't own.

Environment

  • OpenClaw 2026.3.23-2 (7ffe7e4)
  • Raspberry Pi (Debian/Bookworm), Tailscale 1.82
  • Other services using Tailscale Serve on the same host

extent analysis

TL;DR

The gateway should be modified to only manage its own Tailscale Serve binding, preventing it from resetting other services' bindings on restart.

Guidance

  • Identify the gateway's restart mechanism and modify it to not call tailscale serve reset or clear other bindings.
  • Verify that the gateway only manages its own binding by checking the tailscale serve status output after a restart.
  • Consider implementing a separate mechanism for other services to re-establish their Tailscale Serve bindings after a gateway restart.
  • Review the OpenClaw gateway code to ensure it does not interfere with other services using Tailscale Serve on the same host.

Example

No code snippet is provided as the issue does not specify the implementation details of the gateway or the services using Tailscale Serve.

Notes

The solution may require modifications to the OpenClaw gateway code, which could have implications for other services relying on it. Additionally, the fix may need to be adapted for different versions of OpenClaw or Tailscale.

Recommendation

Apply a workaround to prevent the gateway from resetting other services' bindings, such as modifying the restart script to re-establish the bindings after the gateway restarts. This is recommended because upgrading to a fixed version is not explicitly mentioned as an option, and the workaround can provide a temporary solution until a permanent fix is available.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#agent setup#task chaining#parallel task#integration issue#index setup

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix Gateway restart nukes all Tailscale Serve bindings, not just its own [1 participants]