blu commented on issue starred/frigate-blakeblackshear-2#4673 2026-02-06 13:03:54 -08:00
[Support]: My frigate container instance cannot be reached

@obogle1986 commented on GitHub (Feb 8, 2024):

Just do a find -name command. It should be on the root of /opt if not in your frigate directory

blu commented on issue starred/frigate-blakeblackshear-2#4673 2026-02-06 13:03:53 -08:00
[Support]: My frigate container instance cannot be reached

@NickM-27 commented on GitHub (Jan 31, 2024):

make sure that docker is fully downed and upped not just restarted

blu commented on issue starred/frigate-blakeblackshear-2#4673 2026-02-06 13:03:53 -08:00
[Support]: My frigate container instance cannot be reached

@obogle1986 commented on GitHub (Jan 31, 2024):

Ah. That did the trick. Thank you.

blu commented on issue starred/frigate-blakeblackshear-2#4673 2026-02-06 13:03:53 -08:00
[Support]: My frigate container instance cannot be reached

@Tiotbrev commented on GitHub (Feb 8, 2024):

good evening, can you explain the methodology more precisely please, thank you

blu commented on issue starred/frigate-blakeblackshear-2#4673 2026-02-06 13:03:53 -08:00
[Support]: My frigate container instance cannot be reached

@obogle1986 commented on GitHub (Feb 8, 2024):

@Tiotbrev within my docker-compose file, I had :ro (read-only) at the end of my config reference as per the documentation I was following. You can…

blu commented on issue starred/frigate-blakeblackshear-2#4673 2026-02-06 13:03:53 -08:00
[Support]: My frigate container instance cannot be reached

@Tiotbrev commented on GitHub (Feb 8, 2024):

@obogle1986 Thank you very much, but my installation is a little old and I'm completely lost I need to modify the configuration file? can you…

blu commented on issue starred/frigate-blakeblackshear-2#4673 2026-02-06 13:03:53 -08:00
[Support]: My frigate container instance cannot be reached

@obogle1986 commented on GitHub (Feb 8, 2024):

@Tiotbrev not the frigate config file but the docker-compose.yaml file. I have mine here: https://github.com/blakeblackshear/frigate/issues/9539#issu…

blu commented on issue starred/frigate-blakeblackshear-2#4673 2026-02-06 13:03:53 -08:00
[Support]: My frigate container instance cannot be reached

@Tiotbrev commented on GitHub (Feb 8, 2024):

Thanks, I'll look but I can't even find the file anymore. complicated weekend ahead ;-)

blu commented on issue starred/frigate-blakeblackshear-2#4675 2026-02-06 13:03:52 -08:00
[Support]: Multiple objects at the same time are being saved as individual event clips

@NickM-27 commented on GitHub (Jan 31, 2024):

this behavior has not changed in 0.13. There is a job in frigate that runs periodically to clean up duplicate events like that, just need to be patient

blu commented on issue starred/frigate-blakeblackshear-2#4674 2026-02-06 13:03:52 -08:00
[Support]: Stuck starting go2rtc healthcheck since v0.13

@NickM-27 commented on GitHub (Jan 31, 2024):

it is not stuck, it is generating the TRT model

you have to…

blu commented on issue starred/frigate-blakeblackshear-2#4673 2026-02-06 13:03:52 -08:00
[Support]: My frigate container instance cannot be reached

@obogle1986 commented on GitHub (Jan 31, 2024):

Is this the config folder being referred to?

blu commented on issue starred/frigate-blakeblackshear-2#4675 2026-02-06 13:03:52 -08:00
[Support]: Multiple objects at the same time are being saved as individual event clips

@supermarkert commented on GitHub (Jan 31, 2024):

Got it; Thanks! Relatively new to Frigate, and now playing with 0.13, so I was monitoring it like a hawk during testing... 0.13 gives me much…

blu commented on issue starred/frigate-blakeblackshear-2#4674 2026-02-06 13:03:52 -08:00
[Support]: Stuck starting go2rtc healthcheck since v0.13

@BurningTheSky commented on GitHub (Jan 31, 2024):

Ah ok, why is it generating those for the coral? I thought it used TRT for the nvidia gpus?

blu commented on issue starred/frigate-blakeblackshear-2#4675 2026-02-06 13:03:52 -08:00
[Support]: Multiple objects at the same time are being saved as individual event clips

@NickM-27 commented on GitHub (Jan 31, 2024):

Yep, feel free to create a new issue if something else comes up

blu commented on issue starred/frigate-blakeblackshear-2#4673 2026-02-06 13:03:52 -08:00
[Support]: My frigate container instance cannot be reached

@NickM-27 commented on GitHub (Jan 31, 2024):

yes

blu commented on issue starred/frigate-blakeblackshear-2#4674 2026-02-06 13:03:52 -08:00
[Support]: Stuck starting go2rtc healthcheck since v0.13

@NickM-27 commented on GitHub (Jan 31, 2024):

probably because you are running the tensorrt variant of the docker image and the env variables are set by default

blu commented on issue starred/frigate-blakeblackshear-2#4673 2026-02-06 13:03:52 -08:00
[Support]: My frigate container instance cannot be reached

@obogle1986 commented on GitHub (Jan 31, 2024):

The above screenshot shows that it isn't read-only though. What should the permission be? Should I just set it to 777?

blu commented on issue starred/frigate-blakeblackshear-2#4673 2026-02-06 13:03:52 -08:00
[Support]: My frigate container instance cannot be reached

@NickM-27 commented on GitHub (Jan 31, 2024):

it is read only and the logs show this as well [Errno 30] Read-only file system: '/config/model_cache'

you need to update your docker compose…

blu commented on issue starred/frigate-blakeblackshear-2#4674 2026-02-06 13:03:52 -08:00
[Support]: Stuck starting go2rtc healthcheck since v0.13

@BurningTheSky commented on GitHub (Jan 31, 2024):

That's it! Removed all that and good to go. Thanks

blu commented on issue starred/frigate-blakeblackshear-2#4673 2026-02-06 13:03:52 -08:00
[Support]: My frigate container instance cannot be reached

@obogle1986 commented on GitHub (Jan 31, 2024):

I followed the steps and removed :ro and I am still getting the same thing. I went as far as to change the permissions to the config director to…