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
Clicking "Open WEB UI" when connected remotely does not work: it tries to open http://<my-url>:5050/ but when connected remotely (DDNS and exposed HA on HTTPS), I don't necessarily have that NAT-ed.
In fact, I don't want to NAT this, because there's no authentication on there so it clearly can't be opened to outside.
Then one should bind to the ingress port instead of to a fully exposed port, and it would:
work
be more secure (because it would now be authenticated by HomeAssistant instead of being exposed without authentication on the local network)
Version
4.4.2
Installation type
Home Assistant add-on (0.16.7)
(Not sure if maybe I should have opened this on https://github.com/hassio-addons/repository instead but that repository seems maybe a bit too general and it looks like a change might need to happen here as well although I'm not sure.)
Solving
(Updated after discussions below)
For ingress:
The application needs to support being served from a path, i.e. /somefolder/mypath. This can be a challenge for apps which assume everything is served from root (i.e. Javascript/asset loads etc)
Making the app work that way would then allow using the ingress feature.
The text was updated successfully, but these errors were encountered:
Hi there -
This issue seems to be related to networking for the AppDaemon addon, which is not developed or supported by this team. I suggest you open an issue with the addon's author.
The application needs to support being served from a path, i.e. /somefolder/mypath. This can be a challenge for apps which assume everything is served from root (i.e. Javascript/asset loads etc)
What happened?
Clicking "Open WEB UI" when connected remotely does not work: it tries to open
http://<my-url>:5050/
but when connected remotely (DDNS and exposed HA on HTTPS), I don't necessarily have that NAT-ed.In fact, I don't want to NAT this, because there's no authentication on there so it clearly can't be opened to outside.
There is demand for this to work: https://community.home-assistant.io/t/solved-unable-to-connect-to-web-ui/134193/6
My understanding is that HomeAssistant has a feature called "Ingress" that enables exposing the web UI as an iframe within Home Assistant:
Then one should bind to the ingress port instead of to a fully exposed port, and it would:
Version
4.4.2
Installation type
Home Assistant add-on (0.16.7)
(Not sure if maybe I should have opened this on https://github.com/hassio-addons/repository instead but that repository seems maybe a bit too general and it looks like a change might need to happen here as well although I'm not sure.)
Solving
(Updated after discussions below)
For ingress:
Making the app work that way would then allow using the ingress feature.
The text was updated successfully, but these errors were encountered: