Hello,
I have a self-hosted N8N instance running on an Oracle Cloud server via Docker, with Caddy as a reverse proxy. My goal is to embed the n8n-chat widget on a Google Site.
The problem is that the workflow execution gets stuck and never finishes. Symptoms:
On the live Google Site, the chat window appears but the text input field is missing.
When I test the workflow inside the N8N editor, the Chat Trigger node receives the message, but the workflow hangs on the response node (Respond to Chat or Respond to Webhook) and it stays in a “Running” state forever. What I have already tried and verified:
My workflow is Active.
I have correctly configured CORS in the Chat Trigger for https://sites.google.com and https://*.googleusercontent.com.
The Response Mode in the Chat Trigger is correctly set to “Using Response Nodes”.
The embed code on my Google Site is using the correct public webhook URL (not localhost).
I have updated my N8N to the latest version using docker pull.
I have even completely reset my N8N installation with a fresh data volume.
The problem persists even with a simple 2-node “Hello World” workflow. I believe this might be a bug. Could you please advise what to try next? I am attaching screenshots of my configuration and the hanging execution.
Thank you!
I could not reproduce the error with the Respond to Chat and Respond to Webhook nodes hanging indefinitely. My current setup is n8n behind Traefik running on Docker, with Cloudflare in front of it, and everything works as expected.
​
Based on your symptoms and setup (Oracle Cloud + Docker + Caddy + Google Sites), my first impression is that the issue is somewhere in the network configuration, specifically between Caddy, your Docker environment variables, and how n8n generates webhook URLs
Suspected Root Cause
The missing input field and workflow hanging are typically caused by:
​
Missing WEBHOOK_URL environment variable → n8n generates URLs with :5678 port
Caddy not properly forwarding WebSocket connections → Chat initialization fails
Initial chat request without chatInput → Workflow fails on first load
