Connection issue after updating 3.3.6

[sekertr]

After the 3.3.6 update, I have a connection issue. It tries to connect but never connects. I have tried restarting Home Assistant or restarting the addon but to no avail.

n8n add on version: 3.3.6
HA Core: 2025.4.2
HA Supervisor: 2025.04.0
HA Operating System: 15.2
HA Frontend: 20250411.0

[sekertr]

[Rbillon59]

Hello,

Could you send the logs of the addon ?

Thank you

[sekertr]

changed my url to https://homeasistant.mydomain.com

logs.txt

[sekertr]

I went back to version 3.3.5 and everything works.

[ffMathy]

I think this needs to be reported on n8n's repo. It fails for me too on localhost, but if I load it via the Nabu Casa remote URL, it works.

[denug]

same on my end, connection lost keeps blinking inside app so I went to backup 3.3.5 until fix is posted

[sekertr]

This problem was also reported in the n8n repo. Everyone downgrade to version 1.8.6 because 1.8.8 was not working.

[pepelatc]

same problem!

[ffMathy]

@sekertr can you link to the issue on n8n's repo?

[ffMathy]

Progress tracked here: n8n-io/n8n#14769

As soon as that fix comes out, we'll update the addon too. Closing now, as this is not in our scope, but an N8N problem instead.

[gbertsch]

Anyone find a workaround for NPM (Nginx Proxy Manager) ?

[sekertr]

After updating to the latest version (v3.3.9) I realized something.

I don't have n8n connection problem in local network, but in versions released after 3.3.5, although the configuration is the same, the connection error persists in remote connections.

Summary

• No changes were made in addon settings, router and dns settings.
  version 3.3.5 and below:
• http://home:8123/6560bdea_hass-n8n/ingress (working good)
• https://myremoteaddress.com/6560bdea_hass-n8n/ingress (working good)

after version 3.3.5:

• http://home:8123/6560bdea_hass-n8n/ingress (working good)
• https://myremoteaddress.com/6560bdea_hass-n8n/ingress (editor is working, credentials can be created but it has connection issue, so workflows doesnt work)

[sekertr]

I had time to look into this connection issue after a long time. With the last update(3.4.0), the disconnection problem was still there for me. When I looked deeper, it couldn't connect due to websocket's origin error, so it was getting a 'connection lost' error.

I forked this repo to test my homeassistant and change some parameters in nginx.conf file and its working good in last update.

Here is what I added to nginx configuration:

proxy_set_header Origin $scheme://$http_host
proxy_cache off
proxy_buffering off

Full nginx.conf file can be found here

@ffMathy @Rbillon59

[ffMathy]

Well, in that case, let's get it merged in. Create a PR and we'll get it shipped.

[ffMathy]

PR here: #266