> For the complete documentation index, see [llms.txt](https://doc.duaer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.duaer.com/integrations/builtin/trigger-nodes/duaer-nodes-base.telegramtrigger/common-issues.md).

# Common issues with Telegram Trigger in Duaer

Common Telegram Trigger issues in Duaer: stuck while testing, HTTPS required, and test or production only.
## Stuck waiting for a trigger event <a href="#stuck-waiting-for-trigger-event" id="stuck-waiting-for-trigger-event"></a>

When you test Telegram Trigger in the editor, Duaer pushes results back to the page over WebSocket. If a self-hosted Duaer sits behind a reverse proxy that does not forward WebSocket, the page keeps waiting.

Turn on WebSocket forwarding in your proxy (Nginx, Caddy, Traefik, and so on). If you cannot, set DUAER_PUSH_BACKEND to sse. Then close and reopen the digital organization.

## Bad Request: bad webhook: An HTTPS URL must be provided for webhook <a href="#bad-request-bad-webhook-an-https-url-must-be-provided-for-webhook" id="bad-request-bad-webhook-an-https-url-must-be-provided-for-webhook"></a>

Telegram only accepts HTTPS webhook URLs. On self-hosted Duaer, set up TLS on the reverse proxy, then set DUAER_WEBHOOK_URL to the public https:// address.

## Only testing or production receives messages <a href="#workflow-only-works-in-testing-or-production" id="workflow-only-works-in-testing-or-production"></a>

A bot can register one webhook. Each switch between the test and production URL overwrites it, so a published digital organization and an editor test cannot both receive messages. Unpublish while testing, or create a separate bot for testing.
## Questions

### Why does the Duaer Telegram Trigger miss messages while testing?

A Telegram bot registers one webhook. If the Duaer digital organization is published, unpublish before testing or use a separate test bot.