Problem running Telegram Trigger

Help me Build my Workflow
1

Hello everyone, i recently started using n8n and am trying to set up a message telegram trigger. But i am getting the error:

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

I am confused where is the problem. I am using HOSTKEY to host the n8n.

2 Likes
3

Same problem here. Things is this problem happen occasionally, and when I click save the workflow with a Telegram trigger turn on, the error message appear and prevent me to save or sometimes (when the workflow is inactive) prevent me to active the workflow. But if i just do nothing and wait for 10 minutes then i can save and active workflow like normal.

After a bit of research I think this problem related to your domain SSL certificate. But I don’t know the solution for it.

I’m self hosting my n8n too with a domain i bought (very cheap) and looking hard to a way to solve this too. Very annoying.

2 Likes
4

Same here, really annoying thing

5

I also faced this problem and overcame it thanks to the hint from your webhook URL. You can find Webhook URLs in our Telegram Trigger node. In my case, it returns a JSON containing the hint as follows.

"hint": "Click the 'Execute workflow' button on the canvas, then try again. (In test mode, the webhook only works for one call after you click this button)"

It helped me solve the problem.

6

Directly activate the workflow, and in the production environment, the trigger can execute normally

7

When it fails to run in the testing environment, first activate the workflow, execute it once in the production environment, and then switch back to testing mode to run it normally

8

I ran into this exact issue while hosting n8n on a VPS with a DuckDNS domain and Nginx + Certbot. The error was caused by a DNS resolution problem — the server couldn’t resolve my DuckDNS hostname properly.

Here’s what worked for me:

  1. Checked the DNS setup on my VPS with

    cat /etc/resolv.conf

  2. Updated it to use reliable DNS servers (Cloudflare + Google):

    nameserver 1.1.1.1
nameserver 8.8.8.8

  3. Saved the file, tested resolution with

    ping my-subdomain.duckdns.org
dig my-subdomain.duckdns.org

    to make sure it pointed to my VPS’s IP.

  4. Re-registered the Telegram webhook so it pointed to my DuckDNS domain.

After this, the Telegram Trigger node started working again.