# Telegram Trigger Webhook Issue **URL:** \ **Category:** Questions\ **Tags:** telegram, telegram-trigger\ **Created:** [April 12, 2025, 8:20am UTC](https://community.n8n.io/t/telegram-trigger-webhook-issue/100237 "2025-04-12T08:20:02Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Mohamed\_Al-Adawy](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/mohamed_al-adawy/32/72543_2.png) [@Mohamed\_Al-Adawy](https://community.n8n.io/u/Mohamed_Al-Adawy)\ **Post date:** [April 12, 2025, 8:20am UTC](https://community.n8n.io/t/telegram-trigger-webhook-issue/100237/1 "2025-04-12T08:20:03Z")
## 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)? ```auto 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 ---
**Author:** ![barn4k](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/barn4k/32/8170_2.png) [@barn4k](https://community.n8n.io/u/barn4k)\ **Post date:** [April 12, 2025, 11:34am UTC](https://community.n8n.io/t/telegram-trigger-webhook-issue/100237/2 "2025-04-12T11:34:25Z")
Seems the container can’t resolve DNS entries. You can check with the HTTP node if `https://api.telegram.org` is available. ---
**Author:** ![bookeat](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/bookeat/32/72925_2.png) [@bookeat](https://community.n8n.io/u/bookeat)\ **Post date:** [April 14, 2025, 3:52am UTC](https://community.n8n.io/t/telegram-trigger-webhook-issue/100237/3 "2025-04-14T03:52:09Z")
你可以详细讲讲吗？我也遇到了同样的问题。 Could you please explain in detail? I have encountered the same problem. 🙂 ---
**Author:** ![solomon](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/solomon/32/43567_2.png) [@solomon](https://community.n8n.io/u/solomon)\ **Post date:** [April 18, 2025, 7:00pm UTC](https://community.n8n.io/t/telegram-trigger-webhook-issue/100237/4 "2025-04-18T19:00:58Z")
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. ---
**Author:** ![mohamed3nan](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/mohamed3nan/32/188347_2.png) [@mohamed3nan](https://community.n8n.io/u/mohamed3nan)\ **Post date:** [April 18, 2025, 8:08pm UTC](https://community.n8n.io/t/telegram-trigger-webhook-issue/100237/5 "2025-04-18T20:08:28Z")
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/getWebhookInfo` ![image](https://europe1.discourse-cdn.com/n8n/original/3X/1/c/1cad9e5042e7732f8ae16ddf0024096881449b96.png) 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. ---
**Author:** ![tridi](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/tridi/32/109193_2.png) [@tridi](https://community.n8n.io/u/tridi)\ **Post date:** [April 27, 2025, 11:30am UTC](https://community.n8n.io/t/telegram-trigger-webhook-issue/100237/6 "2025-04-27T11:30:42Z")
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=` ---
**Author:** ![lsmelo](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/lsmelo/32/101818_2.png) [@lsmelo](https://community.n8n.io/u/lsmelo)\ **Post date:** [July 20, 2025, 12:48am UTC](https://community.n8n.io/t/telegram-trigger-webhook-issue/100237/8 "2025-07-20T00:48:38Z")
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. ---
**Author:** ![marcodg](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/marcodg/32/102391_2.png) [@marcodg](https://community.n8n.io/u/marcodg)\ **Post date:** [July 21, 2025, 6:10pm UTC](https://community.n8n.io/t/telegram-trigger-webhook-issue/100237/9 "2025-07-21T18:10:09Z")
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. ---
**Author:** ![xavier.engineering](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/xavier.engineering/32/103419_2.png) [@xavier.engineering](https://community.n8n.io/u/xavier.engineering)\ **Post date:** [July 24, 2025, 2:41pm UTC](https://community.n8n.io/t/telegram-trigger-webhook-issue/100237/10 "2025-07-24T14:41:41Z")
Changed the “Trigger On” event in the Telegram Trigger to: - All updates This worked for me, thanks 🙏🏽 ![Screenshot 2025-07-24 at 9.36.37 AM](https://europe1.discourse-cdn.com/n8n/original/3X/1/f/1f444a1a7a022f1df24ebde311cff8581f6f87b3.png) ---
**Author:** ![Kiremit](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/kiremit/32/50045_2.png) [@Kiremit](https://community.n8n.io/u/Kiremit)\ **Post date:** [July 25, 2025, 1:46pm UTC](https://community.n8n.io/t/telegram-trigger-webhook-issue/100237/11 "2025-07-25T13:46:14Z")
Doesnt work at all ---
**Author:** ![Juan\_Guerrero](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/juan_guerrero/32/104364_2.png) [@Juan\_Guerrero](https://community.n8n.io/u/Juan_Guerrero)\ **Post date:** [July 27, 2025, 5:02pm UTC](https://community.n8n.io/t/telegram-trigger-webhook-issue/100237/12 "2025-07-27T17:02:52Z")
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. ---
**Author:** ![jabbson](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/jabbson/32/87328_2.png) [@jabbson](https://community.n8n.io/u/jabbson)\ **Post date:** [July 27, 2025, 5:27pm UTC](https://community.n8n.io/t/telegram-trigger-webhook-issue/100237/13 "2025-07-27T17:27:13Z")
What worked for me was resetting the url for the bot with this type of request: After running this, the webhook works again. ---
**Author:** ![Kiremit](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/kiremit/32/50045_2.png) [@Kiremit](https://community.n8n.io/u/Kiremit)\ **Post date:** [July 28, 2025, 7:05am UTC](https://community.n8n.io/t/telegram-trigger-webhook-issue/100237/14 "2025-07-28T07:05:12Z")
what worked for me was deleting the Telegram Trigger node as well as the credential and reconnecting it right away ---
**Author:** ![Asela\_bro](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/asela_bro/32/105456_2.png) [@Asela\_bro](https://community.n8n.io/u/Asela_bro)\ **Post date:** [August 1, 2025, 7:48am UTC](https://community.n8n.io/t/telegram-trigger-webhook-issue/100237/15 "2025-08-01T07:48:11Z")
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. ---
**Author:** ![Imam\_Assidiqqi](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/imam_assidiqqi/32/46134_2.png) [@Imam\_Assidiqqi](https://community.n8n.io/u/Imam_Assidiqqi)\ **Post date:** [August 8, 2025, 10:14pm UTC](https://community.n8n.io/t/telegram-trigger-webhook-issue/100237/16 "2025-08-08T22:14:34Z")
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 ---
**Author:** ![hlardiez](https://avatars.discourse-cdn.com/v4/letter/h/e5b9ba/32.png) [@hlardiez](https://community.n8n.io/u/hlardiez)\ **Post date:** [August 9, 2025, 2:27am UTC](https://community.n8n.io/t/telegram-trigger-webhook-issue/100237/17 "2025-08-09T02:27:34Z")
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 ---
**Author:** ![subashchandraa](https://avatars.discourse-cdn.com/v4/letter/s/ba8739/32.png) [@subashchandraa](https://community.n8n.io/u/subashchandraa)\ **Post date:** [August 9, 2025, 7:33am UTC](https://community.n8n.io/t/telegram-trigger-webhook-issue/100237/18 "2025-08-09T07:33:12Z")
Can you explain how you did this? ---
**Author:** ![artiekra](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/artiekra/32/108481_2.png) [@artiekra](https://community.n8n.io/u/artiekra)\ **Post date:** [August 9, 2025, 7:53pm UTC](https://community.n8n.io/t/telegram-trigger-webhook-issue/100237/19 "2025-08-09T19:53:36Z")
in my case, simply saving the workflow, and then just opening it again (leaving and going back) has helped fix the issue ---
**Author:** ![akcom](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/akcom/32/59775_2.png) [@akcom](https://community.n8n.io/u/akcom)\ **Post date:** [August 17, 2025, 12:20pm UTC](https://community.n8n.io/t/telegram-trigger-webhook-issue/100237/20 "2025-08-17T12:20:24Z")
I also have this issue, and these steps help me: 1. You need to have a public domain for your n8n deployment - with localhost it will be much harder (need use ngrok) 2. You need to set both ENV variables: WEBHOOK\_URL & WEBHOOK\_TUNNEL\_URL with the same URL 3. This URL must start with ‘https://’ next your domain and then finish with ‘/‘ 4. Do not use word ‘webhook‘ in this URL ---
**Author:** ![jabbson](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/jabbson/32/87328_2.png) [@jabbson](https://community.n8n.io/u/jabbson)\ **Post date:** [August 17, 2025, 4:28pm UTC](https://community.n8n.io/t/telegram-trigger-webhook-issue/100237/21 "2025-08-17T16:28:08Z")
> [@akcom](#): > > WEBHOOK\_TUNNEL\_URL This option is deprecated and removed in 1.0 > **[n8n v1.0 migration guide | n8n Docs](https://docs.n8n.io/1-0-migration-checklist/#removed-webhook_tunnel_url)** > > What's new in version 1 [Next page](https://community.n8n.io/t/telegram-trigger-webhook-issue/100237.md?page=2)