Pairing QR rewired gateway binding and broke Serve
Generating a QR reportedly changed gateway.bind and left Tailscale Serve targeting the old loopback, causing 502.
XClaw live iPhone/Tailscale acceptance still pending.
Read the primary sourceWhen a pairing action changes the address a reverse proxy expects, an apparently healthy Gateway can become unreachable. This failure pattern was documented by OpenClaw users.
Historical reports · XClaw 5.9.9 offline testing completed · Real iPhone/Tailscale acceptance pending
Generating a QR reportedly changed gateway.bind and left Tailscale Serve targeting the old loopback, causing 502.
XClaw live iPhone/Tailscale acceptance still pending.
Read the primary sourceReporter documented ~10 hours of downtime after incompatible bind changes were accepted while Serve was enabled.
The issue label reflects closure; it does not establish that engineers deliberately refused a safety improvement.
Read the primary sourceA user was prompted for pairing despite Tailscale identity being configured.
Authentication and device approval are not interchangeable.
Read the primary sourceA user trying to pair their phone reasonably expects an existing secure desktop route to remain functional. In a documented report, a QR-pairing workflow changed the Gateway bind while Tailscale Serve continued proxying to the previous loopback address. The reported outcome was HTTP 502. A separate request argued that mutually incompatible bind/Tailscale combinations should be rejected before restarting the Gateway.
These reports are evidence of historical pain—not evidence that every current release retains the same behavior. One request was closed as not planned with stale labeling, which is not proof of developer motives.
XClaw v5.9.9 includes managed Serve preflight, guarded rollback, HTTPS diagnostic classifications, and the official QR pathway. Offline QA passed 227 Python tests and related shell/security checks.
Production Serve consent, authenticated WSS, iPhone pairing and reconnect, and preserving the existing Cloudflare route all require live host acceptance.