#camera_proxy 401 errors accessing Frigate

1 messages · Page 1 of 1 (latest)

shy falcon
#

Hey all, I'm trying to integrate a HA with Frigate and for certain types of requests I'm seeing that HA is recieveing a 401 from Frigate. I'm guessing it's just not sending credentials?
I think that the Frigate integration is configured with the username and password correctly since it's able to pull cameras and create entities, but some of the streams don't work, and I see those logs when they don't work

My setup:
HA Docker
Frigate Docker
Frigate Custom Integration
Advanced Camera Card
HA Accessed over HTTPS

The type of logs I can see in HA are:

Reverse proxy error for /api/frigate/frigate/jsmpeg/<SNIP>?authSig=<SNIP>: 401, message='Invalid response status', url='http://<SNIP>:8971/live/jsmpeg/<SNIP>'

Reverse proxy error for /api/frigate/frigate/mse/api/ws?src=pupcam&authSig=<SNIP>: 401, message='Invalid response status', url='http://<SNIP>:8971/live/mse/api/ws?src=<SNIP>'

Any advice as to how to debug this?

shy falcon
#

Actually, a more simple reproduction of the issue; is HA requesting latest.jpg from Frigate, which results in a 401

frigate-1 <SNIP> "GET /api/<SNIP>/latest.jpg HTTP/1.1" 401 179 "-" "HomeAssistant/2025.4.4 aiohttp/3.11.16 Python/3.13" "-"
In HA the response is a 200 from HA, with an empty body

quick heart
#

Hi there, what does the Frigate log say?

shy falcon
# quick heart Hi there, what does the Frigate log say?

There's this one:

frigate-1 <SNIP> "GET /api/<SNIP>/latest.jpg HTTP/1.1" 401 179 "-" "HomeAssistant/2025.4.4 aiohttp/3.11.16 Python/3.13" "-"

Showing a request coming from HA, and Frigate giving a 401 in response, but nothign further

quick heart
#

How are you fetching Frigate api in HA integration? By direct ip:port or reverse proxy (thru NPM or similar)

shy falcon
quick heart
#

Hi, sorry for the delay. Are you able to see the camera streams if you access Frigate NVR via web directly? Is there any stream-level authentication required?

shy falcon