n8n · Telegram Trigger and Google Sheets Trigger nodes
Stuck waiting for trigger event
Short answer
An n8n trigger test that appears stuck listening for events often means n8n runs behind a reverse proxy without websocket proxying configured. Check your reverse proxy configuration (Nginx, Caddy, Apache HTTP Server, Traefik and so on) to enable websocket support.
VerifiedLast verified
01Error text
Stuck waiting for trigger event02Likely causes
- Issues with your network configuration outside of n8n.
- n8n runs behind a reverse proxy without websocket proxying configured.
03How to fix it
- Check your reverse proxy configuration (Nginx, Caddy, Apache HTTP Server, Traefik and so on) to enable websocket support.
- If the canvas is stuck, exit the workflow and open it again to reset it.
04Official documentation
→Related errors
- Invalid cron expressionThis n8n Schedule Trigger error occurs when Trigger Interval is set to Custom (Cron) and n8n does not understand your cron expression. Check that your cron expression follows the syntax used in the n8n cron examples.
- Only one webhook per path and methodn8n shows this message because it only permits registering one webhook for each path and HTTP method combination. Unpublish the workflow with the conflicting webhook.
- 524 timeout on n8n Cloud webhooksAn incoming webhook request on n8n Cloud fails with a 524 status code if your webhook does not respond within 100 seconds. For long-running processes, introduce polling logic with two separate webhooks.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for n8n work:Open n8n jobsn8n rates and salaries