I have a Self Hosted N8N on Digital Ocean inside a Droplet. My Installation was always stable until version n8n:2.15.1 (Stable). For any update after that version I am getting this error which is fluctuating every second : Connection Lost

Questions
1

Describe the problem/error/question

I have a Self Hosted N8N on Digital Ocean inside a Droplet.
My Installation was always stable until version n8n:2.15.1 (Stable).
For any update after that version I am getting this error which is fluctuating every second : Connection Lost
So I am obliged to always roll back to version n8n:2.15.1
Kindly help

What is the error message (if any)? Connection Lost

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • Debug info

    core

    • n8nVersion: 2.15.1
    • platform: docker (self-hosted)
    • nodeJsVersion: 24.13.1
    • nodeEnv: production
    • database: sqlite
    • executionMode: regular
    • concurrency: -1
    • license: enterprise (production)

    storage

    • success: all
    • error: all
    • progress: false
    • manual: true
    • binaryMode: filesystem

    pruning

    • enabled: true
    • maxAge: 192 hours
    • maxCount: 30000 executions

    client

    • userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/147.0.0.0 safari/537.36
    • isTouchDevice: false

    Generated at: 2026-04-28T20:26:40.148Z

3

Thanks. That advice makes sense for Nginx / Nginx Proxy Manager, especially enabling WebSocket support and using N8N_PUSH_BACKEND=websocket. In my case I’m using Caddy, not Nginx, so I applied the Caddy equivalent with proper reverse-proxy headers and kept N8N_PROXY_HOPS=1. The key finding is that the flickering “Connection Lost” started only after upgrading to 2.16.1, and it stopped immediately after rolling back to 2.15.1, so this looks like a version-specific issue on my setup rather than a workflow problem.

However, this is not the solution. Actually the temporary solution for me was to roll back to version 2.15.1 actually I believe this is a version specific issue which started with version 2.16.1 I hope the developers will read this and provide the solution in later versions.

4

I have this Connection Lost message too with my Hostinger/Coolify/Caddy environment.

On the Caddy side, what did you do ? I’m absolutely not a pro of this part, …

Thanks !