Running the Frigate app from the TrueNAS SCALE catalog. Each time I edit config.yml in the UI and hit Save & Restart, the app moves to Deploying… and never finishes. Logs show the go2rtc container cycling messages like go2rtc: stopping, then nothing — Frigate never comes back online until I manually Stop and Start the app.
Anyone else seeing go2rtc fail to restart automatically after a config change; or know a fix so I don’t need the extra stop/start step? Thanks!
For further details, the logs show the following:
2025-07-06 11:44:35.409768126 [INFO] Service Frigate exited with code 0 (by signal 0)
s6-rc: info: service frigate successfully stopped
s6-rc: info: service go2rtc: stopping
s6-rc: info: service frigate-log: stopping
2025-07-06 11:44:35.411959834 exit with signal: terminated
2025-07-06 11:44:35.414664490 [INFO] The go2rtc service exited with code 0 (by signal 0)
s6-rc: info: service go2rtc successfully stopped
s6-rc: info: service go2rtc-log: stopping
Nothing happens after that until I manually stop and start the container.
You have rightly identified this problem, which has persisted for ages, but there is no fix yet.
My approach is to edit the config, save it and then go into the TN app menu and stop/start from there.
Out of interest, I have confirmed that the app simply runs a docker-compose yaml so I installed the ix-dockge app, and ran the docker-compose yaml in it and found that it ran perfectly well. I mention it in case you wanted to experiment.
(I didn’t test to see if the yaml reload from within the frigate UI worked or not).
/mnt/.ix-apps/app_configs/<app>/<version>/templates/rendered/docker-compose.yaml
Hey @E_B, thanks for your response. I’d be open to switching from the community package to a custom app (similar to what I did with lldap), but before making the change, I’d like to confirm whether it would actually resolve the issue. If you have a moment, could you test a Save & Restart from the Config Editor in your YAML-based Frigate deployment and let me know the outcome?
I’m not using ix-dockge at the moment; if I reinstall it I shall extract the ix-frigate docker compose and give it a try.
In the mean time, this might be useful to keep an eye on:
Yes, that was my post you linked to. I also posted some details on the container setup I extracted to this related issue:
Hopefully you can share feedback on if you are able to restart Frigate when using a docker-compose yaml file.
I tried it in ix-dockge for you: the reload from the yaml editor window doesn’t work.
I see this:
but when I left it to complete the countdown I get
and in ix-dockge I see
which is how it remains.
I stopped it manually, and shut down ix-dockge and I’m now back on ix-frigate (the official app running in TrueNAS).
Would you be able to share your YAML file? I’d like to pass it along to the original package authors to help with their diagnosis.
You can simply extract your own from the path I showed.
I guess more to the point - the original documentation has a docker compose configuration they recommend. I’m curious if you’ve tried using these exact settings with your TrueNAS and experience the same restart issue.
I’m not able to try at the moment; could you install dockge and give it a go?
When I try these experiments, I have to stop and unmount my Frigate instance and I’m always worried I’ll make a mistake/it won’t start again.
It would certainly be good to know the answer to this restarting problem.
