Troubleshooting
Fixes for the most common problems during setup and day-to-day use.
Start here: re-run the command with debug output turned on. The extra details usually show what went wrong.
OFFICECLAWS_DEBUG=1 officeclaws <command>Account and subscription
This account has no active subscription
Run officeclaws subscribe and finish the payment. Wait a minute, then run officeclaws onboard again. If you paid on the website with a different email, contact support so we can link the payment to your account.
not logged in — run: officeclaws login
Run officeclaws login.
Contabo
contabo: … after entering credentials
One of the four values is wrong. The most common mistake is using your website password instead of the separate API password. See Step 4.
no VPSes found on your account
The server hasn't been delivered yet, or the credentials belong to a different Contabo account. Check that the server shows as running at my.contabo.com.
Setup has been stuck on "Waiting for the VPS" for a long time During setup, Office Claws installs its SSH key through Contabo, and Contabo then restarts the server. This can take up to 30 minutes. Don't interrupt it. If you stop it halfway, Contabo can lock the server for another 5–15 minutes.
Tailscale
Tailscale daemon is not running
Open the Tailscale app and connect, then try again.
Auth key errors (invalid key, API key does not exist)
The key has expired, was revoked, or was single-use and has already been used. Create a new reusable key and run officeclaws onboard --tailscale-authkey tskey-auth-….
Agent shows offline or chat says it can't connect
- Check that Tailscale is connected on your computer:
tailscale status. - Check that the agent's server appears in your tailnet. It's listed at login.tailscale.com/admin/machines.
- Your computer and the agent must be in the same tailnet.
- Check in the Contabo panel that the VPS is running.
- Did it work for months and then stop? The server's Tailscale key probably expired. Sign in to the VPS through Contabo's VNC console as
root, with the root password you set when ordering the server (theopenclawuser can't usesudothere), and runtailscale up. Or start over from a clean server, see Manage agents. To prevent this from happening again, turn off key expiry.
Agent and chat
The agent doesn't reply, or you see rpc final event had no text or disconnects
You have most likely hit your ChatGPT plan's Codex usage limit. Wait for it to reset, or upgrade your ChatGPT plan. If it says the agent isn't connected to a model, run officeclaws connect-codex.
1008 pairing required
Run officeclaws pairing repair.
Codex sign-in times out
Finish the sign-in within 5 minutes, in a browser on the same computer. Then run officeclaws connect-codex again.
Telegram bot doesn't answer
- Run
officeclaws telegram showand check that it saysenabled : true. - With the
pairingmode, you have to approve your account first. See Telegram. - Make sure no other program is using the same bot token.
Still stuck?
- Collect the logs:
- Your agent:
officeclaws logs --lines 500 - Setup: the newest file in
~/.openclaw/logson your computer
- Your agent:
- Message us on Telegram: t.me/getfrontendeddm. Include the command you ran, the error, and the logs. Remove any keys, tokens, or passwords first.