Apr 8 • Annonces 🆕
Telegram Trigger Node Doesn’t Work in Test or Production (Self-Hosted, No Auth)
G’day,I’ve got a fresh bot and a clean n8n self-hosted setup running behind Caddy with valid HTTPS and no authentication (N8N_BASIC_AUTH_ACTIVE=false). The Telegram Trigger node refuses to work in either test or production mode.
What I’ve Done:
- Created a brand new Telegram bot
- Confirmed the bot works via getWebhookInfo and setWebhook
- Telegram replies with "Webhook was set"
- Confirmed the webhook URL is public, no auth popup, shows 404 for GET (as expected)
- Created Telegram API credentials in n8n with correct bot token
- Connected those credentials in the Telegram Trigger node
- Set to “on message” event
- Tried both Test and Production modes
The Problem:
- In test mode, the node listens but never receives messages
- In production mode, activating the workflow fails silently and reverts to test mode
- Webhook is registered on Telegram’s end, but n8n never responds
- Tried restarting containers, removing basic auth, checking .env, confirming webhook reachability
Expected:
The Telegram Trigger should work in either mode and react to messages.
Actual:
It does nothing. Even getUpdates is blocked due to the webhook being live, which confirms Telegram’s side is working. n8n just never responds to the webhook.
Can someone from the team help confirm if this is a known issue?
1
1 comment
Telegram Trigger Node Doesn’t Work in Test or Production (Self-Hosted, No Auth)
powered by
skool.com/nocode-ia-goats-gratuit-5370
Communauté francophone 🇫🇷
NoCode, automatisations & chilling
Suggested communities
Powered by