Telegram trigger suddenly not working

[Oskarman]

Describe the problem/error/question

The telegram trigger suddenly stopped working.
This is not the first time that I am encountering this issue. I have spent hours trying to troubleshoot it. The last time I solved it was by buying a domain, but now, after a few months, the trigger stopped working again.
I am working on Hostinger. Have heard that the default Hostinger URLs get banned by Telegram, which is why I bought my own and that worked for a while. Now I noticed that a few days ago it stopped working, again.
If anybody else had the same problem and managed to solve it, please advise.

What is the error message (if any)?

Please share your workflow

Share the output returned by the last node

Information on your n8n setup

• n8n version: 2.15.0
• Database (default: SQLite): default
• n8n EXECUTIONS_PROCESS setting (default: own, main): default
• Running n8n via (Docker, npm, n8n cloud, desktop app): Docker in Hostinger
• Operating system: Linux

[Anshul_Namdev]

Hi @Oskarman I think you should read this:

Telegram Trigger webhook stops receiving messages

Describe the problem/error/question I have a Telegram bot connected to an n8n workflow using a Telegram Trigger (webhook). It used to work perfectly about a week ago, but now the workflow does not receive any incoming messages from Telegram. The workflow stays stuck on “Waiting for trigger events”, even though the webhook is set correctly. Telegram’s getWebhookInfo shows that the webhook URL is set, but it also shows: pending_update_count increasing last_error_message: "Read timeout exp…

But honestly this is being a limitation now as telegram does not like hostinger, so i would highly recommend you to switch to n8n cloud! Although you could swap domains but that would only work to an extent, as they have started blocking hostinger infrastructure , so i believe n8n cloud is a far better option.

n8n Cloud Plans Breakdown: Starter, Pro, Business & Enterprise (2026)

[tamy.santos]

hi @Oskarman
I would first re-save or recreate the Telegram Trigger after confirming WEBHOOK_URL points to your current public HTTPS domain, because the n8n docs note that Telegram triggers depend on a valid public HTTPS webhook URL and reverse-proxy setups break when that public webhook URL is no longer correct or reachable.

[achamm]

Have you tried hitting https://api.telegram.org/bot<TOKEN>/deleteWebhook manually and then deactivating/reactivating the workflow? Hostinger IPs get flagged by Telegram a lot, routing through Cloudflare proxy usually fixes it for good