Telegram Trigger webhook stops receiving messages

Questions
1

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 expired"

This suggests Telegram cannot reach or get a response from n8n.

I already regenerated the bot token and reset the webhook successfully.
Webhooks return "Webhook was set" but n8n still does not receive updates.

No errors appear inside n8n UI.

What is the error message (if any)?

No error messages, just “waiting for trigger events”

Information on your n8n setup

    1. n8n version: 2.0.3
    2. Database: default
    3. EXECUTIONS_PROCESS: Default
    4. Running n8n via: Docker
    5. Hosting: Server deployed on Hostinger cloud
    6. Operating system: macOS
2

Hii @MLVteam

check the health status of the trigger
https://api.telegram.org/<your_bot_token>/getWebhookInfo

Most likely there is an issue with the webhook, or there is another webhook configured.

3

they all say {“ok”:false,“error_code”:404,“description”:“Not Found”}

4

@MLVteam How it works in some cases.
For tunnel using Ngrok

Here’s the run bat file

@echo off
docker stop n8n
docker rm n8n
docker run -d ^
  -p 8443:8443 ^
  -v n8n_data:/home/node/.n8n ^
  -e N8N_HOST=urladdress.ngrok-free.app ^
  -e N8N_PROTOCOL=https ^
  -e N8N_PORT=8443 ^
  -e WEBHOOK_TUNNEL_URL=https://urladdress.ngrok-free.app ^
  -e NODEJS_PREFER_IPV4=true ^
  -e N8N_LOG_LEVEL=debug ^
  -e N8N_LOG_FILE_LOCATION=/home/node/.n8n/logs/n8n.log ^
  --name n8n ^
  docker.n8n.io/n8nio/n8n start --tunnel
  
ngrok http --url=urladdress.ngrok-free.app 8443
5 
{"ok":true,"result":{"url":"my_webhook","has_custom_certificate":false,"pending_update_count":2,"last_error_date":1766403862,"last_error_message":"Read timeout expired","max_connections":40,"ip_address":"my_ip"}}

Here what i have as a reponse to getWebhookInfo

6

Thank you for your answers!
So it is like I need to have open tunnel always between telegram and n8n?

7

I had the same issue all off the sudden it stopped working and spend the whole weekend trying to figure this out, the issue is Telegram Blacklisted the hostinger urls, so you will have to add some new domain to it. I did it and now it work, i switched from hstgr.vloud to n8n.mydomain.com

4 Likes
8

ohh wow, thank you, i will do it now!

9

Let me know if it works, after i did it, i got a 308 error and had to to add some enviroment values (it takes about 30min to take effect) and it worked
Docker Manager - Projects - Manage button - scroll down to Enviroment dropdown and add it there

I added in the following values:
N8N_HOST - new domain (if you did it like me n8n.mydomain.com - this would only be mydomian.com)
N8N_PROTOCOL - https
WEBHOOK_URL - https://n8n.mydomain.com/
N8N_EXPRESS_TRUST_PROXY - true

3 Likes
10

@Eugene_Bredenkamp thanks a lot, it worked for me, telegram bots work again! the only think I was stuck for some time because it ruined my user, so i needed to backup db → then remove it → create a new user → restore old db with all workflows.

1 Like
11

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.