openclaw - 💡(How to fix) Fix [Bug]: Android app authorization fails silently when port 443 is unavailable, causing infinite retry loop

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

OpenClaw Android app blocks authorization and repeatedly retries without user feedback when port 443 is unavailable.

Steps to reproduce

1 Deploy OpenClaw Docker with a custom domain and Nginx configured without exposing port 443 (e.g., using port 8443). 2 Connect an Android device to the same network or via Tailscale. 3 Attempt to authorize the Android app with the OpenClaw server. 4 Observe that the app shows no feedback and continuously retries.

Expected behavior

.NOT_ENOUGH_INFO

Actual behavior

The Android app automatically blocks the authorization process and repeatedly re‑initiates the request without any visible error message or user prompt, preventing completion of setup.

OpenClaw version

2026.5.24

Operating system

Android (version unspecified)

Install method

No response

Model

.NOT_ENOUGH_INFO

Provider / routing chain

.NOT_ENOUGH_INFO

Additional provider/model setup details

.NOT_ENOUGH_INFO

Logs, screenshots, and evidence

.NOT_ENOUGH_INFO

Impact and severity

Affected: Users in regions or networks where port 443 cannot be exposed (e.g., due to ISP restrictions, custom Docker/Nginx setups, Tailscale configurations). Severity: High (blocks authorization workflow). Frequency: Always when port 443 is unavailable. Consequence: Users cannot complete Android app setup, leading to failed onboardin

Additional information

.NOT_ENOUGH_INFO