ETELEGRAM: 409 Conflict: terminated by other long poll or webhook
See original GitHub issueQuestion
I have Telegram Bot running as part of a Node.js script. When terminating the Node.js script by hitting Ctrl + C on my keyboard and restarting the script, I am getting the following error from the bot:
{“code”:“ETELEGRAM”,“message”:“ETELEGRAM: 409 Conflict: terminated by other long poll or webhook”}
I guess the error comes from an “unclean” termination of the process (when hitting Ctrl + C on my keyboard). What should I do if there is such an interrupt? Do I need to close a session or anything like that?
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:20 (1 by maintainers)
Top Results From Across the Web
409: Conflict: terminated by setWebhook request in Telegraf ...
To fix this, simply delete the webhook by leaving out the webhook URL: https://api.telegram.org/bot<token>/setWebhook.
Read more >N8n telegram set webhook - Questions
Now it gives an error. {“code”:“ETELEGRAM”,“message”:“ETELEGRAM: 409 Conflict: terminated by other long poll or webhook”}.
Read more >409 conflict: terminated by other getupdates request; make ...
Error : ETELEGRAM: 409 Conflict: terminated by other long poll or webhook. Notifications were still working (not sure about messages to the bot), ......
Read more >Telegram 1.0.8 Polling Error - ioBroker Forum
... 2017-10-04 15:55:03.549 - telegram.0 polling_error:ETELEGRAM, Error: ETELEGRAM: 409 Conflict: terminated by other long poll or webhook ...
Read more >Long Polling vs. Webhooks - grammY
There are two ways how your bot can receive messages from the Telegram servers. They are called long polling and webhooks. grammY supports...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I just recreate Bot Token and the error is gone , i don’t know is it works for all of you, but for me it works
@droidmanspace hey, I am on macOS 10.13.2. I already solved this issue: my bot was deployed to Heroku and when I launched the bot locally with nodemon, it conflicted - sending the response both, from localhost and Heroku. So, I just turned off the Heroku, while testing locally.
I’m not sure is it the case for others or not