Incandescent with rage tonight, because I started fiddling rather than leaving it alone and thus I broke Frigate again, I tried a dozen things (rebooted TN, downgraded Frigate to an earlier app version, upgraded back to current, removed it entirely, reinstalled it).
My fury was second to none (because I don’t seem to learn) and then I remembered your option to get rid of the backup …problem solved and back to normal!
I wonder if I can somehow password protect the Frigate app on TrueNAS UI, then give the pw to my wife and then I can actually enjoy using Frigate rather than fixing it …
Hi all! After so much frustration, i stubled on this page. I tried deleting the bakup file, but didn’t work for me. I even tried using a custom docker yaml, but I had the same issue. My setup was as following: pool/appdataset/frigate (where frigate was a dataset), then i went to the shell and created the “config” folder. Tried deleting the config folder and create it again, I tried deleting the dataset.
Long story short: I went in shell and SUDO mkdir config. And now it’s working! Please let me know if this is helpful. clearly there’s an issue with this app, as it’s the only one I’ve ever had issues like this.
Thanks for the suggestion. I created a new config directory with sudo, but it did not work. The app did “deploy”, but would not even load the UI, and it only deployed once. After stopping and restarting, it threw the same error. Any other ideas? Have you tried stopping and restarting Frigate to make sure it still works? There are a number of things that will get it to upgrade to the latest version, but will subsequently only deploy once.
Yes, as of right now Frigate starts just fine. Another thing that I did change, but I’m not sure it helped: when i recreated the frigate dataset (pool/apps/frigate/config), I changed the dataset preset permissions from SMB to Generic. Can you also test that?
There does appear to be legitimate bug(s) here, but I’ve come up with a workaround that may work for others.
At least part of the issue seems to stem from the SMB dataset preset. I want to have SMB access to this dataset so I can manage the files directly (e.g. backups), which I why I was using SMB preset.
The following workarounds worked for me, although we’ll see how this survives future updates.
If you are starting from scratch:
Create a new dataset with the Generic dataset preset
Create the config and media folders in the shell
Install Frigate
This should work, but you can optionally make an SMB share
If you already have Frigate installed and want to preserve your existing dataset:
Shut down Frigate
Back up config.yml and Frigate.db
Edit the file system permissions for the dataset and strip the ACL, apply recursively, and save
Upgrade to the latest version - currently v0.15.1_1.1.21 (if you’re upgrading from v0.14.X, note that Frigate may modify your config to address certain breaking changes - e.g. they changed some things with recording)
This should work, but you can optionally make an SMB share or, if you already had one, edit the dataset file system permissions to allow access to your SMB users/groups
Hopefully someone fixes this, but if not, hopefully these workarounds help someone.
