[Config Support]: How to install 0.15 beta in proxmox (vm or lxc)

[Polv89]

Describe the problem you are having

Can you tell me the right way to install it on proxmox?
I tried with debian 12 vm + docker but i have some issues
thanks

Version

0.15-5

Frigate config file

mqtt:
  host: mqtt

ffmpeg:
  hwaccel_args:
    - -hwaccel
    - qsv
    - -qsv_device
    - /dev/dri/renderD128
    - -hwaccel_output_format
    - qsv
    - preset-intel-qsv-h265


cameras:
  Retro:
    ffmpeg:
      inputs:
        - path: rtsp://xxx:[email protected]:554//h265Preview_01_main
          roles:
            - detect
            - record
            #- rtmp  # Disabilitato
    detect:
      height: 480
      width: 640
      fps: 5
    record:
      enabled: true
      events:
        retain:
          default: 7  # Mantieni i file relativi agli eventi per 7 giorni
          mode: motion

  Ingresso:
    ffmpeg:
      inputs:
        - path: rtsp://admin:[email protected]:554
          roles:
            - detect
            - record
            #- rtmp  # Disabilitato
    detect:
      height: 480
      width: 640
      fps: 5
    record:
      enabled: true
      events:
        retain:
          default: 7  # Mantieni i file relativi agli eventi per 7 giorni
          mode: motion

  Dietro_casa:
    ffmpeg:
      inputs:
        - path: rtsp://xxx:[email protected]:554//h265Preview_01_main
          roles:
            - detect
            - record
            #- rtmp  # Disabilitato
    detect:
      height: 480
      width: 640
      fps: 5
    record:
      enabled: true
      events:
        retain:
          default: 7  # Mantieni i file relativi agli eventi per 7 giorni
          mode: motion

version: 0.15

Relevant Frigate log output

