What data schema does Rabbit R1 expect for pairing with OpenClaw

general chat
1

I am currently setting up a custom gateway using OpenClaw on an AWS EC2 instance. While the server is running correctly and the ports are open, I am unable to get the Rabbit R1 to accept the pairing QR code. Every attempt results in an “Invalid QR Format” error on the device.

I am trying to point the R1 to my Public IP instead of the internal private LAN IP generated by the script.

that terminal command generates qr code, which can’t create a correctly connection to my AWS

What is the exact expected data schema or prefix required for the Rabbit R1 to recognize a gateway configuration QR code? Does the R1 expect a specific header (e.g., rabbit_pairing:) or a specific encryption/encoding format to successfully trigger the “Pairing Request” screen when using a public IP address?

I want to generate by myself that qr code with changed ip adress using r1 schema, because by default it takes wrong ip :frowning:

2

I am having the same issue. I am running OpenClaw under Cloudron. The connection to Rabbit does not work because it is not accapting any code, openclaw figures out to connect.

3

Have a look at this post: how to connect your r1 to OpenClaw (formerly Moltbot/Clawdbot) - #9 by simon

If you see “Invalid QR Format” on VPS/public setups, the key point is:

  • local network setups can use insecure WS,
  • but remote/VPS setups need a valid SSL domain + WSS on port 443.

So don’t use raw public IP + ws QR for internet-facing pairing. Use a tunnel/proxy setup (e.g. Cloudflare Tunnel), point it to localhost:<openclaw_port>, then generate QR with the public hostname and port 443, scan, and approve pairing.

Also keep token auth enabled and avoid exposing OpenClaw directly without TLS/proxy protection.

1 Like
4

Thank you, will try