[Support]: Is it possible to access Frigate Docker Container instance via Home Assistant via a proxy (not an addon)

Describe the problem you are having

Hello,

I redone my whole setup over the last couple of days so I can run the latest Frigate Beta, I’m now using Docker containers for both Home Assistant and Frigate NVR on the same host. A painful process I don’t wish to repeat ha…

Something I didn’t realise was that the Frigate Proxy appears to be only available as an addon for Home Assistant supervised or HAOS. Are people running this as a Docker container somehow?

This means currently we cannot access Frigate outside of our home network, unless I’m doing something wrong?

As this is the recommended install method, how are people accessing it from outside their house?

Or is everyone just using a VPN, I’d rather not…

Thanks,

Laurence

Version

0.11.0-D2C3CDC

Frigate config file

N/A

Relevant log output

N/A

FFprobe output from your camera

N/A

Frigate stats

No response

Operating system

Debian

Install method

Docker Compose

Coral version

CPU (no coral)

Network connection

Wired

Camera make and model

N/A for this

Any other information that may be helpful

No response

[NickM-27]

I was assuming that this HA proxy addon then allows it to work outside of your home network, externally, provided of course you have setup secure HA access externally

I believe it would work that way, but that’s because supervised HA itself allows this to be the case.

The thing is (at least as far as I know) the core of the logic you are looking for belongs to HA itself (services running in supervisor available through nabu casa) which the container doesn’t support, would need to be added by HA team.

[blakeblackshear]

I run frigate on a dedicated subdomain behind a reverse proxy with Google authentication. I do the same for esphome, home assistant, and a bunch of other containers as well.