#HTTP 404: not_found_error: Not Found (request_id: req_011CXY8vzKNXyHFJ7ovGEqin)
1 messages Β· Page 1 of 1 (latest)
That HTTP 404 not_found_error is unusual for model calls β typically that's an API-level error, not a Moltbot/Clawdbot error.
Before troubleshooting, please run:
moltbot --version
Version mismatches are the #1 cause of weird model errors.
Common culprits for this error:
-
API key issues β Anthropic (and others) rotate keys periodically. Check your
~/.moltbot/config.json5and verify keys are still valid. -
Provider configuration β If you recently updated or changed providers, make sure the
providerssection is correctly formatted. See: https://docs.moltbot.ai/configuration/providers -
Gateway restart needed β Sometimes the gateway gets out of sync. Try:
moltbot gateway restart
- Telegram channel config β The error shows a channel ID, so double-check the Telegram channel is properly linked in your config.
Docs to reference:
- Troubleshooting: https://docs.moltbot.ai/gateway/troubleshooting
- Models: https://docs.moltbot.ai/concepts/models
Let me know what version you're on and we can dig deeper! π¦
not working
check logs
Found the issue! Look at this line in your logs:
Config was last written by a newer Clawdbot (2026.1.25); current version is 2026.1.24-3.
You have a version mismatch. Your config was written by v2026.1.25 but you're running v2026.1.24-3.
Fix steps:
- Update Moltbot:
cd ~/moltbot-ref && git pull pnpm install pnpm build
-
Or if you use Homebrew:
brew update && brew upgrade moltbot -
After updating, restart the gateway:
moltbot gateway restart
The logs show your bot otherwise working fine (messages received, processed successfully with outcome=completed). The version mismatch is likely causing the model API calls to fail.
Let me know once you've updated! π¦