Telegram Trigger Webhook Issue

Mohamed_Al-Adawy · April 12, 2025, 8:20am

Describe the problem/error/question

When I try to test the trigger of the telegram trigger I got the following Error:

What is the error message (if any)?

Problem running workflow
Bad request - please check your parameters
Show Details
Telegram Trigger: Bad Request: bad webhook: Failed to resolve host: Temporary failure in name resolution

Please share your workflow

Share the output returned by the last node

this is the first node in the workflow

Information on your n8n setup

n8n version: 1.86.1
n8n internal port: 8443
n8n external port: 8443
n8n host: my own dns
n8n protocol: https
Database (default: SQLite): Postgresql:17.4-alpine
n8n EXECUTIONS_PROCESS setting (default: own, main):
Running n8n via (Docker, npm, n8n cloud, desktop app): Docker on VPS
Operating system: Ubuntu 24.04

barn4k · April 12, 2025, 11:34am

Seems the container can’t resolve DNS entries. You can check with the HTTP node if https://api.telegram.org is available.

bookeat · April 14, 2025, 3:52am

你可以详细讲讲吗？我也遇到了同样的问题。
Could you please explain in detail? I have encountered the same problem.

solomon · April 18, 2025, 7:00pm

Same problem here, guys.
I’ve been facing this issue since n8n version 1.84 or so.

I can use the bot a few times and then it stops, forcing me to recycle the API token or create another bot.

mohamed3nan · April 18, 2025, 8:08pm

To understand what’s going on and pinpoint where the problem lies, we can trace the flow.

Normally, when you set up Telegram Trigger, it creates a webhook and assigns it to the telegram bot.

To confirm that the webhook is active, you can request it :
https://api.telegram.org/bot<YOUR_TOKEN>/getWebhookInfo

From the screenshot, in my case, it’s clear that everything is fine there.

So, I believe this is the key to debugging and determining where the problem lies.

tridi · April 27, 2025, 11:30am

Switching to a Webhook node instead of the Telegram trigger, I’m still facing the same problem as it suddenly started to error.

Register Your Webhook:
POST Method
https://api.telegram.org/bot[YOURBOTTOKEN]/setWebhook?url=[YOURWEBHOOK]

Delete Your Webhook (Set empty string on url webhook):
POST Method
https://api.telegram.org/bot[YOURBOTTOKEN]/setWebhook?url=

lsmelo · July 20, 2025, 12:48am

Telegram Trigger works after change in n8n node trigger by * (all), only use message trigger return error, first insert a trigger by message after insert another trigger with * all, start workflow, enjoy.

marcodg · July 21, 2025, 6:10pm

I am self hosting (gcloud) and also getting this error and it just seems to come and go. I can’t find a way to consistently make it stop, it just seem to “just work” at some point, after I try to toggle the workflow on and off, save, reload and so on. It’s very annoying.

xavier.engineering · July 24, 2025, 2:41pm

Changed the “Trigger On” event in the Telegram Trigger to:

All updates

This worked for me, thanks

Kiremit · July 25, 2025, 1:46pm

Doesnt work at all

Juan_Guerrero · July 27, 2025, 5:02pm

In my case, since I haven’t found any fix, and since I use Docker Compose. I need to restart the Docker. I read this is a DNS issue.

jabbson · July 27, 2025, 5:27pm

What worked for me was resetting the url for the bot with this type of request:

After running this, the webhook works again.

Kiremit · July 28, 2025, 7:05am

what worked for me was deleting the Telegram Trigger node as well as the credential and reconnecting it right away

Asela_bro · August 1, 2025, 7:48am

In my case, I got the same issue for DNS related problem, I used Cloudflare to manage my DNS and use proxied mode, In my server I also setup the “Traefik” with docker compose,

What I did is change the Cloudflare to only DNS mode and let Traefik to handle SSL staff, now it’s working.

Imam_Assidiqqi · August 8, 2025, 10:14pm

In case it will help someone in the future, what works for me is that I ensure at least single message has been sent to given bot channel

hlardiez · August 9, 2025, 2:27am

In self hosted, there is an issue w/the webhook url: it is set to be http instead of https. In my mind it ia bug of n8n that should accept both http and https in self hosted. This happens both in linux and windows.
Additional software like ngrok is required to bypass the http and https situation

subashchandraa · August 9, 2025, 7:33am

Can you explain how you did this?

artiekra · August 9, 2025, 7:53pm

in my case, simply saving the workflow, and then just opening it again (leaving and going back) has helped fix the issue

akcom · August 17, 2025, 12:20pm

I also have this issue, and these steps help me:

You need to have a public domain for your n8n deployment - with localhost it will be much harder (need use ngrok)
You need to set both ENV variables: WEBHOOK_URL & WEBHOOK_TUNNEL_URL with the same URL
This URL must start with ‘https://’ next your domain and then finish with ‘/‘
Do not use word ‘webhook‘ in this URL

jabbson · August 17, 2025, 4:28pm

This option is deprecated and removed in 1.0