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

n8n error
Stuck waiting for trigger event

02Likely causes

  • Issues with your network configuration outside of n8n.
  • n8n runs behind a reverse proxy without websocket proxying configured.

03How to fix it

  1. Check your reverse proxy configuration (Nginx, Caddy, Apache HTTP Server, Traefik and so on) to enable websocket support.
  2. If the canvas is stuck, exit the workflow and open it again to reset it.

04Official documentation

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

The iPaaS Brief

Subscribe to The iPaaS Brief.

The iPaaS newsletter for the people who run integrations. From iPaaS Group.

Free. You finish on theipaasbrief.com and confirm by email.