Websocket connection wss: failed HTTP authentication failed

[wos]

Hi Folks,

I thought I’ve got finally n8n running, a few weeks ago, after a hard approach.

But now the user (who is working with it - thats not me) experiences strange error messages in browser console … like this:

I’ve searched the forum and the docs ang googled a little, but im not really smarter now. Copilot is suggesting, that I only have to put these 3 lines in docker-compose.yml, then all will be fine:

N8N_BASIC_AUTH_ACTIVE=true
N8N_BASIC_AUTH_USER=a
N8N_BASIC_AUTH_PASSWORD=b

This N8N Instance has no usermanagement active. And the thing, what I can’t understand, is, that the user there, and the passwort … should/could be something arbitrary and has nothing to do with the user in n8n. Why n8n its not generating these things on the fly if its really like this?

So, is copilot hallucinating, or is that right? What sense makes that. I don’t understand it, and i seem, there would be something, what makes sense. But i cant regognize it.

When entering Workflows, it’s the same errors come up, and “Connection Lost” is displayed:

Im Using N8N in a docker environment in Version 1.110.1 and with NPM (Nginx Proxy Manager). Maybe someones could give a hint what would be the right approach to solve this.

Thx

[ReallyeWhine]

WebSocket connection failures are typically caused by HTTP authentication issues. Check the authentication configuration of the WebSocket node in your n8n workflow.

[wos]

Its not that. As i wrote i’m using the NPM (Nginx Proxy Manager), after switching on this …

… the Problem is gone! Don’t know if i need the 3 lines …

N8N_BASIC_AUTH_ACTIVE=true
N8N_BASIC_AUTH_USER=a
N8N_BASIC_AUTH_PASSWORD=b

… or not. I leave them in the config (in reality the user/pass is a bit more complicated as shown here), just glad to see, that’s (hopefully) working now