Telegram Bot Not Receiving Messages or Being Triggered, Despite Successful Outgoing Messages

Questions
,
1

Problem Description

Hi everyone, I’m trying to send a message from my Telegram bot, but the Telegram Trigger on Message doesn’t receive anything and is not triggered. However, sending messages to Telegram works fine from Messages Action to my chat.

I’ve tested this with the following versions: 1.78.1, 1.79.3, 1.94.0, and 1.94.1.
Error Message
There are no error messages shown.
Question
Does anyone have an idea of what might be causing this issue or how I can solve it?

My docker Compose for n8n:

version: '3.9'

services:
  n8n:
    image: n8nio/n8n:1.94.1
    container_name: n8n
    restart: always
    ports:
      - "5678:5678"
    environment:
      - N8N_HOST=n8n.sasan.ir
      - N8N_PROTOCOL=https
      - WEBHOOK_URL=https://n8n.sasan.ir
      - VUE_APP_URL=https://n8n.sasan.ir
      - N8N_RUNNERS_ENABLED=true
      - TZ=Asia/Tehran
      - N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS=true

    networks:
      - nginx-network
    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:5678/health"]
      interval: 30s
      timeout: 10s
      retries: 3

volumes:
  n8n_data:

networks:
  nginx-network:
    external: true

Also here is my nginx config

    server {
        listen 80;
        server_name n8n.sasan.ir;
        return 301 https://$host$request_uri;
    }
    server {
        listen 32443 ssl;
        listen 443 ssl;
        server_name n8n.sasan.ir;

        ssl_certificate /etc/letsencrypt/live/n8n.sasan.ir/fullchain.pem;
        ssl_certificate_key /etc/letsencrypt/live/n8n.sasan.ir/privkey.pem;

        location / {
            proxy_pass http://n8n:5678;
            proxy_set_header Host $host;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header X-Forwarded-Proto $scheme;
            proxy_set_header Upgrade $http_upgrade; 
            proxy_set_header Connection "Upgrade";

        }
        add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
        add_header X-Content-Type-Options nosniff;
        add_header X-Frame-Options "SAMEORIGIN";
        add_header X-Xss-Protection "1; mode=block";
    }

Information on your n8n setup

  • n8n version:
  • Running n8n via (Docker):
2

hello @Sasan_Askari

check the health status of the trigger
https://api.telegram.org/<your_bot_token>/getWebhookInfo

Most probably there is an issue with the webhook, or there is another webhook configured

1 Like