Help Needed: Telegram Trigger Webhook Error (HTTPS URL Required) - n8n v1.97 Docker

Dear n8n Community / Support,

I am encountering an issue with a Telegram Trigger in one of my n8n workflows, and I’m seeking assistance to resolve it.


Describe the problem/error/question

The core problem is that my Telegram Trigger node is failing because it’s expecting an HTTPS URL for the webhook, but seems to be receiving or generating an HTTP one. This prevents the workflow from running.

What is the error message (if any)?

When the workflow attempts to run, it immediately fails with the following error message:

Problem running workflow
Bad request - please check your parameters

Show Details
Telegram Trigger: Bad Request: bad webhook: An HTTPS URL must be provided for webhook

content_copydownload

Use code with caution.


Share the output returned by the last node

(In this case, the workflow is failing at the trigger itself. The error message above is the primary output. If there are any other relevant logs from the n8n console or Docker logs that might provide more context, please include them here.)

The primary output is the error message shown in the “Problem Description” section. There is no successful execution output.

// If you have any additional relevant logs from the n8n console or Docker for this specific failure, paste them here.

content_copydownload

Use code with caution.


Information on your n8n setup

  • n8n version: 1.97

  • Database (default: SQLite): Default (SQLite)

  • n8n EXECUTIONS_PROCESS setting (default: own, main): Default (own, main)

  • Running n8n via: Docker

  • Operating system: Windows 10


What I Understand from the Error:

The error “An HTTPS URL must be provided for webhook” clearly indicates that Telegram requires a secure (HTTPS) connection for its webhooks, but my n8n instance is somehow providing an HTTP URL or is not accessible via HTTPS.

What I’ve Checked / My Suspicions:

  1. WEBHOOK_URL Environment Variable: I suspect this might be related to the WEBHOOK_URL environment variable not being correctly set to an HTTPS URL in my n8n Docker configuration.

  2. External Access / SSL Configuration: My n8n instance is accessible from the internet. I’m unsure if it’s directly exposed or if it’s behind a reverse proxy (like Nginx, Caddy, or Traefik), and whether the SSL/TLS configuration (e.g., Let’s Encrypt certificates) is correctly set up to provide HTTPS for n8n’s public access.

Could you please advise on the following?

  • What are the most common reasons for this specific “An HTTPS URL must be provided for webhook” error when running n8n in Docker?

  • How can I verify that my WEBHOOK_URL is correctly set to an HTTPS address within my n8n Docker environment?

  • How can I determine if my n8n instance (running in Docker) is being accessed directly or via a reverse proxy?

  • Once I know this, what are the common ways to ensure HTTPS is correctly configured for external access to my n8n instance, especially for webhooks?

  • If a reverse proxy is involved, what specific configurations should I check to ensure HTTPS is properly handled and passed to n8n?

Any guidance or troubleshooting steps would be greatly appreciated.

Thank you for your time and assistance.

Best regards,

Rubens

Where is your n8n hosted?
I had this issue when I had it hosted locally on my personal PC.
As soon as I switched to Hostinger hosting, issue was solved.

My n8n is hosted locally using Docker, I’m going to try to host it on a cloud service. Thanks for the tip.