How can I configure Telegram webhooks for n8n running locally with Docker?

Based on the documentation for the Telegram Trigger node, the error:

  Bad Request: bad webhook: An HTTPS URL must be provided for webhook

indicates that Telegram requires an HTTPS URL for the webhook. This means that your n8n instance must be accessible via a secure (HTTPS) endpoint. Here are some steps and approaches you can consider:

1. Configure an HTTPS Endpoint for n8n

When you run n8n locally using Docker, you need to ensure that Telegram can call the webhook using an HTTPS URL. You have a couple of options:

• Use a Reverse Proxy with TLS/SSL Termination:
  Set up a reverse proxy server (e.g., Nginx, Caddy, Traefik) in front of your Docker instance. The proxy should handle HTTPS requests and forward them to n8n over HTTP.
  Be sure to configure the WEBHOOK_URL environment variable for n8n with your public HTTPS URL where your instance is accessible.

• Use a Tunneling Service:
  Services like ngrok provide a temporary HTTPS URL that tunnels to your local instance. This is a great option if you’re just testing or use n8n for personal projects. Once ngrok is running, update the WEBHOOK_URL environment variable with the provided HTTPS endpoint.

2. Update the Docker Environment

You will need to update your Docker compose file (or environment file) to set the WEBHOOK_URL variable. If using a reverse proxy or tunneling service, the variable should reflect the HTTPS address, for example:

YAMLCopied
version: "3.5"

services:
  n8n:
    image: n8nio/n8n:1.79.3
    environment:
      - WEBHOOK_URL=https://your-public-domain.com
    ports:
      - "5678:5678"
    # Other configurations...

Replace https://your-public-domain.com with the actual HTTPS URL for your n8n instance.

3. Considerations for a Hobbyist Setup

Since you mentioned that many solutions seem too advanced:

• Tunneling (Ngrok):
  Using a service like ngrok is usually the simplest way to get an HTTPS URL without delving into full reverse proxy configurations. It creates a secure tunnel between the public internet and your local machine with little setup required.

• Reverse Proxy Simplicity:
  If you prefer a reverse proxy, there are plenty of guides that walk you through setting up Nginx or Caddy with TLS certificates from Let’s Encrypt. This might initially seem complex but offers a more permanent solution if you plan to use your instance over a longer period.

Summary

The webhook error is indeed because Telegram requires an HTTPS URL. Using either a reverse proxy with appropriate TLS/SSL termination or a tunneling service like ngrok will resolve this issue. Once you have an HTTPS endpoint, make sure to update your WEBHOOK_URL so that Telegram's webhook registration uses a valid, secure URL.

Let me know if you need more detailed guidance on setting up either solution!