Bot not responsive on Telegram after edit env
✅Solved
I rotated the telegram bot token in the .env file and am now getting an error after running this command:
openclaw-local % docker exec -it openclaw-local openclaw status
I'm on a docker container on my local mac.
openclaw-local % docker ps | grep openclaw-local
26bcf0f2f043 ghcr.io/openclaw/openclaw:latest "docker-entrypoint.s…" 2 hours ago Up About an hour (healthy) 0.0.0.0:63214->18789/tcp, [::]:63214->18789/tcp, 0.0.0.0:63216->18791/tcp, [::]:63216->18791/tcp openclaw-local
I'm on v 3.2.26
The var TELEGRAM_BOT_TOKEN was already set and everything was fine. I went to @botfather on TG, got a new token and now I can't talk to my bot.
openclaw-local % docker exec -it openclaw-local openclaw status
I'm on a docker container on my local mac.
openclaw-local % docker ps | grep openclaw-local
26bcf0f2f043 ghcr.io/openclaw/openclaw:latest "docker-entrypoint.s…" 2 hours ago Up About an hour (healthy) 0.0.0.0:63214->18789/tcp, [::]:63214->18789/tcp, 0.0.0.0:63216->18791/tcp, [::]:63216->18791/tcp openclaw-local
I'm on v 3.2.26
The var TELEGRAM_BOT_TOKEN was already set and everything was fine. I went to @botfather on TG, got a new token and now I can't talk to my bot.
Solution
If it’s still the old token (or empty), you need a recreate/restart:
2) See whether config is overriding env
- If
3) Look at Telegram-specific failures in logs
2) See whether config is overriding env
- If
channels.telegram.botToken3) Look at Telegram-specific failures in logs
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
134,827Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
