Help with Telegram n8n node

Questions
1

I am utilizing a self hosted n8n instance (in docker). I am accessing my n8n instance via Cloudflare Tunnel, with a published application route directing to the n8n.vtinc.com.br subdomain.
No specific path was specified.

After multiple hours of trying, I could not make the webhook (nor the telegram trigger) to function (at all).

Actions (sending messages, editing messages, deleting messages) works as expected.

Describe the problem/error/question

Non-Functional Webhook Integration, with Telegram Trigger. Observed with the Webhook Trigger, but inconsistent.

What is the error message (if any)?

The Webhook returns a 403 Error or “provided secret is invalid”

Command (n8n provided for Telegram):
curl -X POST “https://n8n.vtinc.com.br/webhook-test/—————–/webhook”
{“message”:“Provided secret is not valid”}

Please share your workflow

Share the output returned by the webhook?

{
“ok”: true,
“result”: {
“url”: “https://n8n.vtinc.com.br/webhook/---------4e87-45b1-9f93-b025--------”,
“has_custom_certificate”: false,
“pending_update_count”: 5,
“last_error_date”: 1760138512,
“last_error_message”: “Wrong response from the webhook: 403 Forbidden”,
“max_connections”: 40,
“ip_address”: “—.—.–.-”
}
}

(Telegram API Information; n8n does NOT return any errors, since the webhook is never triggered)

Docker Compose Config:

services:
  n8n:
    image: docker.n8n.io/n8nio/n8n
    container_name: n8n
    ports:
      - "5678:5678"

    environment:
      GENERIC_TIMEZONE: "America/Sao_Paulo"
      TZ: "America/Sao_Paulo"
      N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS: "true"
      N8N_RUNNERS_ENABLED: "true"
      N8N_SECURE_COOKIE: "false"
      N8N_HOST: "n8n.vtinc.com.br"
      WEBHOOK_URL: "https://n8n.vtinc.com.br"
      N8N_USE_PROXY: "true"
      N8N_TRUSTED_PROXIES: "loopback,linklocal,uniquelocal"
      N8N_DIAGNOSTICS_ENABLED: "false"

    volumes:
      - n8n_data:/home/node/.n8n
      - /var/run/docker.sock:/var/run/docker.sock

    restart: unless-stopped
    tty: true
    stdin_open: true

volumes:
  n8n_data:

Debug Info

[details="instance information"]
# Debug info

## core

- n8nVersion: 1.114.4
- platform: docker (self-hosted)
- nodeJsVersion: 22.19.0
- nodeEnv: production
- database: sqlite
- executionMode: regular
- concurrency: -1
- license: enterprise (production)
- consumerId: 294b5f9d-7151-----------0617950c518d

## 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/535.0 (khtml, like gecko) chrome/139.0.0.0 safari/535.0
- isTouchDevice: false

## security

- secureCookie: false

Generated at: 2025-10-10T23:31:29.223Z
[/details]

P.S I know that the secure cookie setting is not exactly secure, but I kinda need the http settings.

PS2: Is my configuration adequate and complete?

Information on your n8n setup

  • n8n version: 1.114.4
  • Database (default: SQLite): SQLite
  • n8n EXECUTIONS_PROCESS setting (default: own, main): Default
  • Running n8n via Docker Compose
  • Operating system: Debian 13
2 
Do this too in .env and in dockercompose file

- WEBHOOK_URL=https:
- N8N_HOST=https:
- N8N_EDITOR_BASE_URL=https:
- WEBHOOK_TUNNEL_URL=https:

than this or with your gpu (if you are on self hostet ai starter kit)

docker compose --profile cpu up

3

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.