[Bug]: [HA Addon] Frigate UI generally works through HA Ingress but issue some direct API requests w/o ingress which fail

[7floor]

Checklist

• I have updated to the latest available Frigate version.
• I have cleared the cache of my browser.
• I have tried a different browser to see if it is related to my browser.
• I have tried reproducing the issue in incognito mode to rule out problems with any third party extensions or plugins I have installed.
• I have asked the AI at https://docs.frigate.video about my issue.

Describe the problem you are having

Frigate 0.16.4 installed as an HomeAssistant addon (full access)

My HA URL in local network is http://192.168.2.3:8123/

When using Frigate UI through Home Assistant ingress, i.e. at http://192.168.2.3:8123/ccab4aaf_frigate-fa everything seem to work well, but when I look at browser's dev console, it shows errors as follows

Fiddling with URLs, I have found that I can call that API endpoint using Ingress feature as follows:
http://192.168.2.3:8123/api/hassio_ingress/CgdSfsu6HiXa--ZHkqQN8nqTJC7GFTmeM5QxVe1xlF4/api/go2rtc/streams/outdoor
This way, the JSON with stream properties is perfectly returned to me.

Another my observation, is that other API endpoints are correctly called using ingress, e.g. when I open logs, in dev console network tab I see correct http://192.168.2.3:8123/api/hassio_ingress/CgdSfsu6HiXa--ZHkqQN8nqTJC7GFTmeM5QxVe1xlF4/api/logs/frigate?start=-100

I really not sure what feature is broken due to inability to get stream info, but that is definitely not normal I guess.

Steps to reproduce

1. Make sure you're using Frigate as a Home Assistant Addon
2. Open dev console in browser
3. Open Frigate UI from inside Home Assistant
4. Watch errors in console and requests with HTTP 404 in network tab

Version

0.16.4-4131252

In which browser(s) are you experiencing the issue with?

No response

Frigate config file

Will provide upon request, it seems irrelevant for now

docker-compose file or Docker CLI command

irrelevant

Relevant Frigate log output

none relevant

Relevant go2rtc log output

none relevant

Operating system

Home Assistant OS

Install method

Home Assistant Add-on

Network connection

Wired

Camera make and model

irrelevant

Screenshots of the Frigate UI's System metrics pages

irrelevant

Any other information that may be helpful

No response

[inkeep-ai-assistant[bot]]

Based on your description, this appears to be a client-side routing issue where some API requests from the Frigate UI are not correctly prepending the ingress path when running through Home Assistant's ingress proxy.

When using the Home Assistant Add-on, the URL should be one of the following depending on which variant you are using(1):

Add-on Variant	URL
Frigate	http://ccab4aaf-frigate:5000
Frigate (Full Access)	http://ccab4aaf-frigate-fa:5000

The integration is designed to work through ingress, and you've confirmed that most API endpoints work correctly (like /api/logs/frigate), but the go2rtc streams endpoint is failing to use the ingress path(1).

This is likely a bug in the Frigate UI's client-side code where certain API requests aren't respecting the base path configuration. You've already discovered the workaround - the endpoint works when you manually construct the full ingress URL:

http://192.168.2.3:8123/api/hassio_ingress/CgdSfsu6HiXa--ZHkqQN8nqTJC7GFTmeM5QxVe1xlF4/api/go2rtc/streams/outdoor

Since this appears to be a UI bug specific to certain API endpoints not using the ingress path correctly, I recommend:

1. Filing this as a bug report on the Frigate GitHub repository with the specific details about which endpoints fail
2. As a temporary workaround, you could access Frigate directly on port 5000 if your network allows it (though this bypasses Home Assistant's authentication)

The issue doesn't appear to be with your configuration, but rather with how the Frigate UI constructs certain API request URLs when running under an ingress path.

📚 Sources:

1. Home Assistant Integration

---

Have another question? Just tag @inkeep.

[hawkeye217]

Thanks, go2rtc stream metadata fetching has been refactored for Frigate 0.17, so this is likely fixed by #21072, currently available in the Frigate beta add-on.

If you still have issues with 0.17 RC1, let us know.

[7floor]

Thanks for answer.
I prefer not to play with beta and RC versions because I only have my live/production setup.
Said that, I will wait for 0.17 release and re-check there, and let you know of course if something like this will still be occuring.
Also, since 0.17 is expected to be released soon, maybe it is not worth efforts to fix the issue in current release.

[hawkeye217]

Right, we have no plans to change the current release.

I'll close this for now. If the issue still occurs on 0.17, feel free to open another report.