7 replies

APK Connection Failure: Tailscale + No Pairing Request

Environment Details:
- Gateway Host: Windows 10 Home (x64), Firewall disabled on private network.
- Runtime: Node.js v24.13.0.
- Network: Tailscale (MagicDNS enabled).
- OpenClaw Version: v2.9
- Mobile Device: Samsung Galaxy Z Fold7 (Android 14) running the OpenClaw-Node.apk v2026.2.9-dev .

The Issue:
The mobile browser connects via Tailscale only when

dangerouslyDisableDeviceAuth: true

dangerouslyDisableDeviceAuth: true

is set. The APK fails entirely.

Critical Observations:
1. No Pairing Button: Even when accessing the Dashboard via the mobile browser, there is no "Pairing" or "Trust this Device" button/trigger visible anywhere regardless dangerouslyDisableDeviceAuth: true

 is set. The UI doesn't seem to recognize that an untrusted device is attempting to connect.
2. **Auth UI Missing in APK:** The APK lacks a field to input the

 is set. The UI doesn't seem to recognize that an untrusted device is attempting to connect.
2. **Auth UI Missing in APK:** The APK lacks a field to input the

token

, making it impossible to authenticate manually.
3. **Handshake Reset:** Connection attempts from the APK are reset immediately over the Tailscale tunnel.
4. **Pairing Logic:** We suspect the Tailscale proxy is stripping the headers that would normally trigger the pairing workflow on the Gateway.

**Question:**
Why is the "Pairing" button missing from the dashboard when accessed remotely, and is there a way to force-authorize a device ID manually in

, making it impossible to authenticate manually.
3. **Handshake Reset:** Connection attempts from the APK are reset immediately over the Tailscale tunnel.
4. **Pairing Logic:** We suspect the Tailscale proxy is stripping the headers that would normally trigger the pairing workflow on the Gateway.

**Question:**
Why is the "Pairing" button missing from the dashboard when accessed remotely, and is there a way to force-authorize a device ID manually in

openclaw.json` since the UI trigger is absent?

FotC�

Friends of the Crustacean 🦞🤝•4w ago•

7 replies

APK Connection Failure: Tailscale + No Pairing Request

dangerouslyDisableDeviceAuth: true

dangerouslyDisableDeviceAuth: true

 is set. The UI doesn't seem to recognize that an untrusted device is attempting to connect.
2. **Auth UI Missing in APK:** The APK lacks a field to input the

 is set. The UI doesn't seem to recognize that an untrusted device is attempting to connect.
2. **Auth UI Missing in APK:** The APK lacks a field to input the

token

, making it impossible to authenticate manually.
3. **Handshake Reset:** Connection attempts from the APK are reset immediately over the Tailscale tunnel.
4. **Pairing Logic:** We suspect the Tailscale proxy is stripping the headers that would normally trigger the pairing workflow on the Gateway.

**Question:**
Why is the "Pairing" button missing from the dashboard when accessed remotely, and is there a way to force-authorize a device ID manually in

, making it impossible to authenticate manually.
3. **Handshake Reset:** Connection attempts from the APK are reset immediately over the Tailscale tunnel.
4. **Pairing Logic:** We suspect the Tailscale proxy is stripping the headers that would normally trigger the pairing workflow on the Gateway.

**Question:**
Why is the "Pairing" button missing from the dashboard when accessed remotely, and is there a way to force-authorize a device ID manually in

openclaw.json` since the UI trigger is absent?

APK Connection Failure: Tailscale + No Pairing Request

Similar Threads

APK Connection Failure: Tailscale + No Pairing Request

Similar Threads

Similar Threads

Similar Threads