Apr 8 • Support Needed 💻
Telegram Trigger won’t stay in production mode (self-hosted, no auth)
G’day,
I’ve got n8n self-hosted behind Caddy with SSL.I’ve disabled basic auth (N8N_BASIC_AUTH_ACTIVE=false), and confirmed the webhook is publicly accessible.
Telegram Trigger works fine in test mode (listens and receives messages), but refuses to stay in production mode.
When I flip it to production and re-open the node, it reverts back to test. No errors shown.
I’ve:
- Set N8N_BASIC_AUTH_ACTIVE=false
- Restarted the container fully (docker compose down && up)
- Set the webhook manually (confirmed with getWebhookInfo)
- Confirmed no other workflows are using the bot
- Confirmed webhook endpoint works (no auth prompt, shows 404 for GET)
I’m completely stumped. Anyone seen this before?
0
0 comments
Telegram Trigger won’t stay in production mode (self-hosted, no auth)
skool.com/ai-automation-society
A community built to master no-code AI automations. Join to learn, discuss, and build the systems that will shape the future of work.
Leaderboard (30-day)
1
🔥
+2482
2
🔥
+1132
3
+1055
4
🔥
+887
5
🔥
+722
Powered by