Telegram - Cannot execute Telegram node

[roeea2]

Bug Description

Describe the problem/error/question

I cannot activate Telegram trigger or a regular Telegram, it happens not 100% but a lot, after few minutes its being back to normal - but it is really annoying.

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/screenshots/recording

https://www.loom.com/share/7a5246627b17469b8b7b641afdb79e91

Share the output returned by the last node

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

Generated at: 2025-08-25T12:15:44.365Z}

To Reproduce

1. Move to Editor mode
2. Add. a Telegram Node
3. Click on Execute workflow
4. Or click on the node and click on execute Step

Expected behavior

The workflow should start running

Debug Info

1.107.3
Source Codehttps://github.com/n8n-io/n8n
LicenseSustainable Use License + n8n Enterprise License
Instance ID3efbe569e558a18a54352d7073a74807fb3f352c1b3f6b3fdfb719b0cd89fe51
Debug
Copy debug information

Operating System

Linux srv964386 6.8.0-78-generic #78-Ubuntu SMP PREEMPT_DYNAMIC Tue Aug 12 11:34:18 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux

n8n Version

1.107.3

Node.js Version

v18.19.1

Database

SQLite (default)

Execution mode

main (default)

Hosting

self hosted

[Joffcom]

Hey @roeea2,

Thank you for reaching out! We’ve received your issue and are looking into it. To help us track this internally, we’ve created a Linear ticket with the reference: "GHC-3994".

We’ll keep you updated as we make progress, but if you have any additional details or context to share, feel free to add them here - it’s always helpful!

Thanks for your patience and for bringing this to our attention.

[Joffcom]

Hey @roeea2,

This seems to be one of those issues that can happen with Telegram, This is not an issue with n8n itself though. Telegram is returning an error to say it can't resolve the webhook url but looking around I can see reports of this dating back to 2019 from various other projects.

For now as this is not something we can really fix I am going to mark this as closed but I will see if we can maybe capture that error message and make it clearer that Telegram is having an issue.

[roeea2]

Yes, please catch the error as when Im cleaning the cache it DOES work. Please share the error message from TG Roee Aizman E: ***@***.*** M: +972-542345222 http://www.linkedin.com/in/roeea

…

On Tue, Aug 26, 2025, 12:55 Jon ***@***.***> wrote: *Joffcom* left a comment (n8n-io/n8n#18743) <#18743 (comment)> Hey @roeea2 <https://github.com/roeea2>, This seems to be one of those issues that can happen with Telegram, This is not an issue with n8n itself though. Telegram is returning an error to say it can't resolve the webhook url but looking around I can see reports of this dating back to 2019 from various other projects. For now as this is not something we can really fix I am going to mark this as closed but I will see if we can maybe capture that error message and make it clearer that Telegram is having an issue. — Reply to this email directly, view it on GitHub <#18743 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJIDQQ2SDRKNEZJLUW6HZ33PQVIDAVCNFSM6AAAAACEXVIW4OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMRTGQ3TGOJQGY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[roeea2]

So when Im setting up a Bot it does bot happening.
When your telegram node is being accepting the token, yiu are doing something wrong

It is indeed an issue with n8n

[roeea2]

Please check you side. Setting up my own bot working great It is something with your set up of the Bot. Roee Aizman E: ***@***.*** M: +972-542345222 http://www.linkedin.com/in/roeea

…

On Tue, Aug 26, 2025, 12:59 Roee Aizman ***@***.***> wrote: Yes, please catch the error as when Im cleaning the cache it DOES work. Please share the error message from TG Roee Aizman E: ***@***.*** M: +972-542345222 http://www.linkedin.com/in/roeea On Tue, Aug 26, 2025, 12:55 Jon ***@***.***> wrote: > *Joffcom* left a comment (n8n-io/n8n#18743) > <#18743 (comment)> > > Hey @roeea2 <https://github.com/roeea2>, > > This seems to be one of those issues that can happen with Telegram, This > is not an issue with n8n itself though. Telegram is returning an error to > say it can't resolve the webhook url but looking around I can see reports > of this dating back to 2019 from various other projects. > > For now as this is not something we can really fix I am going to mark > this as closed but I will see if we can maybe capture that error message > and make it clearer that Telegram is having an issue. > > — > Reply to this email directly, view it on GitHub > <#18743 (comment)>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAJIDQQ2SDRKNEZJLUW6HZ33PQVIDAVCNFSM6AAAAACEXVIW4OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMRTGQ3TGOJQGY> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >

[roeea2]

Please also share the error code