Connection lost after upgrade to 1.88.0

The problem

Issue n8n-io/n8n#14653 (closed, 80 comments): ### Bug Description After the upgrade I started to get error index-D76xStxp.js:293035 [WebSocketClient] Connection lost, code=1008 onConnectionLost @ index-D76xStxp.js:29303 ### To Reproduce 1. Use nginx with reverse proxy 2. Upgrade to 1.88.0 3. WS failing to connect ### Expected behavior WS works as intended ### Operating System Ubuntu 22.04.5 LTS ### n8n Version 1.88.0 ### Node.js Version 21.7.3 ### Database PostgreSQL ### Execution mode main (default)

The verified fix

After upgrading to 1.88.0, the editor websocket (/rest/push) failed with code 1008 behind nginx reverse proxies. Reporter-confirmed fix (antman1p): add an explicit nginx location block for /rest/push with proxyhttpversion 1.1, Upgrade/Connection headers and Origin/X-Forwarded headers, e.g. location /rest/push { proxypass http://n8n:5678; proxysetheader Upgrade $httpupgrade; proxysetheader Connection 'upgrade'; proxysetheader Origin ...; }. Member Joffcom closed the issue after the nginx-config guidance resolved it.

In gh:n8n-io/n8n#14653 (https://github.com/n8n-io/n8n/issues/14653), someone reported: Issue n8n-io/n8n#14653 (closed, 80 comments): ### Bug Description After the upgrade I started to get error index-D76xStxp.js:293035 [WebSocketClient] Connection lost, code=1008 onConnectionLost @ index-D76xStxp.js:29303 ### To Reproduce 1. Use nginx with reverse proxy 2. Upgrade to 1.88.0 3. WS failing to connect ### Expected behavior WS works as intended ### Operating System Ubuntu 22.04.5 LTS ### n8n Version 1.88.0 ### Node.js Version 21.7.3 ### Database PostgreSQL ### Execution mode main (default) The verified resolution from the thread: After upgrading to 1.88.0, the editor websocket (/rest/push) failed with code 1008 behind nginx reverse proxies. Reporter-confirmed fix (antman1p): add an explicit nginx location block for /rest/push with proxyhttpversion 1.1, Upgrade/Connection headers and Origin/X-Forwarded headers, e.g. location /rest/push { proxypass http://n8n:5678; proxysetheader Upgrade $httpupgrade; proxysetheader Connection 'upgrade'; proxysetheader Origin ...; }. Member Joffcom closed the issue after the nginx-config guidance resolved it.