HA ingress won't work with static built web ui
See original GitHub issueLooks like due to Home Assistant changing the pathname / baseUrl of accessing the HTTP web ui, the paths are broken.
eg: HA ingress uses a path like /api/hassio_ingress/phGvaecS8O1W86zsjRe23F93S-9gU0bQNxv5xjP7ZXs/
and proxies that into the Web UI. Unfortunately, the statically built HTML expects the paths of the JS to be /js/...
, but that means it’s attempting to load from the Home Assistant’s root /js
folder and not the frigate docker container’s host:port/path.
Some other solution will be needed, like running another web server that can understand if it’s being run with ingress and changing the URLs to the built JS/CSS.
Alternatively, an nginx path could be added for /homeassistant
, which could then serve a modified HTML file, though this may be just as much work to maintain, but harder to test and verify.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:31 (18 by maintainers)
Top GitHub Comments
I think we should just update the UI to pull the latest.jpg at an interval. From what I can tell, it’s going to take an update from homeassistant to get it to handle multipart content types properly. This is what happens when you try to build your own proxy.
Looks like ingress modifies the content type headers and breaks mjpeg.