[Solved] n8n Telegram does not work behind reverse proxy

Hi,

I have n8n running on Docker, Synology NAS which uses nginx proxy.

The Telegram trigger is not triggered when I send a message to a Telegram bot I created. The node is spinning but does not receive message.

It appears to be proxy but no idea what to change.

Thanks for your feedback!

I might have extra relevant info:

Telegram trigger doesn't work - Questions - n8n Community

Tried this for my setup https://api.telegram.org/bot 64<=BotApiToken=>/getWebhookInfo

Iow my cert might not

{ "ok": true, "result": { "url": "", "has_custom_certificate": false, "pending_update_count": 23 } }

ChatGPT said:

Yes, this is a response from Telegram’s getWebhookInfo API method, providing details about the webhook status for a Telegram bot. Here’s what each field means:

"ok": true: Indicates that the API request was successful.
"result": Contains the webhook details.

Within "result":

"url": "": The webhook URL is empty, meaning no webhook is currently set up for this bot.
"has_custom_certificate": false: Indicates that no custom certificate is being used (Telegram uses its default if this is false).
"pending_update_count": 23: Indicates there are 23 pending updates (messages or actions) waiting to be delivered to the bot, likely due to the absence of an active webhook.

To resolve this: