Telegram trigger not working in selfhosted instance

[crey_D]

Bug Description

Hello,
All telegram triggers don’t work for me. I have a public domain with a valid HTTPS certificate. When I use a webhook trigger and curl it, it works without a problem. However as soon as I add any telegram trigger (different bots, different workflows) I don’t receive any events. It also doesn’t matter if I use the test mode or the production mode. This is my docker compose, slightly adjusted from the template provided:

services:
  n8n:
    image: docker.n8n.io/n8nio/n8n
    restart: unless-stopped
    container_name: n8n
    labels:
      - traefik.enable=true
      - traefik.docker.network=traefik_web
      - traefik.http.routers.n8n.rule=Host(`my.domain.test`)
      - traefik.http.routers.n8n.entrypoints=web,websecure
      - traefik.http.routers.n8n.tls=true
      - traefik.http.routers.n8n.tls.certresolver=default
      # https://docs.n8n.io/hosting/installation/server-setups/docker-compose/#6-create-docker-compose-file
      - traefik.http.middlewares.n8n.headers.SSLRedirect=true
      - traefik.http.middlewares.n8n.headers.STSSeconds=315360000
      - traefik.http.middlewares.n8n.headers.browserXSSFilter=true
      - traefik.http.middlewares.n8n.headers.contentTypeNosniff=true
      - traefik.http.middlewares.n8n.headers.forceSTSHeader=true
      - traefik.http.middlewares.n8n.headers.SSLHost=domain.test
      - traefik.http.middlewares.n8n.headers.STSIncludeSubdomains=true
      - traefik.http.middlewares.n8n.headers.STSPreload=true
      - traefik.http.routers.n8n.middlewares=n8n@docker
    environment:
      - N8N_HOST=my.domain.test
      - N8N_PORT=5678
      - N8N_PROTOCOL=https
      - NODE_ENV=production
      - WEBHOOK_URL=https://my.domain.test/
      - N8N_EDITOR_BASE_URL=https://my.domain.test/
      - GENERIC_TIMEZONE=Europe/Berlin
      - N8N_RUNNERS_ENABLED=true
      - N8N_PROXY_HOPS=1
    volumes:
      - /data/n8n/data:/home/node/.n8n
      - /data/n8n/files:/files
    networks:
      - web

networks:
  web:
    name: traefik_web
    external: true

To Reproduce

1. Create telegram trigger in new workflow
2. Click on “test”
   

Expected behavior

Expect to receive test as well as production messages from telegram.

##[details=“instance information”]

Debug Info

Debug info

core

• n8nVersion: 1.104.2
• platform: docker (self-hosted)
• nodeJsVersion: 22.17.0
• database: sqlite
• executionMode: regular
• concurrency: -1
• license: community
• consumerId: unknown

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 (macintosh; intel mac os x 10.15; rv:141.0) gecko/20100101 firefox/141.0
• isTouchDevice: false

Generated at: 2025-08-01T15:45:53.467Z
[/details]

Operating System

Ubuntu Server 22

n8n Version

1.104.2

Node.js Version

22.17.0

Database

SQLite (default)

Execution mode

main (default)

Hosting

self hosted

This was an issue raised but automatically closed on GitHub: Telegram trigger not working in selfhosted instance · Issue #17911 · n8n-io/n8n · GitHub