I just applied the 2025.5.1 update and my NGINX reverse proxy no longer connects. I can connect fine via the IP and port, but using the proxy it sits at the “Unable to connect will retry in 60 seconds” screen. Current NGINX config worked fine on the previous core version, do I need to change any NGINX locations etc. with this core release?
I use Linuxserver.io swag container, and did not have to change anything to the nginx configuration for 2025.5.1
I am having the same issue.
It works but it’s super slow!
Hello,
Just updated to 2025.5.1 and I have the same issue. “Unable to connect” when going though the Nginx reverse proxy, but no issue with direct IP:port. I also didn’t change anything, here is my configuration.yaml :
# Loads default set of integrations. Do not remove.
default_config:
# Load frontend themes from the themes folder
frontend:
themes: !include_dir_merge_named themes
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
http:
# For extra security set this to only accept connections on localhost if NGINX is on the same machine
# Uncommenting this will mean that you can only reach Home Assistant using the proxy, not directly via IP from other clients.
# server_host: 127.0.0.1
use_x_forwarded_for: true
# You must set the trusted proxy IP address so that Home Assistant will properly accept connections
# Set this to your NGINX machine IP, or localhost if hosted on the same machine.
# NGINX IP address here, or 127.0.0.1 if hosted on the same machine>
trusted_proxies: 127.0.0.1
Edit :
I managed to solve this issue by… Commenting this in my nginx conf, reloading, uncommenting then reloading again. So the issue came from nginx ? From my browser cache ? idk
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection “upgrade”;
How could you update to 2025.5?
I’m stuck with 2025.4.4, and pip3 install --upgrade homeassistant installs no newer version?
Update: solved it. The virtual python environment needed an update to a newer python version…
For anyone experiencing the same issue after upgrading… Apparently, my static IP was set to automatic after the upgrade which caused the IP address to change. Setting it back to the correct static IP-address fixed the issue.