Activity
Mon
Wed
Fri
Sun
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
What is this?
Less
More

Memberships

AI Agent Developer Academy

2.4k members • Free

Automation Masters

3.5k members • Free

AI Automation Society

208.5k members • Free

AI Developer Accelerator

10.8k members • Free

Business AI Alliance

8k members • Free

AI Automation Agency Hub

274.8k members • Free

1 contribution to AI Automation Society
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
1-1 of 1
Lynton Reid
1
5points to level up
@lynton-reid-4962
later

Active 184d ago
Joined Jan 27, 2025
Powered by