MacOS x Docker issue: Cannot connect to OpenClaw dashboard.
✅Solved
I have ran the
When connecting to the gateway Im constantly met with
The issue I seem to see is that OpenClaw is seeing a cloudflare IP (162.159.133.xxx)
1. Configuration changes tried:
- Changed bind setting from loopback to lan in both .env and config file
- Verified config with: docker compose exec openclaw-gateway cat /home/node/.openclaw/openclaw.json
- Config shows correct "bind": "lan" and "auth": {"mode": "token"}
2. Pairing attempts:
- Added wildcard pairing: {"*": {"approved": true}} to /home/node/.openclaw/devices/paired.json
- Added specific Cloudflare IP: {"162.159.133.234": {"approved": true}}
Neither worked - pairing requirement persists
3. Network troubleshooting:
- Disabled macOS "Limit IP address tracking" (System Settings → Network → Ethernet → Details)
- Disabled Chrome "Use secure DNS" (Chrome Settings → Privacy and security)
- Disabled Safari IP hiding features
- Confirmed no VPN or Cloudflare WARP installed
- Confirmed no proxy settings: scutil --proxy shows nothing
- DNS is local router (192.168.xxx.xxx), not Cloudflare DNS
4. Connection method variations:
- Tried http://127.0.0.1:18789 - Cloudflare IP appears in logs
- Tried http://localhost:18789 - Cloudflare IP appears in logs
- Tried http://[::1]:18789 (IPv6) - Cloudflare IP appears in logs
5. System checks:
- Routing table normal: netstat -rn shows standard localhost routing
/etc/hosts file normal (127.0.0.1 → localhost)
Additional context:
- Gateway HTTP server works fine: curl -I http://127.0.0.1:18789 returns 200
- Dashboard UI loads correctly, only websocket connection fails pairing
- CLI commands also fail with same error: docker compose run --rm openclaw-cli devices list → gateway closed (1006 abnormal closure)
Thank you in advance for any assistance that may be able to help in setting this up in docker.
Slats
docker-setup.shWhen connecting to the gateway Im constantly met with
disconnected (1008): pairing requiredThe issue I seem to see is that OpenClaw is seeing a cloudflare IP (162.159.133.xxx)
1. Configuration changes tried:
- Changed bind setting from loopback to lan in both .env and config file
- Verified config with: docker compose exec openclaw-gateway cat /home/node/.openclaw/openclaw.json
- Config shows correct "bind": "lan" and "auth": {"mode": "token"}
2. Pairing attempts:
- Added wildcard pairing: {"*": {"approved": true}} to /home/node/.openclaw/devices/paired.json
- Added specific Cloudflare IP: {"162.159.133.234": {"approved": true}}
Neither worked - pairing requirement persists
3. Network troubleshooting:
- Disabled macOS "Limit IP address tracking" (System Settings → Network → Ethernet → Details)
- Disabled Chrome "Use secure DNS" (Chrome Settings → Privacy and security)
- Disabled Safari IP hiding features
- Confirmed no VPN or Cloudflare WARP installed
- Confirmed no proxy settings: scutil --proxy shows nothing
- DNS is local router (192.168.xxx.xxx), not Cloudflare DNS
4. Connection method variations:
- Tried http://127.0.0.1:18789 - Cloudflare IP appears in logs
- Tried http://localhost:18789 - Cloudflare IP appears in logs
- Tried http://[::1]:18789 (IPv6) - Cloudflare IP appears in logs
5. System checks:
- Routing table normal: netstat -rn shows standard localhost routing
/etc/hosts file normal (127.0.0.1 → localhost)
Additional context:
- Gateway HTTP server works fine: curl -I http://127.0.0.1:18789 returns 200
- Dashboard UI loads correctly, only websocket connection fails pairing
- CLI commands also fail with same error: docker compose run --rm openclaw-cli devices list → gateway closed (1006 abnormal closure)
Thank you in advance for any assistance that may be able to help in setting this up in docker.
Slats
Solution
Nice — glad it’s unblocked.
One tiny correction for future-you:
…but as long as you’re paired and the dashboard reconnects, you’re good.
If this fixed it, please right-click my solution message → Apps →
Mark Solution so Answer Overflow indexes it for the next person.
One tiny correction for future-you:
openclaw devices approverequestIdpending.json…but as long as you’re paired and the dashboard reconnects, you’re good.
If this fixed it, please right-click my solution message → Apps →
Mark Solution so Answer Overflow indexes it for the next person.
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
83,815Members
Resources
Was this page helpful?
