Frigate was working fine. I did an update and it stopped communicating with home assistant. I used host networking.
On further testing and looking at logs the issue is it stopped responding on IPv6 and is only responding on IPv4.
My ollama and other apps still respond on IPv6 just fine.
Using ss -tunlpe It seems the frigate process is only listening on 0.0.0.0 and not :: as it was before, is there any easy way to fix this vs having to just write my own yaml?
on further investigation its likely the previous versions were not llistening on IPv6 and i got lucky that dns resolution was giving out IPv4 addresses first, or maybe there wasn’t a truenas IPv6 registration
i can edit the listen.conf inside the containert to add the listen [::]:5000; and listen [::]:8971 ssl; drectives and issue ngininx -t and nginx -s reload and then i can access frigate via IPv6 from the browser
however this still seems to cause issues with home assistant frigate add-on to https://truenas1.myinternaldomaincom:8971/api/stats edit
it would still be good if there was a way to have the app listen on both IPv6 and IPv4 by default IMO (or have a way to configure it)
(i will contine to investiage the home assistant issues in their community) turned out the home assistant issue was actually a network switch issue
tl;dr whats the best way to modify the listen.conf given it looks like this file is managed by the apps orchestration engine - i note it binds the right LE truenas cert as an example… so i don’t want to overide the file with my own…
