n8n Telegram node fails to register webhooks when deployed via Coolify

[aliayoubiaaa]

Bug Description

n8n Telegram node fails to register webhooks when deployed via Coolify
show this 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

how config the server to run the telegam webhook node

To Reproduce

1. Deploy n8n via Coolify: Deploy the n8n service using Coolify's standard template, ensuring it is accessible via a public domain (e.g., https://n8n.example.com).
2. Omit Environment Variables (Crucial): Do not set the N8N_HOST or N8N_PROTOCOL environment variables in the Coolify settings for the n8n application.
3. Create Workflow: Create a new workflow in n8n.
4. Add Telegram Trigger: Add a Telegram Trigger node as the first step.
5. Configure Credentials: Configure the node with valid Telegram Bot Credentials (API Key).
6. Activate Workflow: Attempt to activate the workflow (click the toggle switch in the top right).

Expected behavior

telegam node work

Debug Info

Debug info

core

• n8nVersion: 1.120.4
• platform: docker (self-hosted)
• nodeJsVersion: 22.21.0
• nodeEnv: production
• database: postgres
• executionMode: scaling (single-main)
• concurrency: -1
• license: enterprise (production)
• consumerId: 409834e2-81aa-45f0-b746-2702359bce06

storage

• success: all
• error: all
• progress: false
• manual: true
• binaryMode: memory

pruning

• enabled: true
• maxAge: 336 hours
• maxCount: 10000 executions

client

• userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/142.0.0.0 safari/537.36
• isTouchDevice: false

Generated at: 2025-11-23T05:27:40.841Z

Operating System

ubunutu 24

n8n Version

1.120.4

Node.js Version

22

Database

SQLite (default)

Execution mode

main (default)

Hosting

self hosted

[n8n-assistant]

Hey @aliayoubiaaa,

Thank you for reaching out! We’ve received your issue and are looking into it. To help us track this internally, we’ve created a Linear ticket with the reference: "GHC-5604".

We’ll keep you updated as we make progress, but if you have any additional details or context to share, feel free to add them here - it’s always helpful!

Thanks for your patience and for bringing this to our attention.

---

For INTERNAL use only: GHC-5604

[MookieLian]

Thank you for reaching out! It looks like this issue might be more of a support request rather than a bug report. For general support, troubleshooting, or questions, we recommend raising your request on our community support forum.

The forum is a great place to connect with both our team and other community members who can help out. You might even find answers to similar questions there!

For issues related to n8n cloud billing or instances going offline please email help@n8n.io as we are not able to access your cloud account or workflows from these issues.

We'll go ahead and close this issue to keep the tracker focused on bug reports. Feel free to join the conversation on the forum, and let us know if you have any further concerns or questions.

Thanks again for being part of the n8n community!

#closed:support-issue