Connection lost error only in Chromium browsers (Chrome, Edge), Firefox OK

[Laurentfrom47]

Hello,
In chromium based browsers, i have this error in console:

pushConnection.store-BfRLeHNn.js:87 
 WebSocket connection to 'wss://n8n.website.com/rest/push?pushRef=xc88erusrx' failed: Error during WebSocket handshake: 'Connection' header value must contain 'Upgrade'
connect	@	pushConnection.store-BfRLeHNn.js:87

I set the headers in OpenLiteSpeed, but without success.

What is strange is that it works very well with Firefox?

Thank you.

Information on your n8n setup

• n8n version: 1.79.3
• Database (default: SQLite): sqlite
• n8n EXECUTIONS_PROCESS setting (default: own, main): regular
• Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
• Operating system: Ubuntu Openlitespeed

[Exnav29]

Hey @Laurentfrom47

The WebSocket handshake error you’re encountering (Connection header value must contain ‘Upgrade’) in Chromium-based browsers but not in Firefox suggests that your OpenLiteSpeed (OLS) proxy settings might not be correctly forwarding the Connection and Upgrade headers.

Firefox can sometimes be more forgiving with WebSocket upgrades, whereas Chromium-based browsers enforce stricter compliance.

I’ve put together a document with the steps on how you can resolve the handshake error. Steps to Fix the WebSocket Handshake Issue in OpenLiteSpeed.docx - Google Docs

[Laurentfrom47]

Thanks, i don’t see Enable WebSocket Proxy in listeners?

[Exnav29]

Try checking to see if you have the latest OpenLiteSpeed version.

[Laurentfrom47]

I have 1.8.2

[Exnav29]

@Laurentfrom47

Enable WebSocket Proxy

I appreciate your patience while troubleshooting this issue. Since you’re on OpenLiteSpeed v1.8.2, and the latest version is v1.8.3, it’s possible that this is a version-related limitation or bug. At this point, I’ve gone through every possible solution I can think of, and I’m at my wits’ end.

I highly recommend:

Upgrading to v1.8.3 to see if the missing “Enable WebSocket Proxy” setting appears.
Checking OpenLiteSpeed’s forums or GitHub issues in case others have faced the same problem.
Considering switching to a different reverse proxy, like Nginx or Caddy, if WebSocket support remains an issue.
I wish I had a more direct solution, but at this point, I’m out of ideas. Let me know if you do end up finding a workaround!

[Laurentfrom47]

No one has any idea why it only works with Firefox when using OpenLiteSpeed? A bug in n8n?

Thanks.