March 28Mar 28 Author 15 hours ago, John Graham said:Hello First I LOVE Frigate and if i cant fix this i ok with it. I hope this is a good place to ask .. been running frigate for some time with no problems all the ways up to v17 now and i seem to be having a problem. the screen as you are watching live only shows 1 ever 2 or 3 sec. nothing has changed here that i know of. Frigate is running on a Server as i UN-Raid server :Supermicro X9QR7-TF+/X9QRi-F+ , Version 123456789American Megatrends Inc, Version 3.0aBIOS dated: Thu 3 Apr 2014 12:00 AMProcessors 4 of Intel® Xeon® CPU E5-4650 v2 @ 2.40GHzMemory: 128 GiB DDR3 Multi-bit ECCno Video Card but i have a Coral TPU PCI based TPU installed: 1detectors:coral: type: edgetpu device: pci:0 classify: truethe only thing that is running is MQTT server and Plex (No one is using plex but me and it make no differences that i can see )I only have 3 cameras. I don't under understand why it is so slow all play back is at full speed (even with Audio) the cameras are all POE. They are all on there own wired network with nothing but cameras and Un-Raid 2nd port on the server set to the same address group Here is the Config From Frigate:thanks for any help .. I am hoping some one see the problem i cantFrigat_config.txtIs this happening all the time?"Frigate employs "smart streaming" where camera images update once per minute when no detectable activity is occurring to conserve bandwidth and resources. As soon as any motion or active objects are detected, cameras seamlessly switch to a live stream."https://docs.frigate.video/configuration/liveCan you check the camera FPS under /system#cameras if there is any issue also. Edited March 28Mar 28 by yayitazale
May 13May 13 I ran into an issue where the Docker container didn't want to start any more after the upgrade to Unraid 7.3.0, with the following error:Error response from daemon: error while creating mount source path '/etc/localtime': mkdir /etc/localtime: file existsIn the end, it turned out that the /etc/localtime symlink on my Unraid instance was pointing towards a file in /usr/share/zoneinfo/ that doesn't exist (any more?). Changing the timezone of the Unraid instance in the settings fixed that reference, and as such fixed the docker bind mount. I hope it helps someone else, so they don't lose half an hour trying to figure this out as well.Either way, this doesn't seem like a bug with the container. I'm not sure if it is fully related to 7.3.0, but that's what things seem to point to for me.
May 15May 15 Hello there,I am currently setting up a frigate instance and now i get this error here:Unable to poll intel GPU stats: Failed to initialize PMU! (Operation not permitted)Is that something serious? I run the app on a intel cpu with that acceleration feature available. I do have a coral usb stick attached for frigates use. Idea was to speed up the ffmpeg a bit with the igpu and detect fast with coral. Edited May 15May 15 by masterdot
May 17May 17 Author On 5/16/2026 at 12:50 AM, masterdot said:Hello there,I am currently setting up a frigate instance and now i get this error here:Unable to poll intel GPU stats: Failed to initialize PMU! (Operation not permitted)Is that something serious? I run the app on a intel cpu with that acceleration feature available.I do have a coral usb stick attached for frigates use. Idea was to speed up the ffmpeg a bit with the igpu and detect fast with coral.No, that's normal; unless you run the container in privileged mode (which is not recommended for security reasons), it won't be able to retrieve the CPU/iGPU statistics, which is why you're getting that error. Edited May 17May 17 by yayitazale
May 18May 18 I'm setting up a new install on Unraid and this is baffling that I can't figure out what the default login is - nor can I see where it's documented anywhere. I would think that first-time startups should present a username and password setup dialog, but I'm not seeing that - it immediately takes me to the login page and there's no "forgot password" or other option. Am I just overlooking something so basic and simple?Yes, I tried both the default config.yaml as well as a templated one that I can fill in my camera details once I'm able to login. Even after restarting, I'm not seeing a "setup login" screen. Edited May 18May 18 by yoleska
May 18May 18 I also have been looking at the files on disk and this succeeded. Took me a couple extra steps to figure out the hashing function. Password is temporary, so I don't mind posting it. docker exec -it frigate python3 -c " import sqlite3, hashlib, secrets, base64 password = 'FrigateAdmin1!' salt = secrets.token_hex(16) pw_hash = hashlib.pbkdf2_hmac('sha256', password.encode('utf-8'), salt.encode('utf-8'), 600000) b64_hash = base64.b64encode(pw_hash).decode('ascii').strip() hashed = 'pbkdf2_sha256\$600000\$' + salt + '\$' + b64_hash conn = sqlite3.connect('/config/frigate.db') cur = conn.cursor() cur.execute('UPDATE user SET password_hash = ? WHERE username = ?', (hashed, 'admin')) conn.commit() print('Password updated, rows affected:', cur.rowcount) print('Hash stored:', hashed[:40], '...') conn.close() "
May 18May 18 Author 2 hours ago, yoleska said:I'm setting up a new install on Unraid and this is baffling that I can't figure out what the default login is - nor can I see where it's documented anywhere. I would think that first-time startups should present a username and password setup dialog, but I'm not seeing that - it immediately takes me to the login page and there's no "forgot password" or other option. Am I just overlooking something so basic and simple?Yes, I tried both the default config.yaml as well as a templated one that I can fill in my camera details once I'm able to login. Even after restarting, I'm not seeing a "setup login" screen.You must read the docs before posting: https://docs.frigate.video/configuration/authentication#onboarding
May 18May 18 9 hours ago, yayitazale said:You must read the docs before posting: https://docs.frigate.video/configuration/authentication#onboardingYup, sorry I should have mentioned that. I read that and tried a few times and that didn't change anything. It's still prompting me to login, not reset. Running the python script was the last resort after trying the steps in the onboarding section. I also tried this: "On startup, an admin user and password are generated and printed in the logs." but the the logs might be scrolling too fast by the time I can tail the docker logs and there's no log messages about passwords. I tried looking for logs on disk, but couldn't find them. Also tried searching the doc that you linked above and didn't see where they were stored on disk. Looked in /dev/shm/logs/ in the container, but didn't see anything about password.
May 19May 19 Author 13 hours ago, yoleska said:Yup, sorry I should have mentioned that. I read that and tried a few times and that didn't change anything. It's still prompting me to login, not reset.Running the python script was the last resort after trying the steps in the onboarding section.I also tried this: "On startup, an admin user and password are generated and printed in the logs." but the the logs might be scrolling too fast by the time I can tail the docker logs and there's no log messages about passwords. I tried looking for logs on disk, but couldn't find them. Also tried searching the doc that you linked above and didn't see where they were stored on disk. Looked in /dev/shm/logs/ in the container, but didn't see anything about password.You should try a minimal setup, without any cameras configured or anything like that... just as described in the documentation. https://docs.frigate.video/guides/getting_started#configuring-frigate
May 19May 19 I figured it out. Frigate was setting the log files as root:root and when I was trying to write to them through an NFS share, they weren't getting written. I finally was able to use a simple config with that admin reset arg, and then I looked at the docker logs outside Unraid and saw the password. Sorry for the noise.
June 6Jun 6 hi igetdocker run -d --name='frigate' --net='bridge' --pids-limit 2048 -e TZ="Europe/Budapest" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Kronos" -e HOST_CONTAINERNAME="frigate" -e 'FRIGATE_RTSP_PASSWORD'='mypassword' -e 'PLUS_API_KEY'='' -e 'LIBVA_DRIVER_NAME'='radeonsi' -e 'NVIDIA_VISIBLE_DEVICES'='' -e 'NVIDIA_DRIVER_CAPABILITIES'='' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8971]' -l net.unraid.docker.icon='' -p '8971:8971/tcp' -p '8554:8554/tcp' -p '5000:5000/tcp' -p '8555:8555/tcp' -p '8555:8555/udp' -v '/mnt/user/appdata/frigate':'/config':'rw' -v '/mnt/user/Media/frigate':'/media/frigate':'rw' -v '/etc/localtime':'/etc/localtime':'ro' --device='' --device='/dev/dri/renderD128' --shm-size=256m --mount type=tmpfs,target=/tmp/cache,tmpfs-size=1000000000 --restart unless-stopped 'ghcr.io/blakeblackshear/frigate:stable' docker: bad format for path: Run 'docker run --help' for more informationThe command failed.i placed a basic config.yml in /usr/appdata/frigatethis my template settings https://ibb.co/QjrvkCCTanyone can help me point in a direction?
June 6Jun 6 3 hours ago, Deych said:hi igetdocker run -d --name='frigate' --net='bridge' --pids-limit 2048 -e TZ="Europe/Budapest" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Kronos" -e HOST_CONTAINERNAME="frigate" -e 'FRIGATE_RTSP_PASSWORD'='mypassword' -e 'PLUS_API_KEY'='' -e 'LIBVA_DRIVER_NAME'='radeonsi' -e 'NVIDIA_VISIBLE_DEVICES'='' -e 'NVIDIA_DRIVER_CAPABILITIES'='' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8971]' -l net.unraid.docker.icon='' -p '8971:8971/tcp' -p '8554:8554/tcp' -p '5000:5000/tcp' -p '8555:8555/tcp' -p '8555:8555/udp' -v '/mnt/user/appdata/frigate':'/config':'rw' -v '/mnt/user/Media/frigate':'/media/frigate':'rw' -v '/etc/localtime':'/etc/localtime':'ro' --device='' --device='/dev/dri/renderD128' --shm-size=256m --mount type=tmpfs,target=/tmp/cache,tmpfs-size=1000000000 --restart unless-stopped 'ghcr.io/blakeblackshear/frigate:stable' docker: bad format for path: Run 'docker run --help' for more informationThe command failed.i placed a basic config.yml in /usr/appdata/frigatethis my template settings https://ibb.co/QjrvkCCTanyone can help me point in a direction?nevermind found the issue, gpu was vfio bound
June 28Jun 28 I have a general question that leads to more questions.I have started playing around with Frigate and have the Nvidia tensorRT branch.I have a 1080TI that I have in my unraid system that I generally use for encoding and what not so I am using it for decoding and encoding in frigate.I have the --runtime=nvidia paramater added to the extra parameters section and have the and have the GPU id in the NVIDIA_VISIBLE_DEVICES section with compute,utility,video in the capabilities section .Could I use the 1080TI for detecting as well or is it not powerful enough and should go down the path of getting a Coral TPU instead?I havent really played around much with frigate before so have very limited knowledge on what I should put in the config file and what additional variables I would need to add to the container setup.I have looked looked at the documentation in regards ONNX which I believe I would need to use if I wanted to use my GPU but same in way over my head from there.Thanks in advance.
June 29Jun 29 Author On 6/28/2026 at 8:34 AM, JWMutant said:I have a general question that leads to more questions.I have started playing around with Frigate and have the Nvidia tensorRT branch.I have a 1080TI that I have in my unraid system that I generally use for encoding and what not so I am using it for decoding and encoding in frigate.I have the --runtime=nvidia paramater added to the extra parameters section and have the and have the GPU id in the NVIDIA_VISIBLE_DEVICES section with compute,utility,video in the capabilities section .Could I use the 1080TI for detecting as well or is it not powerful enough and should go down the path of getting a Coral TPU instead?I havent really played around much with frigate before so have very limited knowledge on what I should put in the config file and what additional variables I would need to add to the container setup.I have looked looked at the documentation in regards ONNX which I believe I would need to use if I wanted to use my GPU but same in way over my head from there.Thanks in advance.Yes, the GTX 1080 Ti is perfectly suitable because, thanks to its 11 GB of VRAM, it has more than enough memory to run the YOLOv9 models and handle multiple video streams simultaneously and it’s more than capable of keeping model inference times low.In the first step of installing the instance, you must select the NVIDIA branch:Next, as you mentioned, you need to add “--runtime=nvidia” to the additional parameters and configure the NVIDIA entries in the configuration form. As for models, I recommend using YOLO V9:From your Unraid machine's console (not the container one), navigate to the folder where you want to save the model, preferably in the default path (model_cache):cd /mnt/user/appdata/frigate/model_cache/Run the command listed in the documentation at https://docs.frigate.video/configuration/object_detectors/#yolov9-for-other-detectors; if you have many cameras—more than 6, for example—start with a “tiny” (T) size and IMG_SIZE=320 to ensure acceptable inference times. Otherwise, with fewer than 6 cameras, you can try IMG_SIZE=640 and S or M sizes, but keep in mind that the larger the model, the longer the inference time and the higher the power consumption will be.Verify that your ONNX file was created correctly in the specified folderConfigure detection with the ONNX detector pointing to your ONNX file (if you placed it in model_cache, you don’t need to change anything) https://docs.frigate.video/configuration/object_detectors#yolo-v3-v4-v7-v9-2Restart Frigate and check the logs to see if the model has loaded correctly.In addition, if you're also going to perform hardware-accelerated video decoding using the NVIDIA GPU itself, you should use the NVIDIA decoder preset: https://docs.frigate.video/configuration/hardware_acceleration_video#setup-decoder Edited June 29Jun 29 by yayitazale
June 29Jun 29 Thanks very much for the info, it really helped.Just out of interest has there been an up in the last 20 odd hours that may have broken something?Everything was working fine yesterday. Today I thought I would start from scratch like I have been doing over the past 3 days, but today Im getting the following.2026-06-29 19:39:20.070663773 127.0.0.1 - - [29/Jun/2026:19:39:20 +0930] "" 400 0 "-" "-" "-" request_time="0.000" upstream_response_time="-"2026-06-29 19:39:43.535285958 192.168.178.20 - - [29/Jun/2026:19:39:43 +0930] "GET / HTTP/1.1" 400 657 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/149.0.0.0 Safari/537.36" "-" request_time="0.000" upstream_response_time="-"2026-06-29 19:39:43.918769616 192.168.178.20 - - [29/Jun/2026:19:39:43 +0930] "GET /favicon.ico HTTP/1.1" 400 657 "http://192.168.178.22:8971/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/149.0.0.0 Safari/537.36" "-" request_time="0.000" upstream_response_time="-"2026-06-29 19:40:20.167602798 127.0.0.1 - - [29/Jun/2026:19:40:20 +0930] "" 400 0 "-" "-" "-" request_time="0.000" upstream_response_time="-"To get past that page I end up needing to place my cursor at the start of the address which is simply my ip:8971 and press enter. This then gives me the following page. Edited June 29Jun 29 by JWMutant
June 29Jun 29 Author 18 minutes ago, JWMutant said:Thanks very much for the info, it really helped.Just out of interest has there been an up in the last 20 odd hours that may have broken something?Everything was working fine yesterday. Today I thought I would start from scratch like I have been doing over the past 3 days, but today Im getting the following.2026-06-29 19:39:20.070663773 127.0.0.1 - - [29/Jun/2026:19:39:20 +0930] "" 400 0 "-" "-" "-" request_time="0.000" upstream_response_time="-"2026-06-29 19:39:43.535285958 192.168.178.20 - - [29/Jun/2026:19:39:43 +0930] "GET / HTTP/1.1" 400 657 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/149.0.0.0 Safari/537.36" "-" request_time="0.000" upstream_response_time="-"2026-06-29 19:39:43.918769616 192.168.178.20 - - [29/Jun/2026:19:39:43 +0930] "GET /favicon.ico HTTP/1.1" 400 657 "http://192.168.178.22:8971/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/149.0.0.0 Safari/537.36" "-" request_time="0.000" upstream_response_time="-"2026-06-29 19:40:20.167602798 127.0.0.1 - - [29/Jun/2026:19:40:20 +0930] "" 400 0 "-" "-" "-" request_time="0.000" upstream_response_time="-"To get past that page I end up needing to place my cursor at the start of the address which is simply my ip:8971 and press enter. This then gives me the following page.What do you see in the logs after restarting the container?
June 29Jun 29 s6-rc: info: service frigate successfully stoppeds6-rc: info: service go2rtc: stoppings6-rc: info: service frigate-log: stoppings6-rc: info: service frigate-log successfully stoppeds6-rc: info: service go2rtc successfully stoppeds6-rc: info: service prepare: stoppings6-rc: info: service go2rtc-log: stoppings6-rc: info: service prepare successfully stoppeds6-rc: info: service go2rtc-log successfully stoppeds6-rc: info: service log-prepare: stoppings6-rc: info: service s6rc-fdholder: stoppings6-rc: info: service log-prepare successfully stoppeds6-rc: info: service legacy-cont-init: stoppings6-rc: info: service s6rc-fdholder successfully stoppeds6-rc: info: service legacy-cont-init successfully stoppeds6-rc: info: service fix-attrs: stoppings6-rc: info: service fix-attrs successfully stoppeds6-rc: info: service s6rc-oneshot-runner: stoppings6-rc: info: service s6rc-oneshot-runner successfully stoppedERROR: driverInitFileInfo 578 result=11ERROR: init 664 result=11ERROR: init 250 result=11s6-rc: info: service s6rc-fdholder: startings6-rc: info: service s6rc-oneshot-runner: startings6-rc: info: service s6rc-oneshot-runner successfully starteds6-rc: info: service fix-attrs: startings6-rc: info: service s6rc-fdholder successfully starteds6-rc: info: service fix-attrs successfully starteds6-rc: info: service legacy-cont-init: startings6-rc: info: service legacy-cont-init successfully starteds6-rc: info: service prepare: startings6-rc: info: service log-prepare: startings6-rc: info: service log-prepare successfully starteds6-rc: info: service nginx-log: startings6-rc: info: service go2rtc-log: startings6-rc: info: service frigate-log: startings6-rc: info: service certsync-log: startings6-rc: info: service nginx-log successfully starteds6-rc: info: service go2rtc-log successfully starteds6-rc: info: service frigate-log successfully starteds6-rc: info: service certsync-log successfully starteds6-rc: info: service prepare successfully starteds6-rc: info: service go2rtc: startings6-rc: info: service go2rtc successfully starteds6-rc: info: service go2rtc-healthcheck: startings6-rc: info: service frigate: startings6-rc: info: service go2rtc-healthcheck successfully starteds6-rc: info: service frigate successfully starteds6-rc: info: service nginx: startings6-rc: info: service nginx successfully starteds6-rc: info: service certsync: startings6-rc: info: service certsync successfully starteds6-rc: info: service legacy-services: startings6-rc: info: service legacy-services successfully started2026-06-29 20:03:06.916540896 [2026-06-29 20:03:06] frigate.record.maintainer INFO : Exiting recording maintenance...2026-06-29 20:03:06.963346576 [2026-06-29 20:03:06] frigate.app INFO : Detection queue closed2026-06-29 20:03:07.464434414 [2026-06-29 20:03:07] frigate.app INFO : Detected frames queue closed2026-06-29 20:03:07.965491043 [2026-06-29 20:03:07] frigate.app INFO : Timeline queue closed2026-06-29 20:03:08.433575419 [2026-06-29 20:03:08] frigate.comms.ws INFO : Exiting websocket client...2026-06-29 20:03:08.924227189 [2026-06-29 20:03:08] peewee.sqliteq INFO : writer received shutdown request, exiting.2026-06-29 20:03:09.595304728 [INFO] Service Frigate exited with code 0 (by signal 0)2026-06-29 20:03:09.598518464 exit with signal: terminated2026-06-29 20:03:09.606208760 [INFO] The go2rtc service exited with code 0 (by signal 0)2026-06-29 20:03:13.831539599 [INFO] Starting NGINX...2026-06-29 20:03:13.918619515 [INFO] Preparing Frigate...2026-06-29 20:03:14.278419744 [INFO] Preparing new go2rtc config...2026-06-29 20:03:14.357538598 [INFO] Starting Frigate...2026-06-29 20:03:14.729370752 [INFO] Starting go2rtc...2026-06-29 20:03:15.135468780 20:03:15.132 INF go2rtc platform=linux/amd64 revision=df95ce3 version=1.9.102026-06-29 20:03:15.135474080 20:03:15.133 INF config path=/config/go2rtc_homekit.yml2026-06-29 20:03:15.135476464 20:03:15.133 INF [rtsp] listen addr=:85542026-06-29 20:03:15.135478809 20:03:15.134 INF [api] listen addr=:19842026-06-29 20:03:15.135481063 20:03:15.134 INF [webrtc] listen addr=:85552026-06-29 20:03:15.321143591 [INFO] Starting certsync...2026-06-29 20:03:15.896723589 127.0.0.1 - - [29/Jun/2026:20:03:15 +0930] "" 400 0 "-" "-" "-" request_time="0.000" upstream_response_time="-"2026-06-29 20:03:18.647144947 2026/06/29 20:03:18 [error] 288#288: *2 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "127.0.0.1:5000"2026-06-29 20:03:18.647170786 2026/06/29 20:03:18 [error] 288#288: *2 auth request unexpected status: 502 while sending to client, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", host: "127.0.0.1:5000"2026-06-29 20:03:18.984423628 [2026-06-29 20:03:18] frigate.util.config INFO : Checking if frigate config needs migration...2026-06-29 20:03:18.988220419 [2026-06-29 20:03:18] frigate.util.config INFO : frigate config does not need migration...2026-06-29 20:03:20.032561495 [2026-06-29 20:03:20] frigate.util.services INFO : Automatically detected nvidia hwaccel for video decoding2026-06-29 20:03:20.044798352 [2026-06-29 20:03:20] frigate.app INFO : Starting Frigate (0.17.2-3d4dd3a)2026-06-29 20:03:20.052265311 [2026-06-29 20:03:20] peewee_migrate.logs INFO : Starting migrations2026-06-29 20:03:20.053442950 [2026-06-29 20:03:20] peewee_migrate.logs INFO : There is nothing to migrate2026-06-29 20:03:20.077129070 [2026-06-29 20:03:20] frigate.app INFO : Recording process started: 7142026-06-29 20:03:20.089310712 [2026-06-29 20:03:20] frigate.app INFO : Review process started: 7152026-06-29 20:03:20.092242821 [2026-06-29 20:03:20] frigate.app INFO : go2rtc process pid: 1712026-06-29 20:03:20.107554089 [2026-06-29 20:03:20] frigate.app INFO : Embedding process started: 7292026-06-29 20:03:20.139370245 [2026-06-29 20:03:20] frigate.detectors WARNING : CPU detectors are not recommended and should only be used for testing or for trial purposes.2026-06-29 20:03:20.141948438 [2026-06-29 20:03:20] frigate.app INFO : Output process started: 7612026-06-29 20:03:20.142368170 INFO: Created TensorFlow Lite XNNPACK delegate for CPU.2026-06-29 20:03:20.310334966 [2026-06-29 20:03:20] frigate.api.fastapi_app INFO : Starting FastAPI app2026-06-29 20:03:20.477175913 [2026-06-29 20:03:20] frigate.api.fastapi_app INFO : FastAPI started2026-06-29 20:03:23.830692932 [INFO] Starting go2rtc healthcheck service...2026-06-29 20:04:16.001587468 127.0.0.1 - - [29/Jun/2026:20:04:16 +0930] "" 400 0 "-" "-" "-" request_time="0.000" upstream_response_time="-"
June 29Jun 29 Author 10 minutes ago, JWMutant said:s6-rc: info: service frigate successfully stoppeds6-rc: info: service go2rtc: stoppings6-rc: info: service frigate-log: stoppings6-rc: info: service frigate-log successfully stoppeds6-rc: info: service go2rtc successfully stoppeds6-rc: info: service prepare: stoppings6-rc: info: service go2rtc-log: stoppings6-rc: info: service prepare successfully stoppeds6-rc: info: service go2rtc-log successfully stoppeds6-rc: info: service log-prepare: stoppings6-rc: info: service s6rc-fdholder: stoppings6-rc: info: service log-prepare successfully stoppeds6-rc: info: service legacy-cont-init: stoppings6-rc: info: service s6rc-fdholder successfully stoppeds6-rc: info: service legacy-cont-init successfully stoppeds6-rc: info: service fix-attrs: stoppings6-rc: info: service fix-attrs successfully stoppeds6-rc: info: service s6rc-oneshot-runner: stoppings6-rc: info: service s6rc-oneshot-runner successfully stoppedERROR: driverInitFileInfo 578 result=11ERROR: init 664 result=11ERROR: init 250 result=11s6-rc: info: service s6rc-fdholder: startings6-rc: info: service s6rc-oneshot-runner: startings6-rc: info: service s6rc-oneshot-runner successfully starteds6-rc: info: service fix-attrs: startings6-rc: info: service s6rc-fdholder successfully starteds6-rc: info: service fix-attrs successfully starteds6-rc: info: service legacy-cont-init: startings6-rc: info: service legacy-cont-init successfully starteds6-rc: info: service prepare: startings6-rc: info: service log-prepare: startings6-rc: info: service log-prepare successfully starteds6-rc: info: service nginx-log: startings6-rc: info: service go2rtc-log: startings6-rc: info: service frigate-log: startings6-rc: info: service certsync-log: startings6-rc: info: service nginx-log successfully starteds6-rc: info: service go2rtc-log successfully starteds6-rc: info: service frigate-log successfully starteds6-rc: info: service certsync-log successfully starteds6-rc: info: service prepare successfully starteds6-rc: info: service go2rtc: startings6-rc: info: service go2rtc successfully starteds6-rc: info: service go2rtc-healthcheck: startings6-rc: info: service frigate: startings6-rc: info: service go2rtc-healthcheck successfully starteds6-rc: info: service frigate successfully starteds6-rc: info: service nginx: startings6-rc: info: service nginx successfully starteds6-rc: info: service certsync: startings6-rc: info: service certsync successfully starteds6-rc: info: service legacy-services: startings6-rc: info: service legacy-services successfully started2026-06-29 20:03:06.916540896 [2026-06-29 20:03:06] frigate.record.maintainer INFO : Exiting recording maintenance...2026-06-29 20:03:06.963346576 [2026-06-29 20:03:06] frigate.app INFO : Detection queue closed2026-06-29 20:03:07.464434414 [2026-06-29 20:03:07] frigate.app INFO : Detected frames queue closed2026-06-29 20:03:07.965491043 [2026-06-29 20:03:07] frigate.app INFO : Timeline queue closed2026-06-29 20:03:08.433575419 [2026-06-29 20:03:08] frigate.comms.ws INFO : Exiting websocket client...2026-06-29 20:03:08.924227189 [2026-06-29 20:03:08] peewee.sqliteq INFO : writer received shutdown request, exiting.2026-06-29 20:03:09.595304728 [INFO] Service Frigate exited with code 0 (by signal 0)2026-06-29 20:03:09.598518464 exit with signal: terminated2026-06-29 20:03:09.606208760 [INFO] The go2rtc service exited with code 0 (by signal 0)2026-06-29 20:03:13.831539599 [INFO] Starting NGINX...2026-06-29 20:03:13.918619515 [INFO] Preparing Frigate...2026-06-29 20:03:14.278419744 [INFO] Preparing new go2rtc config...2026-06-29 20:03:14.357538598 [INFO] Starting Frigate...2026-06-29 20:03:14.729370752 [INFO] Starting go2rtc...2026-06-29 20:03:15.135468780 20:03:15.132 INF go2rtc platform=linux/amd64 revision=df95ce3 version=1.9.102026-06-29 20:03:15.135474080 20:03:15.133 INF config path=/config/go2rtc_homekit.yml2026-06-29 20:03:15.135476464 20:03:15.133 INF [rtsp] listen addr=:85542026-06-29 20:03:15.135478809 20:03:15.134 INF [api] listen addr=:19842026-06-29 20:03:15.135481063 20:03:15.134 INF [webrtc] listen addr=:85552026-06-29 20:03:15.321143591 [INFO] Starting certsync...2026-06-29 20:03:15.896723589 127.0.0.1 - - [29/Jun/2026:20:03:15 +0930] "" 400 0 "-" "-" "-" request_time="0.000" upstream_response_time="-"2026-06-29 20:03:18.647144947 2026/06/29 20:03:18 [error] 288#288: *2 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "127.0.0.1:5000"2026-06-29 20:03:18.647170786 2026/06/29 20:03:18 [error] 288#288: *2 auth request unexpected status: 502 while sending to client, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", host: "127.0.0.1:5000"2026-06-29 20:03:18.984423628 [2026-06-29 20:03:18] frigate.util.config INFO : Checking if frigate config needs migration...2026-06-29 20:03:18.988220419 [2026-06-29 20:03:18] frigate.util.config INFO : frigate config does not need migration...2026-06-29 20:03:20.032561495 [2026-06-29 20:03:20] frigate.util.services INFO : Automatically detected nvidia hwaccel for video decoding2026-06-29 20:03:20.044798352 [2026-06-29 20:03:20] frigate.app INFO : Starting Frigate (0.17.2-3d4dd3a)2026-06-29 20:03:20.052265311 [2026-06-29 20:03:20] peewee_migrate.logs INFO : Starting migrations2026-06-29 20:03:20.053442950 [2026-06-29 20:03:20] peewee_migrate.logs INFO : There is nothing to migrate2026-06-29 20:03:20.077129070 [2026-06-29 20:03:20] frigate.app INFO : Recording process started: 7142026-06-29 20:03:20.089310712 [2026-06-29 20:03:20] frigate.app INFO : Review process started: 7152026-06-29 20:03:20.092242821 [2026-06-29 20:03:20] frigate.app INFO : go2rtc process pid: 1712026-06-29 20:03:20.107554089 [2026-06-29 20:03:20] frigate.app INFO : Embedding process started: 7292026-06-29 20:03:20.139370245 [2026-06-29 20:03:20] frigate.detectors WARNING : CPU detectors are not recommended and should only be used for testing or for trial purposes.2026-06-29 20:03:20.141948438 [2026-06-29 20:03:20] frigate.app INFO : Output process started: 7612026-06-29 20:03:20.142368170 INFO: Created TensorFlow Lite XNNPACK delegate for CPU.2026-06-29 20:03:20.310334966 [2026-06-29 20:03:20] frigate.api.fastapi_app INFO : Starting FastAPI app2026-06-29 20:03:20.477175913 [2026-06-29 20:03:20] frigate.api.fastapi_app INFO : FastAPI started2026-06-29 20:03:23.830692932 [INFO] Starting go2rtc healthcheck service...2026-06-29 20:04:16.001587468 127.0.0.1 - - [29/Jun/2026:20:04:16 +0930] "" 400 0 "-" "-" "-" request_time="0.000" upstream_response_time="-"From your logs, I notice that Frigate is starting successfully, but I don't see any specific detector initialization logs that would indicate whether the YOLOv9 model is loading correctly. The logs show the detector process starting but don't show model compilation or loading details.Check your config file and check if the model file is in the correct place.
June 29Jun 29 8 hours ago, yayitazale said:From your logs, I notice that Frigate is starting successfully, but I don't see any specific detector initialization logs that would indicate whether the YOLOv9 model is loading correctly. The logs show the detector process starting but don't show model compilation or loading details.Check your config file and check if the model file is in the correct place.Yes I haven’t gotten as far as setting up the detector because I’m getting the 400 error when trying to access the UI.
June 29Jun 29 From what I can work out the internal port mapping is not correct. But am not sure how to resolve it purely because I haven’t changed anything in regards the initial set up. I haven’t changed any ports or anything like that.
June 30Jun 30 Author 9 hours ago, JWMutant said:From what I can work out the internal port mapping is not correct. But am not sure how to resolve it purely because I haven’t changed anything in regards the initial set up. I haven’t changed any ports or anything like that.I cannot help you without more info, can you share a screenshot of the configuration of the container and the configuration file (config.yaml) created during the initial startup?
June 30Jun 30 I worked out what the problem was/is.Frigate 0.17 serves the UI over HTTPS on port 8971, not HTTP. But when you left click on the Frigate docker and select webui it automatically launches a new webpage as http://192.168.178.22:8971. But what it should be doing is opening a new webpage as https://192.168.178.22:8971.I get the warning but at least I can open it now.Not sure if it is defaulting the new webpage to http because of something on my end or if its how the docker does things. Edited June 30Jun 30 by JWMutant
June 30Jun 30 Author 10 minutes ago, JWMutant said:I worked out what the problem was/is.Frigate 0.17 serves the UI over HTTPS on port 8971, not HTTP. But when you left click on the Frigate docker and select webui it automatically launches a new webpage as http://192.168.178.22:8971. But what it should be doing is opening a new webpage as https://192.168.178.22:8971.I get the warning but at least I can open it now.Not sure if it is defaulting the new webpage to http because of something on my end or if its how the docker does things.https://docs.frigate.video/frigate/installation#ports8971Authenticated UI and API access without TLS. Reverse proxies should use this port.EDIT: You're right, https://docs.frigate.video/configuration/tls, so I just modified the template so that future new installations will use HTTPS by default for the web UI. Thanks Edited June 30Jun 30 by yayitazale
June 30Jun 30 52 minutes ago, yayitazale said:https://docs.frigate.video/frigate/installation#ports8971Authenticated UI and API access without TLS. Reverse proxies should use this port.Thanks very very much for your help and patients.I think I am almost there.For the record when it comes to using my 1080ti I have the following config.But I dont think I have something set up correctly as I am getting the following error : 2026-06-30 17:21:29.010640640 2026-06-30 17:21:29.010578883 [W:onnxruntime:, transformer_memcpy.cc:83 ApplyImpl] 14 Memcpy nodes are added to the graph main_graph for CUDAExecutionProvider. It might have negative impact on performance (including unable to run CUDA graph). Set session_options.log_severity_level=1 to see the detail logs before this message.2026-06-30 17:21:29.013960480 2026-06-30 17:21:29.013926115 [E:onnxruntime:, inference_session.cc:2094 Initialize] This session cannot use the graph capture feature as requested by the user as all compute graph nodes have not been partitioned to the CUDAExecutionProvider2026-06-30 17:21:29.021954998 Process frigate.detector:onnx:2026-06-30 17:21:29.021960147 Traceback (most recent call last):2026-06-30 17:21:29.021962161 File "/usr/lib/python3.11/multiprocessing/process.py", line 314, in _bootstrap2026-06-30 17:21:29.021963434 self.run()2026-06-30 17:21:29.021965027 File "/opt/frigate/frigate/object_detection/base.py", line 143, in run2026-06-30 17:21:29.021966590 object_detector = LocalObjectDetector(detector_config=self.detector_config)2026-06-30 17:21:29.021971950 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^2026-06-30 17:21:29.021997579 File "/opt/frigate/frigate/object_detection/base.py", line 62, in init2026-06-30 17:21:29.021998992 self.detect_api = create_detector(detector_config)2026-06-30 17:21:29.022000124 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^2026-06-30 17:21:29.022035772 File "/opt/frigate/frigate/detectors/__init__.py", line 18, in create_detector2026-06-30 17:21:29.022036844 return api(detector_config)2026-06-30 17:21:29.022037886 ^^^^^^^^^^^^^^^^^^^^2026-06-30 17:21:29.022039108 File "/opt/frigate/frigate/detectors/plugins/onnx.py", line 39, in init2026-06-30 17:21:29.022058646 self.runner = get_optimized_runner(2026-06-30 17:21:29.022059738 ^^^^^^^^^^^^^^^^^^^^^2026-06-30 17:21:29.022061020 File "/opt/frigate/frigate/detectors/detection_runners.py", line 592, in get_optimized_runner2026-06-30 17:21:29.022062042 ort.InferenceSession(2026-06-30 17:21:29.022063535 File "/usr/local/lib/python3.11/dist-packages/onnxruntime/capi/onnxruntime_inference_collection.py", line 472, in init2026-06-30 17:21:29.022064797 self._create_inference_session(providers, provider_options, disabled_optimizers)2026-06-30 17:21:29.022066471 File "/usr/local/lib/python3.11/dist-packages/onnxruntime/capi/onnxruntime_inference_collection.py", line 561, in createinference_session2026-06-30 17:21:29.022087260 sess.initialize_session(providers, provider_options, disabled_optimizers)2026-06-30 17:21:29.022089625 onnxruntime.capi.onnxruntime_pybind11_state.Fail: [ONNXRuntimeError] : 1 : FAIL : This session cannot use the graph capture feature as requested by the user as all compute graph nodes have not been partitioned to the CUDAExecutionProvidermqtt: enabled: false ffmpeg: hwaccel_args: preset-nvidia detectors: onnx: type: onnx device: GPU-6174797f-a41e-9293-c52f-5abb9464f868 providers: - CUDAExecutionProvider cuda_graphs: false model: path: /config/model_cache/yolov9-t-320.onnx model_type: yolo-generic width: 320 height: 320 input_tensor: nchw input_dtype: float labelmap_path: /labelmap/coco-80.txt
June 30Jun 30 Author 13 minutes ago, JWMutant said:Thanks very very much for your help and patients.I think I am almost there.For the record when it comes to using my 1080ti I have the following config.But I dont think I have something set up correctly as I am getting the following error :2026-06-30 17:21:29.010640640 2026-06-30 17:21:29.010578883 [W:onnxruntime:, transformer_memcpy.cc:83 ApplyImpl] 14 Memcpy nodes are added to the graph main_graph for CUDAExecutionProvider. It might have negative impact on performance (including unable to run CUDA graph). Set session_options.log_severity_level=1 to see the detail logs before this message.2026-06-30 17:21:29.013960480 2026-06-30 17:21:29.013926115 [E:onnxruntime:, inference_session.cc:2094 Initialize] This session cannot use the graph capture feature as requested by the user as all compute graph nodes have not been partitioned to the CUDAExecutionProvider2026-06-30 17:21:29.021954998 Process frigate.detector:onnx:2026-06-30 17:21:29.021960147 Traceback (most recent call last):2026-06-30 17:21:29.021962161 File "/usr/lib/python3.11/multiprocessing/process.py", line 314, in _bootstrap2026-06-30 17:21:29.021963434 self.run()2026-06-30 17:21:29.021965027 File "/opt/frigate/frigate/object_detection/base.py", line 143, in run2026-06-30 17:21:29.021966590 object_detector = LocalObjectDetector(detector_config=self.detector_config)2026-06-30 17:21:29.021971950 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^2026-06-30 17:21:29.021997579 File "/opt/frigate/frigate/object_detection/base.py", line 62, in init2026-06-30 17:21:29.021998992 self.detect_api = create_detector(detector_config)2026-06-30 17:21:29.022000124 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^2026-06-30 17:21:29.022035772 File "/opt/frigate/frigate/detectors/__init__.py", line 18, in create_detector2026-06-30 17:21:29.022036844 return api(detector_config)2026-06-30 17:21:29.022037886 ^^^^^^^^^^^^^^^^^^^^2026-06-30 17:21:29.022039108 File "/opt/frigate/frigate/detectors/plugins/onnx.py", line 39, in init2026-06-30 17:21:29.022058646 self.runner = get_optimized_runner(2026-06-30 17:21:29.022059738 ^^^^^^^^^^^^^^^^^^^^^2026-06-30 17:21:29.022061020 File "/opt/frigate/frigate/detectors/detection_runners.py", line 592, in get_optimized_runner2026-06-30 17:21:29.022062042 ort.InferenceSession(2026-06-30 17:21:29.022063535 File "/usr/local/lib/python3.11/dist-packages/onnxruntime/capi/onnxruntime_inference_collection.py", line 472, in init2026-06-30 17:21:29.022064797 self._create_inference_session(providers, provider_options, disabled_optimizers)2026-06-30 17:21:29.022066471 File "/usr/local/lib/python3.11/dist-packages/onnxruntime/capi/onnxruntime_inference_collection.py", line 561, in createinference_session2026-06-30 17:21:29.022087260 sess.initialize_session(providers, provider_options, disabled_optimizers)2026-06-30 17:21:29.022089625 onnxruntime.capi.onnxruntime_pybind11_state.Fail: [ONNXRuntimeError] : 1 : FAIL : This session cannot use the graph capture feature as requested by the user as all compute graph nodes have not been partitioned to the CUDAExecutionProvidermqtt:enabled: false ffmpeg:hwaccel_args: preset-nvidia detectors:onnx: type: onnx device: GPU-6174797f-a41e-9293-c52f-5abb9464f868 providers: - CUDAExecutionProvider cuda_graphs: false model:path: /config/model_cache/yolov9-t-320.onnxmodel_type: yolo-genericwidth: 320height: 320input_tensor: nchwinput_dtype: floatlabelmap_path: /labelmap/coco-80.txt Not sure but I think you don't need this:providers: - CUDAExecutionProvider cuda_graphs: falsehttps://github.com/blakeblackshear/frigate/discussions/23546#discussioncomment-17412679 Edited June 30Jun 30 by yayitazale
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.