Telegram Trigger Webhook Issue

[imtks11]

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.