2025-01-13 15:24:44.191708057  [2025-01-13 15:24:44] frigate.events.cleanup         INFO    : Exiting event cleanup...
2025-01-13 15:24:44.191799740  [2025-01-13 15:24:44] frigate.storage                INFO    : Exiting storage maintainer...
2025-01-13 15:24:44.191926975  [2025-01-13 15:24:44] frigate.ptz.autotrack          INFO    : Exiting autotracker...
2025-01-13 15:24:44.192251448  [2025-01-13 15:24:44] frigate.stats.emitter          INFO    : Exiting stats emitter...
2025-01-13 15:24:44.193326442  [2025-01-13 15:24:44] root                           INFO    : Waiting for detection process to exit gracefully...
2025-01-13 15:24:44.296529937  [2025-01-13 15:24:44] detector.cpu                   INFO    : Exited detection process...
2025-01-13 15:24:44.300730817  [2025-01-13 15:24:44] root                           INFO    : Detection process has exited...
2025-01-13 15:24:44.306242392  [2025-01-13 15:24:44] frigate.object_processing      INFO    : Exiting object processor...
2025-01-13 15:24:44.425390719  [2025-01-13 15:24:44] frigate.events.maintainer      INFO    : Exiting event processor...
2025-01-13 15:24:44.801944484  [2025-01-13 15:24:44] frigate.app                    INFO    : Detection queue closed
2025-01-13 15:24:45.303029399  [2025-01-13 15:24:45] frigate.app                    INFO    : Detected frames queue closed
2025-01-13 15:24:45.804087134  [2025-01-13 15:24:45] frigate.app                    INFO    : Timeline queue closed
2025-01-13 15:24:46.505578119  [2025-01-13 15:24:46] frigate.output.output          INFO    : exiting output process...
2025-01-13 15:24:49.970691111  [2025-01-13 15:24:49] frigate.record.maintainer      INFO    : Exiting recording maintenance...
2025-01-13 15:24:50.827505936  [2025-01-13 15:24:50] frigate.comms.ws               INFO    : Exiting websocket client...
2025-01-13 15:24:50.973287876  [2025-01-13 15:24:50] peewee.sqliteq                 INFO    : writer received shutdown request, exiting.
2025-01-13 15:24:50.989968923  [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-01-13 15:24:50.992210493  exit with signal: terminated
s6-rc: info: service frigate-log successfully stopped
2025-01-13 15:24:50.995960178  [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
s6-rc: info: service go2rtc-log successfully stopped
s6-rc: info: service log-prepare: stopping
s6-rc: info: service s6rc-fdholder: stopping
s6-rc: info: service log-prepare successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service s6rc-fdholder successfully stopped
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-fdholder: starting
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service s6rc-fdholder successfully started
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service log-prepare: starting
s6-rc: info: service log-prepare successfully started
s6-rc: info: service nginx-log: starting
s6-rc: info: service go2rtc-log: starting
s6-rc: info: service frigate-log: starting
s6-rc: info: service certsync-log: starting
s6-rc: info: service go2rtc-log successfully started
s6-rc: info: service go2rtc: starting
s6-rc: info: service nginx-log successfully started
s6-rc: info: service frigate-log successfully started
s6-rc: info: service certsync-log successfully started
s6-rc: info: service go2rtc successfully started
s6-rc: info: service go2rtc-healthcheck: starting
s6-rc: info: service frigate: starting
s6-rc: info: service frigate successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service go2rtc-healthcheck successfully started
2025-01-13 15:28:43.289917856  [INFO] Starting NGINX...
2025-01-13 15:28:43.289917687  [INFO] Preparing new go2rtc config...
2025-01-13 15:28:43.289916338  [INFO] Preparing Frigate...
2025-01-13 15:28:43.367686744  [INFO] Starting Frigate...
2025-01-13 15:28:43.610538918  2025/01/13 15:28:43 [error] 154#154: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.1.192, server: , request: "GET /ws HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "192.168.2.135:5000"
2025-01-13 15:28:43.610567758  2025/01/13 15:28:43 [error] 154#154: *1 auth request unexpected status: 502 while sending to client, client: 192.168.1.192, server: , request: "GET /ws HTTP/1.1", host: "192.168.2.135:5000"
2025-01-13 15:28:43.610661848  192.168.1.192 - - [13/Jan/2025:15:28:43 +0000] "GET /ws HTTP/1.1" 500 579 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36" "-"
2025-01-13 15:28:44.002074233  [INFO] Starting go2rtc...
2025-01-13 15:28:44.129726414  15:28:44.129 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2025-01-13 15:28:44.129730399  15:28:44.129 INF config path=/dev/shm/go2rtc.yaml
2025-01-13 15:28:44.131145745  15:28:44.130 INF [rtsp] listen addr=:8554
2025-01-13 15:28:44.131148639  15:28:44.130 INF [webrtc] listen addr=:8555/tcp
2025-01-13 15:28:44.131150037  15:28:44.131 INF [api] listen addr=:1984
s6-rc: info: service nginx successfully started
s6-rc: info: service certsync: starting
s6-rc: info: service certsync successfully started
s6-rc: info: service legacy-services: starting
2025-01-13 15:28:44.487107986  [INFO] Starting certsync...
s6-rc: info: service legacy-services successfully started
2025-01-13 15:28:44.568300566  127.0.0.1 - - [13/Jan/2025:15:28:44 +0000] "" 400 0 "-" "-" "-"
2025-01-13 15:28:47.796447218  2025/01/13 15:28:47 [error] 155#155: *4 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"
2025-01-13 15:28:47.796450984  2025/01/13 15:28:47 [error] 155#155: *4 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"
2025-01-13 15:28:47.901212667  [2025-01-13 15:28:47] frigate.util.config            INFO    : Checking if frigate config needs migration...
2025-01-13 15:28:47.909842133  [2025-01-13 15:28:47] frigate.util.config            INFO    : frigate config does not need migration...
2025-01-13 15:28:48.023813184  [2025-01-13 15:28:48] frigate.util.services          WARNING : Did not detect hwaccel, using a GPU for accelerated video decoding is highly recommended
2025-01-13 15:28:48.052033014  [2025-01-13 15:28:48] frigate.app                    INFO    : Starting Frigate (0.15.0-173b7aa)
2025-01-13 15:28:48.075845492  [2025-01-13 15:28:48] peewee_migrate.logs            INFO    : Starting migrations
2025-01-13 15:28:48.076498198  [2025-01-13 15:28:48] peewee_migrate.logs            INFO    : There is nothing to migrate
2025-01-13 15:28:48.083486326  [2025-01-13 15:28:48] frigate.app                    INFO    : Recording process started: 351
2025-01-13 15:28:48.090364950  [2025-01-13 15:28:48] frigate.app                    INFO    : Review process started: 352
2025-01-13 15:28:48.094500233  [2025-01-13 15:28:48] frigate.app                    INFO    : go2rtc process pid: 97
2025-01-13 15:28:48.109801765  [2025-01-13 15:28:48] detector.cpu                   INFO    : Starting detection process: 367
2025-01-13 15:28:48.123009887  [2025-01-13 15:28:48] frigate.app                    INFO    : Output process started: 382
2025-01-13 15:28:48.123176866  [2025-01-13 15:28:48] frigate.detectors              WARNING : CPU detectors are not recommended and should only be used for testing or for trial purposes.
2025-01-13 15:28:48.130487187  [2025-01-13 15:28:48] frigate.app                    INFO    : Camera processor not started for disabled camera dummy_camera
2025-01-13 15:28:48.131943980  [2025-01-13 15:28:48] frigate.app                    INFO    : Capture process not started for disabled camera dummy_camera
2025-01-13 15:28:48.247319162  [2025-01-13 15:28:48] frigate.api.fastapi_app        INFO    : Starting FastAPI app
2025-01-13 15:28:48.407170636  [2025-01-13 15:28:48] frigate.api.fastapi_app        INFO    : FastAPI started
2025-01-13 15:28:53.265193932  [INFO] Starting go2rtc healthcheck service...

Relevant go2rtc log output

.

Frigate stats

No response

Operating system

Debian

Install method

Docker Compose

docker-compose file or Docker CLI command

version: '3.9'
services:
  frigate:
    container_name: frigate
    image: blakeblackshear/frigate:0.15.0-beta1
    privileged: true
    restart: unless-stopped
    shm_size: '64mb'
    volumes:
      - ./config:/config
      - ./media:/media/frigate
      - type: tmpfs
        target: /tmp/cache
    ports:
      - "5000:5000"
      - "1935:1935"
    environment:
      FRIGATE_RTSP_PASSWORD: "your_rtsp_password"

Object Detector

CPU (no coral)

Screenshots of the Frigate UI's System metrics pages

No response

Any other information that may be helpful

No response

[NickM-27]

ffmpeg:
  hwaccel_args:
    - -hwaccel
    - qsv
    - -qsv_device
    - /dev/dri/renderD128
    - -hwaccel_output_format
    - qsv
    - preset-intel-qsv-h265

this is invalid, it should just be

ffmpeg:
  hwaccel_args: preset-intel-qsv-h265

[Polv89]

I understand, so:
I installed a proxmox lxc with pve scripts =>
https://community-scripts.github.io/ProxmoxVE/scripts?id=frigate

i tried many configurations, like the one i posted, have a host with i5-7500t, dedicated 4vCPU to the lxc, i have high cpu values, and can't use hardware accelleration.

So, i tried to install from scratch, a clean debian 12 with docker (portainer and compose) but i can't edit the configuration on web, if i charge (also the default configuration) manually editing the config.yml but i can't open the homepage.

[NickM-27]

right, then you should show the logs when doing that. Running in portainer is not recommended, if you prefer a gui then using dockge is recommended.

[Polv89]

I reinstalled in a vm using ubuntu 24.04 with dockge
this is the compose file:

version: "3.9"
services:
  frigate:
    container_name: frigate
    image: ghcr.io/blakeblackshear/frigate:0.15.0-beta5
    privileged: true
    restart: unless-stopped
    shm_size: 64mb
    volumes:
      - ./config:/config
      - ./media:/media/frigate
      - type: tmpfs
        target: /tmp/cache
    ports:
      - 5000:5000
      - 1935:1935
    environment:
      FRIGATE_RTSP_PASSWORD: your_rtsp_password

  i go to http://myip:5000/ but when i try to edit the configuration file it gives me error every time
  my config is

mqtt:
  host: mqtt

ffmpeg:
  hwaccel_args:
    - preset-intel-qsv-h265


cameras:
  Retro:
    ffmpeg:
      inputs:
        - path: rtsp://xxx:[email protected]:554//h265Preview_01_main
          roles:
            - detect
            - record
            #- rtmp  # Disabilitato
    detect:
      height: 480
      width: 640
      fps: 5
    record:
      enabled: true
      events:
        retain:
          default: 7  # Mantieni i file relativi agli eventi per 7 giorni
          mode: motion

  Ingresso:
    ffmpeg:
      inputs:
        - path: rtsp://admin:[email protected]:554
          roles:
            - detect
            - record
            #- rtmp  # Disabilitato
    detect:
      height: 480
      width: 640
      fps: 5
    record:
      enabled: true
      events:
        retain:
          default: 7  # Mantieni i file relativi agli eventi per 7 giorni
          mode: motion

  Dietro_casa:
    ffmpeg:
      inputs:
        - path: rtsp://xxx:[email protected]:554//h265Preview_01_main
          roles:
            - detect
            - record
            #- rtmp  # Disabilitato
    detect:
      height: 480
      width: 640
      fps: 5
    record:
      enabled: true
      events:
        retain:
          default: 7  # Mantieni i file relativi agli eventi per 7 giorni
          mode: motion

version: 0.15-1

[NickM-27]

Okay, then we will need to see that error

[Polv89]

Okay, then we will need to see that error

Now i tried to make a "clean" configuration, step by step

mqtt:
  enabled: false

ffmpeg:
  hwaccel_args: preset-intel-qsv-h264

cameras:
  Retro: # <------ Name the camera
    enabled: true
    ffmpeg:
      inputs:
        - path: rtsp://xxx:xxx@xxx:xxx//h264Preview_01_sub # <----- The stream you want to use for detection
          roles:
            - detect
    detect:
      enabled: false # <---- disable detection until you have a working camera feed
      width: 1280
      height: 720

  Dietro_casa: # <------ Name the camera
    enabled: true
    ffmpeg:
      inputs:
        - path: rtsp://xxx:xxx@xxx:554//h264Preview_01_sub  # <----- The stream you want to use for detection
          roles:
            - detect
    detect:
      enabled: false # <---- disable detection until you have a working camera feed
      width: 1280
      height: 720

  Ingresso: # <------ Name the camera
    enabled: true
    ffmpeg:
      inputs:
        - path: rtsp://xxx:xxx@xxx:554 # <----- The stream you want to use for detection
          roles:
            - detect
    detect:
      enabled: false # <---- disable detection until you have a working camera feed
      width: 640
      height: 480

version: 0.15-1

It seems to work, but if i try to add record parameters that i used with 0.14 i have an errore and refresh the page, so i can't know the specific error.

The config page should not refresh automatically, what record config are you referring to?

Another thing, if i write h264Preview_01_sub and hwaccel_args: preset-intel-qsv-h264 seems to work, if i write h265 no.

which makes sense, because the sub stream is h264

[Polv89]

Is this configuration right ?
(i have enabled recording only for one for test it)

I want to:

1. watch cameras with better resolution
2. record when detect motion at low resolution

mqtt:
  enabled: false

ffmpeg:
  hwaccel_args: preset-vaapi

cameras:
  Retro: # <------ Nome della telecamera
    enabled: true
    ffmpeg:
      inputs:
        - path: rtsp://xx:[email protected]:554//h264Preview_01_sub # <----- Stream sub per la rilevazione
          roles:
            - detect
        - path: rtsp://xx:[email protected]:554//h264Preview_01_Main # <----- Stream principale per la visualizzazione e la registrazione
          roles:
            - record
    detect:
      enabled: true # <---- disable detection until you have a working camera feed
      width: 640
      height: 480

  Dietro_casa: # <------ Nome della telecamera
    enabled: true
    ffmpeg:
      inputs:
        - path: rtsp://xx:[email protected]:554//h264Preview_01_sub  # <----- Stream sub per la rilevazione
          roles:
            - detect
        - path: rtsp://xx:[email protected]:554//h264Preview_01_Main # <----- Stream principale per la visualizzazione e la registrazione
          roles:
            - record
    detect:
      enabled: false # <---- disable detection until you have a working camera feed
      width: 640
      height: 480

  Ingresso: # <------ Nome della telecamera
    enabled: true
    ffmpeg:
      inputs:
        - path: rtsp://admin:[email protected]/cam/realmonitor?channel=1&subtype=01&authbasic=xx # <----- Stream sub per la rilevazione
          roles:
            - detect
        - path: rtsp://admin:[email protected]/cam/realmonitor?channel=1&subtype=00&authbasic=xx# <----- Stream principale per la visualizzazione e la registrazione
          roles:
            - record
    detect:
      enabled: false # <---- disable detection until you have a working camera feed
      width: 640
      height: 480

record:
  enabled: True
  retain:
    days: 3
    mode: motion
  alerts:
    retain:
      days: 3
      mode: motion
  detections:
    retain:
      days: 3
      mode: motion



version: 0.15-1