#Older version
1 messages · Page 1 of 1 (latest)
First, please run this and paste it so we know what you’re on:
openclaw --version
If you just want to roll back without deleting your config/workspace, do not uninstall ~/.openclaw. Try:
openclaw update --tag 2026.4.23 --yes
openclaw doctor
openclaw gateway restart
If openclaw update itself is stuck/broken, reinstall that exact version with pnpm:
pnpm add -g openclaw@2026.4.23
openclaw doctor
openclaw gateway restart
Current latest is 2026.4.25, so if you’re on 2026.4.24, updating forward may also fix it:
openclaw update
Docs: https://docs.openclaw.ai/install/updating
Uninstall guide if you really want a full wipe: https://docs.openclaw.ai/install/uninstall
And there was an error with channel telegram some 5000ms
That sounds like Telegram startup/probe timing out, not necessarily the whole install being broken. Please don’t paste your Telegram bot token, but do paste the exact error line if you can.
Run these first:
openclaw --version
openclaw status --all
openclaw channels status --probe
If it’s hanging because Telegram can’t reach the Bot API, check network:
curl -I https://api.telegram.org
openclaw logs --follow
If you just want OpenClaw to start while you debug Telegram, temporarily disable Telegram and restart:
openclaw config set channels.telegram.enabled false --strict-json
openclaw gateway restart
Rollback option, keeping your config/workspace:
openclaw update --tag 2026.4.23 --yes
openclaw doctor
openclaw gateway restart
Docs: https://docs.openclaw.ai/gateway/troubleshooting and https://docs.openclaw.ai/channels/telegram#troubleshooting
Im using open router with z-ai free model ⚠️ API rate limit reached. Please try again later. This error can so should I switch to another openrouter model?
Yes — that error is from the model/API quota, not usually an OpenClaw install problem. So uninstalling/rolling back probably won’t fix a rate limit.
Try this in the chat with your bot:
/model list
Then pick another configured model:
/model 2
or, if you know the exact OpenRouter model id:
/model openrouter/<model-id>
Free OpenRouter models often have tighter limits, so the practical options are:
- Wait until the rate limit resets.
- Switch to another OpenRouter model with
/model. - Use a paid OpenRouter key/credits if you need reliability.
- Ask in #models for current model recommendations — model availability/rate limits change too fast for me to safely recommend a specific one here.
So I need to do openclaw config? And open router api and select a new model
Yep — roughly:
-
Keep the OpenRouter API key configured
If it’s already set, no need to redo it. If not:openclaw onboard --auth-choice openrouter-api-key -
Pick/switch model
In chat with your bot:/model listThen choose one by number, or set one from CLI:
openclaw models set openrouter/<provider>/<model>
-
For free OpenRouter models specifically, you can scan candidates:
openclaw models scan --set-default
If you’re using free models, rate limits are normal. Switching can help, but a paid OpenRouter key/credits will be more reliable.
I have selected nvidia nemotron nano 9b v2 after selecting what do I do
If you selected it from /model, you’re basically done.
Next steps:
/model status
Then send a simple test message like:
hi, reply with one sentence
If it still uses the old/rate-limited model, start a fresh session:
/new
If you selected it from terminal instead, verify:
openclaw models status
You only need openclaw config if the OpenRouter API key/model wasn’t saved. If you get rate-limited again, it’s the free OpenRouter model quota — wait or switch to another model with /model list.
I mean like how do I check it or start it from telegram as I selected a new model
Ah got it. Two important bits:
- If you only selected the model on OpenRouter’s website, OpenClaw does not automatically know. You must select it in OpenClaw too.
- If you selected it in Discord with
/model, that may only affect that Discord session. Telegram may need its own/modelor a fresh default.
Do this:
openclaw gateway status
openclaw channels status --probe
Then open Telegram, DM your bot:
/start
/model status
If it says pairing required, run on the machine:
openclaw pairing list telegram
openclaw pairing approve telegram <CODE>
Then in Telegram:
/model list
Pick the new model there, then start fresh:
/new
Send a test message like “hi”. If you want the model to be default everywhere, set it from terminal:
openclaw models set openrouter/<provider>/<model>
Docs: https://docs.openclaw.ai/channels/telegram and https://docs.openclaw.ai/concepts/models
No i selected it from open claw config again so nect what do to chat in telegram
Gotcha — if you selected the model in OpenClaw config, next do this:
openclaw gateway restart
openclaw channels status --probe
Then open Telegram and DM your bot:
/start
If it replies, send:
/model status
Then start a clean chat/session with the new model:
/new
Now just message it normally.
If Telegram says pairing required, run:
openclaw pairing list telegram
openclaw pairing approve telegram <CODE>
Don’t paste your bot token here. Docs: https://docs.openclaw.ai/channels/telegram
It still says api limit reached should I use a new api from openrouter?
Maybe — but a new OpenRouter API key only helps if the limit is on that key.
Usually:
- Same OpenRouter account + new key → probably still rate-limited if it’s account/free-quota based.
- Add credits / paid usage → most reliable fix.
- Switch to another model → helps if the specific free model is rate-limited.
- Different OpenRouter account/key → may work, but don’t abuse free limits.
If you do get a new key, configure it again:
openclaw onboard --auth-choice openrouter-api-key
openclaw gateway restart
Then in Telegram:
/new
Also check your OpenRouter dashboard usage/limits. And don’t paste the API key here.
Now it says llm request timeout
That’s a provider/model timeout now — not an uninstall problem.
Try this:
openclaw models status --probe
If OpenRouter is timing out, either switch model again or give it more time:
openclaw config set models.providers.openrouter.timeoutSeconds 120 --strict-json
openclaw gateway restart
Then in Telegram:
/new
and test with a tiny message like “hi”.
If it still times out, the free Nemotron route is probably overloaded/slow on OpenRouter. Use /model list and pick another model, or ask in #models for current good OpenRouter choices. Also please paste openclaw --version if it keeps happening. Docs: https://docs.openclaw.ai/concepts/models
Should I switch account and try once?
You can try once, but I’d do it in this order:
- Try a different OpenRouter model first — timeouts often mean that specific free route is overloaded.
- Check OpenRouter dashboard for quota/rate-limit state.
- If you have another legitimate OpenRouter account/key, you can test it, but don’t rely on account switching to dodge free limits. Paid credits are the stable fix.
To switch key:
openclaw onboard --auth-choice openrouter-api-key
openclaw gateway restart
Then in Telegram:
/new
If it still says timeout, it’s probably the model/provider route, not the account.
I have used new api and selected minimax 2.5 next what to do
Nice — now just restart and test from Telegram:
openclaw gateway restart
openclaw channels status --probe
openclaw models status --probe
Then in Telegram DM with your bot:
/new
hi, reply in one sentence
If it replies, you’re good.
If it still fails, paste the exact error text from:
openclaw logs --follow
Don’t paste API keys/tokens.
Its not responding at all?
Okay, now we need to see where it’s failing: gateway, Telegram, or model.
Run these and paste the output:
openclaw --version
openclaw status
openclaw gateway status
openclaw channels status --probe
openclaw models status --probe
Then restart once:
openclaw gateway restart