Telegram trigger dont listen | n8n docker selfhosted

[JR_Livre]

n8n version: latest
Database: postgres 13
n8n EXECUTIONS_PROCESS setting: default
Running n8n via: Docker
Operating system: Ubuntu 24.04

Hey N8ners!

I’m facing a small challenge with the n8n and Telegram interaction!
My specific question is about the “Updates:message” trigger: it doesn’t seem to be listening to my event at all! ~:(

I’ve double-checked the credentials and they all show success. The process in Telegram (done through BotFather) has also been reviewed, and everything related to authentication is perfect.

Important fact: the communication remains silent only when using the self-hosted version. I repeated the same workflow, with the same credentials and configurations on the official N8N cloud and the trigger heard the message normally.

Is there any special point to pay attention to in the specific case of an n8n that lives in a Docker? I feel like it could be something about SSL, or public availability issues of the hook… I use LetsEncrypt and Traefik, but can’t assure if tha certificate looks good.

Print 1, with an overview of the workflow. Note that other subsequent Telegram nodes worked when the data was manually inserted into the trigger. In other words, only the trigger listening has problems.

Print 2, testing the trigger on N8N.cloud, under the same credentials.

[n8n]

It looks like your topic is missing some important information. Could you provide the following if applicable.

• n8n version:
• Database (default: SQLite):
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app):
• Operating system:

[Jon]

Hey @JR_Livre,

When you activate the workflow does it show any error messages? If you check the webhook url as well is it using localhost or your correct domain?

[JR_Livre]

Aloha Jon!

No error messages.

When I test trigger alone into N8N “live”, thing goes OK. Furthermore, I tested this by copying the output of the trigger from the N8N cloud version and pasting it into my self-hosted workflow’s trigger. All nodes functioned correctly, except for the trigger itself.

URLs using my own domain.

I suspect that the virtual environment configurations are hindering the trigger’s ability to listen effectively. Unfortunately, I’m unsure which specific settings are causing the issue or how to verify them.

Thanks in advance, have a nice week

[brauliodiasribeiro]

I have a problem with Telegram and I believe it may be the Nginx Proxy Manager.

My installation is self-hosted.
I have the WEBHOOK_URL with my website “https://n8n.mysite.com”
In Nginx Proxy Manager I have a valid certificate and I needed to configure it to work on my domain. Here it is:

location / {
proxy_pass http://192.168.10.254:5678;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection “Upgrade”;
proxy_set_header Host $host;
chunked_transfer_encoding off;
proxy_buffering off;
proxy_cache off;
}

I don’t receive a message in the Telegram trigger, and when I click to activate flow, this error appears too.

Workflow could not be activated:
Can’t connect to n8n.