Describe the problem/error/question
On the newest version 1.88.0 there is connection lost error - Monosnap
What is the error message (if any)?
Connection lost
Please share your workflow
On every workflow
Information on your n8n setup
n8n version: 1.88.0
Database (default: SQLite): default
n8n EXECUTIONS_PROCESS setting (default: own, main): own
Running n8n via (Docker, npm, n8n cloud, desktop app): docker
Operating system: linux ubuntu
1 Like
Hi, are you using a reverse proxy?
Reg,
J.
Hi, J,
yes, I am with reverse proxy.
Regards, S.
Hi, you probably need to configure it to allow it to upgrade the connection to websocket.
Reg,
J.
netroy
April 10, 2025, 8:43pm
5
Besides configuring the reverse proxy for Websockets, you all need to pass through the Host
and the Origin
headers through the proxy to the n8n server.
I also have the same problem. I’m running n8n on EKS over a load balancer. 1.86.1 and other previous versions work fine, but 1.88.0 does not. I suspect it has something to do with my ingress file, but I don’t know exactly what to add or modify. What changed in this version, and is there a guide to adjusting my config to match?
1 Like
I solved the problem by changing this environment variable:
N8N_PUSH_BACKEND=sse
To this:
N8N_PUSH_BACKEND=websocket
Hope this helps!
4 Likes
Only works when downgrading to 1.86.1, the above versions still have the socket connection error
Hi @Aethera_Dev ,
Does this work in general? Cause I am using N8N on a Google Cloud Project using NGINX as a reverse proxy following this guide:
Guide on how to fully self-host n8n in a GCP project with up to no monthly costs (depending on the workflows you might pay networking costs, see: [GCP Network Pricing](https://cloud.google.com/vpc/network-pricing)) as well as auto-update the Docker image whenever the open-source GitHub repo of n8n has another release.
@Aethera_Dev tried that and still shows same connection issues.
1 Like
Cally
April 17, 2025, 8:12am
12
Yes, the issue has been resolved by setting N8N_PUSH_BACKEND=websocket.
rwakc
April 18, 2025, 7:46am
13
I am also still experiencing the same issues
Docke compose
n8n:
image: docker.n8n.io/n8nio/n8n
restart: always
environment:
- DB_TYPE=postgresdb
- DB_POSTGRESDB_HOST=postgres
- DB_POSTGRESDB_PORT=5432
- DB_POSTGRESDB_DATABASE=${POSTGRES_DB}
- DB_POSTGRESDB_USER=${POSTGRES_NON_ROOT_USER}
- DB_POSTGRESDB_PASSWORD=${POSTGRES_NON_ROOT_PASSWORD}
- TZ=“Europe/Ljubljana”
- N8N_PUSH_BACKEND=websocket
- N8N_HOST=“url.com ”
- WEBHOOK_TUNNEL_URL=“https://url.com ”
- WEBHOOK_URL=“https://url.com ”
- VUE_APP_URL_BASE_API=“https://url.com ”
NGINX PROXY
server {
server_name n8n…com;
listen 80 ;
return 301 https://$host$request_uri;
}
server {
server_name n8n…com;
listen 443 ssl http2;
ssl_protocols TLSv1.2 TLSv1.3;
ssl_prefer_server_ciphers on;
ssl_session_timeout 5m;
ssl_session_cache shared:SSL:50m;
ssl_session_tickets off;
ssl_certificate /config/keys/.crt;
ssl_certificate_key /config/keys/.key;
location / {
proxy_pass http://n8n_5678;
proxy_set_header Upgrade $http_upgrade; # Added for WebSocket
proxy_set_header Connection “Upgrade”; # Modified for WebSocket
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
chunked_transfer_encoding off;
proxy_buffering off;
proxy_cache off;
proxy_http_version 1.1;
}
}
system
Closed
April 28, 2025, 6:09am
15
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.