You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In fact esphome don't accept the normal way of nginx is transmiting the browser request host and port to esphome throught ha ingress.
by default when firewall is on front and expose the nginx with diferent port than the nginx port (is the case of nginx proxy manager ha addons is 443) this port are not transmited by default by nginx (nginx use the 443 port in place), and the esphome refuse the connection.
For example:
firewall on port 12345 on public ip -> homeassistant nginx proxy manager port 443 on ha private ip (ex: 192.168.xx.xx the ha os ip) -> homeassistant core ui on 8123 (on local container private ip)
with the way of nginx do the 12345 port are not transmited to the backend (the backend receive 443 in place)...
I've found a "clean way" to fix this use of ha ingress with esphome using NGINX proxy manager addon (base on exchange on esphome/issues#1035 (comment)) by using custom location of nginx proxy manager.
i've added the location /api/hassio_ingress/ on the Proxy Host to homeassistant/api/hassio_ingress/ on 8123 port, with http protocol:
and i've added the custom configuration :
proxy_set_header Host $http_host;
to force to use the hostnameANDport from the browser as transmited by using ($http_host nginx variable) the Host header received in place of the nginx variable $host that not containe the request port.
In fact esphome don't accept the normal way of nginx is transmiting the browser request host and port to esphome throught ha ingress.
by default when firewall is on front and expose the nginx with diferent port than the nginx port (is the case of nginx proxy manager ha addons is 443) this port are not transmited by default by nginx (nginx use the 443 port in place), and the esphome refuse the connection.
For example:
with the way of nginx do the 12345 port are not transmited to the backend (the backend receive 443 in place)...
I've found a "clean way" to fix this use of ha ingress with esphome using NGINX proxy manager addon (base on exchange on esphome/issues#1035 (comment)) by using
custom location
ofnginx proxy manager
.i've added the location
/api/hassio_ingress/
on theProxy Host
tohomeassistant/api/hassio_ingress/
on8123
port, withhttp
protocol:and i've added the custom configuration :
to force to use the
hostname
ANDport
from the browser as transmited by using ($http_host
nginx variable) theHost
header received in place of the nginx variable$host
that not containe the request port.and also configured
Websockets support
on theproxy host
:The text was updated successfully, but these errors were encountered: