N8n Test Mode & Chat Trigger Not Working Properly – UI Updates Only After Refresh

Questions
1

I’m experiencing a serious issue with the test mode and real-time execution feedbac* in my self-hosted n8n instance. The problem occurs in multiple ways, making it difficult to work efficiently. Here’s what’s happening:

  1. Test Mode Doesn’t Work Properly
  • When I launch a workflow test in n8n, nothing happens.
  • If I refresh the page, I suddenly see that the test actually executed.
  1. Telegram Trigger Workflow Executes But Doesn’t Show in UI
  • The workflow is triggered successfully via Telegram.
  • I receive the message on Telegram (so the execution is happening).
  • However, the execution does not appear in the n8n UI unless I refresh the page.
  1. Clicking “Stop” in Test Mode Requires Reset
  • If I click the Stop button while testing a workflow, the UI gets stuck.
  • I have to reset everything before I can run another test.
  1. Chat Trigger Workflows Don’t Work at All

The second picture is just an example of a basic workflow, the problem occurs on every workflow with a chat trigger

What I Have Tried:
Restarted n8n and cleared browser cache.
Verified that my instance is correctly configured and running.
Checked WebSockets and API responses.

  • Hosting: DigitalOcean
  • Installation: Docker
  • n8n Version: 1.78
  • Reverse Proxy: Cloudflare Tunnel
    Has anyone experienced something similar? Any suggestions on how to fix this issue?
2

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
3

Can you please try the same in another browser?

I’ve ran into this kind of issue before and the problem was some extension i had installed.

4

Hey,
thank you for the response, but even in another browser it doesn’t work.

5

I had the same problem and the main issue was in the nginx conf.

I follow the indications of this post and it works for me.