Hello
My custom app is running:
but there’s no page being served out at the port (which I have set to 30068).
Here are my custom app settings:
but they are sparsely populated because I don’t know how to edit these boxes to make it work.
I have the app catalogue version of Frigate working and I have chosen to freeze it at v0.13. I now want my custom app to work at the same version, which I can then experiment with updating to 0.14.
Can anyone tell me how to modify my custom app settings so that the webUI gets served out please?
I’m ready to submit screenshots, logs, I can ssh into the TrueNAS and look at internal settings - all with guidance because I am out of my depth.
(I am unable to u/g to EE at the moment).
edit - when I first installed it (port 15000 defaulted) it was running but editing the port to :30068 caused it to hang at “deploying” only. I have changed it back to :15000 and it is running again (but no UI served).
These are the logs I see:
025-01-03 18:30:45.296217+00:00s6-rc: info: service s6rc-fdholder: starting
2025-01-03 18:30:45.296542+00:00s6-rc: info: service s6rc-oneshot-runner: starting
2025-01-03 18:30:45.303017+00:00s6-rc: info: service s6rc-oneshot-runner successfully started
2025-01-03 18:30:45.303599+00:00s6-rc: info: service fix-attrs: starting
2025-01-03 18:30:45.303640+00:00s6-rc: info: service s6rc-fdholder successfully started
2025-01-03 18:30:45.308814+00:00s6-rc: info: service fix-attrs successfully started
2025-01-03 18:30:45.308964+00:00s6-rc: info: service legacy-cont-init: starting
2025-01-03 18:30:45.314102+00:00s6-rc: info: service legacy-cont-init successfully started
2025-01-03 18:30:45.314267+00:00s6-rc: info: service log-prepare: starting
2025-01-03 18:30:45.327203+00:00s6-rc: info: service log-prepare successfully started
2025-01-03 18:30:45.327264+00:00s6-rc: info: service nginx-log: starting
2025-01-03 18:30:45.327460+00:00s6-rc: info: service go2rtc-log: starting
2025-01-03 18:30:45.327650+00:00s6-rc: info: service frigate-log: starting
2025-01-03 18:30:45.329968+00:00s6-rc: info: service nginx-log successfully started
2025-01-03 18:30:45.330252+00:00s6-rc: info: service go2rtc-log successfully started
2025-01-03 18:30:45.330979+00:00s6-rc: info: service go2rtc: starting
2025-01-03 18:30:45.331140+00:00s6-rc: info: service frigate-log successfully started
2025-01-03 18:30:45.333768+00:00s6-rc: info: service go2rtc successfully started
2025-01-03 18:30:45.333979+00:00s6-rc: info: service go2rtc-healthcheck: starting
2025-01-03 18:30:45.334146+00:00s6-rc: info: service frigate: starting
2025-01-03 18:30:45.336930+00:00s6-rc: info: service go2rtc-healthcheck successfully started
2025-01-03 18:30:45.336961+00:00s6-rc: info: service frigate successfully started
2025-01-03 18:30:45.337612+00:00s6-rc: info: service nginx: starting
2025-01-03 18:30:45.346501+00:00s6-rc: info: service nginx successfully started
2025-01-03 18:30:45.346681+00:00s6-rc: info: service legacy-services: starting
2025-01-03 18:30:45.347708+00:002025-01-03 18:30:45.347483664 [INFO] Preparing new go2rtc config...
2025-01-03 18:30:45.350722+00:002025-01-03 18:30:45.350545248 [INFO] Preparing Frigate...
2025-01-03 18:30:45.350762+00:002025-01-03 18:30:45.350592940 [ERROR] Frigate config file not found
2025-01-03 18:30:45.354754+00:002025-01-03 18:30:45.354399415 [INFO] Starting NGINX...
2025-01-03 18:30:45.358728+00:00s6-rc: info: service legacy-services successfully started
2025-01-03 18:30:45.359037+00:002025-01-03 18:30:45.358927623 [INFO] Service Frigate exited with code 1 (by signal 0)
2025-01-03 18:30:45.365941+00:00s6-rc: info: service legacy-services: stopping
2025-01-03 18:30:45.370737+00:00s6-rc: info: service legacy-services successfully stopped
2025-01-03 18:30:45.371089+00:00s6-rc: info: service nginx: stopping
2025-01-03 18:30:45.371147+00:00s6-rc: info: service go2rtc-healthcheck: stopping
2025-01-03 18:30:45.379932+00:002025-01-03 18:30:45.379745853 [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
2025-01-03 18:30:45.380857+00:00s6-rc: info: service go2rtc-healthcheck successfully stopped
2025-01-03 18:30:45.381415+00:002025-01-03 18:30:45.381300846 [INFO] Service NGINX exited with code 256 (by signal 15)
2025-01-03 18:30:45.382850+00:00s6-rc: info: service nginx successfully stopped
2025-01-03 18:30:45.383000+00:00s6-rc: info: service nginx-log: stopping
2025-01-03 18:30:45.383143+00:00s6-rc: info: service frigate: stopping
2025-01-03 18:30:45.384948+00:00s6-rc: info: service frigate successfully stopped
2025-01-03 18:30:45.385177+00:00s6-rc: info: service go2rtc: stopping
2025-01-03 18:30:45.385470+00:00s6-rc: info: service frigate-log: stopping
2025-01-03 18:30:45.386762+00:00s6-rc: info: service nginx-log successfully stopped
2025-01-03 18:30:45.388540+00:00s6-rc: info: service frigate-log successfully stopped
2025-01-03 18:30:45.393968+00:002025-01-03 18:30:45.393811143 [INFO] The go2rtc service exited with code 256 (by signal 15)
2025-01-03 18:30:45.395125+00:00s6-rc: info: service go2rtc successfully stopped
2025-01-03 18:30:45.395420+00:00s6-rc: info: service go2rtc-log: stopping
2025-01-03 18:30:45.400203+00:00s6-rc: info: service go2rtc-log successfully stopped
2025-01-03 18:30:45.400527+00:00s6-rc: info: service log-prepare: stopping
2025-01-03 18:30:45.400694+00:00s6-rc: info: service s6rc-fdholder: stopping
2025-01-03 18:30:45.402433+00:00s6-rc: info: service log-prepare successfully stopped
2025-01-03 18:30:45.402660+00:00s6-rc: info: service legacy-cont-init: stopping
2025-01-03 18:30:45.404122+00:00s6-rc: info: service s6rc-fdholder successfully stopped
2025-01-03 18:30:45.414509+00:00s6-rc: info: service legacy-cont-init successfully stopped
2025-01-03 18:30:45.415466+00:00s6-rc: info: service fix-attrs: stopping
2025-01-03 18:30:45.416928+00:00s6-rc: info: service fix-attrs successfully stopped
2025-01-03 18:30:45.417128+00:00s6-rc: info: service s6rc-oneshot-runner: stopping
2025-01-03 18:30:45.420785+00:00s6-rc: info: service s6rc-oneshot-runner successfully stopped
and when I try to open a shell I see this:
