Corrections in N8N VPS installed via Docker, Telegram Trigger does not receive events.

Budget: 4500 UAH Deadline: 2 days

I can take on the diagnostics and fixing of n8n on Hostinger VPS. The timeframe is 1-2 days, budget - 4500 UAH, if the problem lies in the typical combination of Docker, HTTPS, webhook URL, n8n environment variables, port, proxy, or Telegram Trigger settings.

I will start by checking Docker, n8n logs, webhook URL, external accessibility, SSL, N8N_HOST, WEBHOOK_URL, N8N_PROTOCOL variables, and the actual response from the Telegram API. Then I will fix the configuration, restart the container without data loss, and check the actual receipt of events in the workflow. Note, there is a nuance here - in n8n, the Telegram Trigger often seems to listen, but Telegram just cannot reach the correct webhook.

Clarifications
> Is there currently a domain with SSL for n8n, or is it only accessible via IP?
> Is n8n launched via docker compose or a single docker run?

Similar task examples from Ingello
> https://business.ingello.com/fractal - process automation and agent scenario logic
> https://business.ingello.com/vorfahr - integrations, automation, and complex service interaction scenarios

Main Ingello page for the exchange - https://systems-fl.ingello.com/ua

To get started, I need access to the VPS, access to n8n, the name of the Telegram bot without the token in the public chat, and the current docker compose file or launch command. I won’t break anything unnecessary, but I am a technical nerd - I will make a copy of the configuration before making changes =)

After fixing, I will provide a brief summary - what was the cause, what was changed, and how to verify that the trigger is working stably. Expand

Budget: 713 UAH Deadline: 1 day

👋 Hello! I'm ready to start working right now. I clearly understand the task and have successful experience in implementing exactly such projects (examples are in the reviews). I will complete the task today, quickly and without unnecessary questions. Let's discuss the details and get started! 🚀

Budget: 2000 UAH Deadline: 3 days

Hello! I have reviewed the project and am ready to start working. I am confident you will be satisfied with the result.

Budget: 2500 UAH Deadline: 1 day

Good day
I can connect, check the container logs, configure n8n, verify the availability of the webhook externally, the Telegram bot webhook, and after making corrections, test the trigger with a real message.

Budget: 1500 UAH Deadline: 1 day

Hello, I am ready to solve your issue with the trigger, feel free to reach out.

Budget: 1300 UAH Deadline: 1 day

I understood the task: n8n on Docker on Hostinger VPS, the admin panel opens, but the Telegram Trigger in the workflow is stuck in the "listening" status and events from Telegram are not coming. Diagnostics and fixes are needed.

In 90% of cases, the reason is one of three.

First — the webhook URL in the Telegram bot does not match the one registered by n8n. The Telegram Bot API works only in one of two modes: polling (n8n constantly polls getUpdates) or webhook (Telegram pushes events to your URL). The n8n Trigger by default sets the webhook via getWebhookInfo — and if it’s not empty and not your domain, our trigger will never receive updates. This is checked via a direct request to the Bot API getWebhookInfo — if there’s a foreign URL or the URL does not match the WEBHOOK_URL from the n8n env, the webhook must be deleted (deleteWebhook) and let n8n set it again.

Second — incorrect WEBHOOK_URL in the env. If n8n is behind a reverse proxy (nginx) on a subdomain with SSL, then the WEBHOOK_URL must be saint-publicly-resolvable HTTPS, not localhost and not http. Telegram only accepts https webhooks with a valid certificate. If you have Caddy/nginx with Let's Encrypt — you need to ensure that port 443 is publicly accessible and WEBHOOK_URL = https://your-n8n-domain.tld. This is checked via curl from an external machine plus sslscan for validity.

Third — Docker network. If n8n is in a container on a bridge network without published ports, the reverse proxy on the host will not reach the nodejs server inside. This is checked via docker inspect on network mode plus docker port on published ports plus netstat on the host.

What I will do in the work. I will log in to the VPS, look at the docker-compose and n8n env, check the current state of the webhook in the Telegram API directly, look at the n8n logs for the last hour on the Telegram-Trigger node, check the nginx access log for requests from the Telegram IP range. After the diagnosis — a fix (usually this is editing docker-compose.yml + restarting the container, or resetting the webhook via API). We will test together through your bot — I will send a test message, check if the workflow worked and if the subsequent nodes executed.

Please clarify: do you know the login to the Hostinger VPS and do you have root access, how to log in (SSH key or password). If you already know which version of n8n you upgraded to — this will also be useful (there are breaking changes in the Telegram Trigger between 1.40+ and the current versions). Expand

Budget: 700 UAH Deadline: 1 day

Hello, I would be happy to help you for a coffee donation for the bot and feedback)

I had a similar problem, the most likely reasons are:
1) You have incorrectly specified the variable WEBHOOK_URL in the N8N project
2) You do not have a domain connected to N8N
3) You do not have an SSL certificate connected (this is required by Telegram)

Budget: 1300 UAH Deadline: 2 days

Hello, I can help with diagnosing and fixing the Telegram Trigger issue in n8n on VPS. First, we need to look at the current Docker/n8n configuration, webhook URL, and container logs - the problem is often related to the webhook, HTTPS, reverse proxy, or network settings of the VPS. Once I have access, I will be able to check and test the trigger's functionality.

Budget: 700 UAH Deadline: 1 day

Hello! I am ready to complete your task, I have experience working with similar tasks.

Budget: 2000 UAH Deadline: 1 day

Hello!

I specialize in automating business processes and implementing AI agents. I work with n8n, Python, CRM systems, API integrations, and LLM (OpenAI, etc.). I help reduce routine tasks, optimize processes, and increase efficiency.

I am ready to quickly and efficiently complete your task. Let's discuss the details!

Budget: 3000 UAH Deadline: 1 day

Hello. I have extensive experience in developing Telegram bots and with n8n. I am ready to fix the error.

Budget: 3000 UAH Deadline: 1 day

The Telegram Trigger in n8n on Docker is almost always not receiving events due to an incorrectly configured webhook — Telegram simply cannot reach your VPS. Typical reasons include: missing or incorrect WEBHOOK_URL in the Docker configuration, blocked port at the Hostinger firewall level, or n8n not being proxied through HTTPS.

I regularly deploy services on Linux servers via Docker, set up network rules, reverse proxies, and Telegram bots through webhooks. This stack is my daily toolkit.

What I will do: I will check the Docker Compose configuration, the environment variables N8N_HOST and WEBHOOK_URL, the availability of the port from the outside, and the presence of a valid SSL. If necessary, I will reconfigure the reverse proxy, register the webhook manually via the Telegram API, and test the workflow until a complete result is achieved.

Approximately 2-3 hours of work. The final cost will be agreed upon after you share the server configuration details.

Message me — we will sort it out quickly.

Budget: 1000 UAH Deadline: 2 days

Good day, Yevheniy
I am interested in your project and would be happy to collaborate.
I am ready to complete the task, I have experience with this issue.