Activity
Mon
Wed
Fri
Sun
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
What is this?
Less
More

Memberships

OpenClaw Users

745 members • Free

Clief Notes

19k members • Free

2 contributions to OpenClaw Users
Cron commands fail with “pairing required” even though gateway is running and status works
I was trying to set up a simple daily reminder using openclaw cron, but all cron commands failed with: gateway connect failed: GatewayClientRequestError: pairing required What I tested: • openclaw status worked • openclaw gateway status showed the gateway running and RPC probe ok • openclaw cron status, openclaw cron list, and openclaw cron add ... all failed with pairing required • ran openclaw doctor • ran openclaw doctor --fix • regenerated gateway token through openclaw configure • restarted gateway with openclaw gateway restart At one point the dashboard/config flow also showed: unauthorized: gateway token mismatch After token regeneration + restart, the mismatch cleared, but cron still failed with pairing required. This seems like a broken local auth/pairing state for cron specifically, with no clear recovery path. The UX is especially confusing because normal status checks work while cron remains unusable.
1
0
Has anyone had a problem like this...
Heya! I've installed openclaw on my local machine and I have few questions now: 1. How to start it on CMD (Windows 11) without installing it a new every time? 2. I can't access the dashboard from my browser, I'm using Firefox, tried to trouble shoot for couple of hours without a success... Are there anyways to go around all the '1006' and 'unrecognized' errors? 3. Trying to set up automated x.com account, using Gemini token. Is it as hard as it looks?
1 like • 3d
Hey Adam! I’m a total noob at this but I had a similar problem. My setup may be different than yours. I bought a new mini pc (beelink) and downloaded WSL2 to convert it from the windows shell to Ubuntu. As someone who didn’t know anything about hardware a week ago, I just kept asking Gemini how to get the most out of this and what I should click during the downloading. I kept losing connection with same error. I found that the only thing that kept my agent “alive” was keeping the Ubuntu app open. Additionally, I changed my system to “always on” and took my screens off of “sleep” mode. These things seemed to keep my agent going.
1-2 of 2
Chris Martin
1
3points to level up
@chris-martin-2542
Figuring things out one step at a time.

Active 10h ago
Joined Apr 6, 2026
Powered by