CLAWSOLATOR ALPHABeta release planned · License under considerationRead what is verified
Remote access / Cloudflare

HTTP works. The agent still cannot connect.

A 302 login redirect, a working HTML dashboard, an authenticated WebSocket and an approved device are four different facts. They must be checked separately.

Historical reports · Guarded XClaw tooling in alpha · Live phone acceptance not completed

Community reports that explain the confusion

Bug report · Closed as not planned (stale)

Cloudflare Quick Tunnel origin rejected

Control UI rejected a trycloudflare.com origin with an origin-not-allowed error.

Origin validation is an important security control; never encourage disabling it.

Read the primary source
Bug report · Historical report

Control UI client handshake through Cloudflare tunnel

Reporter observed null client identification fields during Cloudflare tunnel handshake.

Different from a universal tunnel defect; live end-to-end proof pending.

Read the primary source
Documentation/product report · Open (at research)

Cloudflare-originated WebSocket 403 on worker destination

A reporter observed HTTP working while WebSocket Upgrade returned 403 for a specific Access Worker destination.

Not an OpenClaw Gateway deployment; do not imply Clawsolator fixes this Cloudflare Worker issue.

Read the primary source

The meaningful engineering distinction

Cloudflare can provide excellent access controls, but an allowed HTTPS page does not establish a native WebSocket connection to OpenClaw. Likewise, an origin rejection can be a desirable security check rather than a defect that should simply be disabled.

XClaw v5.9.4 distinguishes a legitimate Access sign-in redirect from proven WSS connectivity. It preserves management credentials privately, avoids automatic retries of uncertain Cloudflare write operations, and uses official iOS pairing behavior. Its offline regression tests are documented; the final real-device connection must still be verified.

At the Clawsolator security salon

What Clawsolator does not recommend

Never fix origin errors by blindly removing authentication.

Keep the Gateway private, verify origin/Access policy and transport independently, then approve the expected device. Do not confuse a Cloudflare management API token, Access service token and Gateway device authorization.