WebSocket connection issues with n8n on Jino.ru VPS - "Lost connection to the server"

Questions
1

Hello n8n community,

I’m experiencing persistent WebSocket connection issues with n8n deployed on a VPS from Jino.ru hosting provider. The problem occurs specifically when running workflows - I get “Lost connection to the server” error.

Environment:

Problem Description:
Workflows start but immediately fail with “Lost connection to the server”. This happens regardless of:

  • Using nginx reverse proxy or direct connection
  • Different n8n versions (native, Docker)
  • Various WebSocket configurations
  • EventBus backend (fallback to polling)

What I’ve Tried:

  1. Nginx with WebSocket support:
server {
    listen 80;
    server_name c4dae744e5e6.vps.myjino.ru;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
    proxy_set_header Host $host;
    location / {
        proxy_pass http://localhost:5678;
    }
}
Different n8n configurations:

bash
N8N_PUSH_BACKEND=websocket N8N_PROXY_HOPS=1 n8n start
N8N_PUSH_BACKEND=eventbus n8n start
Environment variables:

bash
N8N_HOST=c4dae744e5e6.vps.myjino.ru
WEBHOOK_URL=https://c4dae744e5e6.vps.myjino.ru
N8N_PROTOCOL=https
Error Logs:

Origin header does NOT match the expected origin.
ResponseError: Invalid origin!
Suspicion:
The hosting provider (Jino.ru) might be blocking or interfering with WebSocket connections, despite standard configurations working elsewhere.

Questions:

Has anyone successfully deployed n8n on Jino.ru VPS?
Are there known issues with specific hosting providers blocking WebSocket?
Any workarounds for WebSocket connectivity issues?
Could this be n8n configuration issue or definitely hosting-related?

The application is accessible via HTTPS, but WebSocket handshake seems to fail. Any help or insights would be greatly appreciated!

Thank you!
2

Based on the search results from [community.n8n.io]( I cannot get n8n to work on my server. I got this websocket error message in console ), this appears to be a common WebSocket configuration issue with reverse proxies.

Try adding these specific headers to your nginx configuration’s location block:

• `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;`

Also set these n8n environment variables: `N8N_CORS_ORIGIN=https://c4dae744e5e6.vps.myjino.ru` and remove `N8N_PROXY_HOPS=1`. If WebSocket issues persist with your hosting provider, try setting `N8N_PUSH_BACKEND=sse` as an alternative to WebSocket connections, which may work better with restrictive hosting environments.