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?