Running TrueNAS Scale 25.04 fresh install, Frigate installs but not able to create first admin login in formation in the log file. Not able to use code to regenerate the admin password, not able to access via port 5000. Seems to be broken even in 25.10 version as well. Lots of web traffic about this issue as well as some others that act the same as Frigate.
Does anyone have had success with overcoming this issue?
Overcoming, no. I got the thing to work after a lot of trial and error, of that mostly error. The parser is picky, the UI to edit same pretty abysmal.
That said, I did get it to work for a bit. I was super happy until I discovered dropped frames, etc. Those are likely due to the very slow cores in my D1537 CPU.
Then Frigate decided that my previously working config file should now be considered persona non grata. I got the hint and moved on.
To me, Frigate was worse than ZoneFinder under CORE. I also concluded that if UPS operation was one of my goals that powering the whole NAS for a day or two along with the cameras would be very expensive to implement. There are more power efficient ways to do it.
I have been having mixed results - sometimes it does populate a password (really long string of alpha) and then it does not. Also - inconsistent setup from fresh installs, no previous data retained in testing. It will sometimes randomly not create the non-auth log in, in that case it will also sometimes not provide initial password. This results in complete removal and reinstall of the app to remedy. This holds true on both .04 and .10 versions of TrueNAS Scale. I finally got it to work dependently and then lost live streams for all my attached cameras. Again - back to having to delete the app and re-install it. Now I have cameras loaded, they stream to computers on my network, but the SSL obtained from Lets Encrypt has failed to be used from within Frigate no matter what I have tried. Nginx settings are showing my destination as 192.168.68.103 attached to port 30193 right now, with other attempts using ports listed in the online documentation. The certificate is good - points to my domain name, traffic is being passed to Nginx on secure channels. States both the proxy host and the ssl are onilne and in use. SSL scheme set to https options for websockets support and block common exploits are enabled. Looking at the certificate - it states it is attached to my domain name, is in use as indicated, and is good until June 4th. No matter what I have tried the SSL is not working for Frigate.
Any ideas will be gladly appreciated.
