Beta 2 authentication #11957

ondrejmo · 2024-06-14T12:36:51Z

ondrejmo
Jun 14, 2024

Describe the problem you are having

The authentication can be bypassed / does not work. I enabled it using auth.mode: native, changed the default user/password from logs to something different, but when I try to access the web interface in anonymous browser window I can still see/do everything, even-though I did not log in.

Steps to reproduce

deploy frigate
change default user/pass
access frigate in anonymous browser window
you see everything instead of authentication prompt

Version

0.14.0 beta 2

Frigate config file

---

auth:
  mode: native

mqtt:
  # Required: host name
  host: nats.example.svc
  # Optional: port (default: shown below)
  port: 1883
  # Optional: topic prefix (default: shown below)
  # WARNING: must be unique if you are running multiple instances
  topic_prefix: frigate
  # Optional: client id (default: shown below)
  # WARNING: must be unique if you are running multiple instances
  client_id: frigate
  # Optional: user
  user: "{FRIGATE_MQTT_USER}"
  # Optional: password
  # NOTE: Environment variables that begin with 'FRIGATE_' may be referenced in {}.
  #       eg. password: '{FRIGATE_MQTT_PASSWORD}'
  password: "{FRIGATE_MQTT_PASSWORD}"
  # Optional: interval in seconds for publishing stats (default: shown below)
  stats_interval: 60

detectors:
  coral:
    type: edgetpu
    device: usb
  cpu1:
    type: cpu

cameras: {}
#   front_door:
#     ffmpeg:
#       inputs:
#         - path: rtsp://{FRIGATE_RSTP_USERNAME}:{FRIGATE_RTSP_PASSWORD}@10.0.10.10:554/cam/realmonitor?channel=1&subtype=2
#           roles:
#             - detect
#             - rtmp
#     width: 1280
#     height: 720
#     fps: 5

Relevant log output

Operating system

Ubuntu 22.04 server

Install method

Kubernetes

Network connection

Wired

Camera make and model

does not matter

Any other information that may be helpful

No response

Answered by hawkeye217

Jun 14, 2024

What port are you using? Authentication is available on port 8080 as the docs indicate.

View full answer

hawkeye217 · 2024-06-14T12:43:53Z

hawkeye217
Jun 14, 2024
Collaborator

What port are you using? Authentication is available on port 8080 as the docs indicate.

3 replies

ondrejmo Jun 14, 2024
Author

Thanks for the swift answer, could please point me to the particular part of documentation where this is explained?

hawkeye217 Jun 14, 2024
Collaborator

https://deploy-preview-11419--frigate-docs.netlify.app/configuration/authentication/

JSkye3293 Jun 30, 2024

Hello, I'd like to add to this. I've also got a similar issue with the ports on 8971, when enabled it shows a blank page saying it failed to connect. My instance was migrated over from version 13, I have disabled TLS in hopes that would solve it. I do not see any nginx errors that are related to serving these ports, portainer does show that its being exposed. Port 5000 is disabled, but seems to be the only one to work. I did follow the updated documentation to the best of my ability however I feel that there may need to be a troubleshooting section added to help get this working in case more issues like this pop up.
Love the project, keep up the good work!

Here is both my docker compose and Config, with the latest log that I have. Thanks!
Please note I have removed all user creds and active IP addresses for security.

Docker compose

version: "3.9"
services:
  frigate:
    container_name: frigate-beta
    restart: unless-stopped
    image: ghcr.io/blakeblackshear/frigate:0.14.0-beta3-tensorrt
    deploy:    # <------------- Add this section
      resources:
        reservations:
          devices:
            - driver: nvidia
              #device_ids: ['1']
             # count: 1 # number of GPUs
              capabilities: [gpu]

    shm_size: "4gb"

    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /home/administrator/frigate/config:/config
      - /home/administrator/frigate/media:/media/frigate
     # - /home/administrator/ffmpeg:/usr/lib/btbn-ffmpeg:ro
      - type: tmpfs # Optional: 1GB of memory, reduces SSD/SD Card wear
        target: /tmp/cache
        tmpfs:
          size: 4000000000


    ports:
      - "8971:8971"
     # - "5000:5000" # Internal unauthenticated access. Expose carefully.
      - "8554:8554" # RTSP feeds
      - "8555:8555/tcp" # WebRTC over tcp
      - "8555:8555/udp" # WebRTC over udp

 #   environment:
 #      FRIGATE_RTSP_PASSWORD: "password"

config.yml


mqtt:
  enabled: false

tls:
  enabled: False

# Depreciated from 0.14.1-beta2 to beta3, could not get to work in beta versions
#auth:
#  mode: native

detectors:
  tensorrt:
    type: tensorrt
    device: 0 #This is the default, select the first GPU

model:
  path: /config/model_cache/tensorrt/yolov7-320.trt
  input_tensor: nchw
  input_pixel_format: rgb
  width: 320
  height: 320

go2rtc:
  streams:
    cam1:
      - rtsp:/user:[email protected]:554/cam/realmonitor?channel=1&subtype=0
    cam2:
      - rtsp:/user:[email protected]:554/cam/realmonitor?channel=1&subtype=0
    cam3:
      - rtsp:/user:[email protected]:554/cam/realmonitor?channel=1&subtype=0


# Optional: ffmpeg configuration
# More information about presets at https://docs.frigate.video/configuration/ffmpeg_presets
ffmpeg:
  # Optional: global ffmpeg args (default: shown below)
  global_args: -hide_banner -loglevel warning -threads 2
  # Optional: global hwaccel args (default: shown below)
  # NOTE: See hardware acceleration docs for your specific device
  hwaccel_args: preset-nvidia-h264
  # Optional: global input args (default: shown below)
  input_args: preset-rtsp-generic
  # Optional: global output args
  output_args:
    # Optional: output args for detect streams (default: shown below)
    detect: -threads 2 -f rawvideo -pix_fmt yuv420p
    # Optional: output args for record streams (default: shown below)
    record: preset-record-generic
    # Optional: output args for rtmp streams (default: shown below)
  retry_interval: 10



cameras:
  cam1: # <--- this will be changed to your actual camera later
    enabled: true
    ffmpeg:
      hwaccel_args: preset-nvidia-h264
      inputs:
        - path: rtsp:/user:[email protected]:554/cam/realmonitor?channel=1&subtype=0
          roles:
            - detect
            - record

    record:
      enabled: true
      retain:
        days: 7
        mode: motion
      events:
        retain:
          default: 14
          mode: active_objects

    motion:
      threshold: 80
      contour_area: 45
      improve_contrast: 'true'
  cam2: # <--- this will be changed to your actual camera later
    enabled: true
    ffmpeg:
      hwaccel_args: preset-nvidia-h264
      inputs:
        - path: rtsp:/user:[email protected]:554/cam/realmonitor?channel=1&subtype=0
          roles:
            - detect
            - record

    record: # <----- Enable recording
      enabled: true
      retain:
        days: 7
        mode: motion
      events:
        retain:
          default: 14
          mode: active_objects


    motion:
      threshold: 80
      contour_area: 50
      improve_contrast: 'true'
    objects:
      filters:
        tree:
          mask: 
            0.455,0.388,0.463,0.261,0.345,0.252,0.326,0.239,0.322,0.191,0.362,0.037,0.632,0.117,0.619,0.151,0.635,0.144,0.635,0.173,0.617,0.199,>
  cam3: # <--- this will be changed to your actual camera later
    enabled: true
    ffmpeg:
      hwaccel_args: preset-nvidia-h264
      inputs:
        - path: rtsp:/user:[email protected]:554/cam/realmonitor?channel=1&subtype=0
          roles:
            - detect
            - record

    record: # <----- Enable recording
      enabled: true
      retain:
        days: 7
        mode: motion
      events:
        retain:
          default: 14
          mode: active_objects


    motion:
      threshold: 80
      contour_area: 50
      improve_contrast: 'true'
      mask: 
        0.13,0.401,0.151,0.344,0.327,0.218,0.39,0.178,0.461,0.163,0.486,0.184,0.545,0.225,0.555,0.264,0.557,0.289,0.55,0.316,0.554,0.353,0.567,0>
    zones:
      Back_Door:
        coordinates: 0.72,0.618,0.791,0.083,0.605,0.012,0.575,0.373,0.626,0.505
        objects: person
    review:
      alerts:
        required_zones: Back_Door
      detections:
        required_zones: Back_Door
detect:
  # Optional: width of the frame for the input with the detect role (default: use native stream resolution)
  width: 1280
  # Optional: height of the frame for the input with the detect role (default: use native stream resolution)
  height: 720
  # Optional: desired fps for your camera for the input with the detect role (default: shown below)
  # NOTE: Recommended value of 5. Ideally, try and reduce your FPS on the camera.
  fps: 20
  # Optional: enables detection for the camera (default: True)
  enabled: true
  # Optional: Number of consecutive detection hits required for an object to be initialized in the tracker. (default: 1/2 the frame rate)
  min_initialized: 2
  # Optional: Number of frames without a detection before Frigate considers an object to be gone. (default: 5x the frame rate)
  max_disappeared: 75
  # Optional: Configuration for stationary object tracking
  stationary:
    # Optional: Frequency for confirming stationary objects (default: same as threshold)
    # When set to 1, object detection will run to confirm the object still exists on every frame.
    # If set to 10, object detection will run to confirm the object still exists on every 10th frame.
    interval: 50
    # Optional: Number of frames without a position change for an object to be considered stationary (default: 10x the frame rate or 10s)
    threshold: 150
    # Optional: Define a maximum number of frames for tracking a stationary object (default: not set, track forever)
    # This can help with false positives for objects that should only be stationary for a limited amount of time.
    # It can also be used to disable stationary object tracking. For example, you may want to set a value for person, but leave
    # car at the default.
    # WARNING: Setting these values overrides default behavior and disables stationary object tracking.
    #          There are very few situations where you would want it disabled. It is NOT recommended to
    #          copy these values from the example config into your config unless you know they are needed.
    max_frames:
      # Optional: Default for all object types (default: not set, track forever)
      default: 3000
      # Optional: Object specific values
      objects:
        person: 1000
        car: 1000
        tree: 500
  # Optional: Milliseconds to offset detect annotations by (default: shown below).
  # There can often be latency between a recording and the detect process,
  # especially when using separate streams for detect and record.
  # Use this setting to make the timeline bounding boxes more closely align
  # with the recording. The value can be positive or negative.
  # TIP: Imagine there is an event clip with a person walking from left to right.
  #      If the event timeline bounding box is consistently to the left of the person
  #      then the value should be decreased. Similarly, if a person is walking from
  #      left to right and the bounding box is consistently ahead of the person
  #      then the value should be increased.
  # TIP: This offset is dynamic so you can change the value and it will update existing
  #      events, this makes it easy to tune.
  # WARNING: Fast moving objects will likely not have the bounding box align.
  annotation_offset: 0

# Optional: Object configuration
# NOTE: Can be overridden at the camera level
objects:
  # Optional: list of objects to track from labelmap.txt (default: shown below)
  track:
    - person
    - bike
    - car
    - dog
    - cat
    - tree




motion:
  # Optional: The threshold passed to cv2.threshold to determine if a pixel is different enough to be counted as motion. (default: shown below)
  # Increasing this value will make motion detection less sensitive and decreasing it will make motion detection more sensitive.
  # The value should be between 1 and 255.
  threshold: 30
  # Optional: The percentage of the image used to detect lightning or other substantial changes where motion detection
  #           needs to recalibrate. (default: shown below)
  # Increasing this value will make motion detection more likely to consider lightning or ir mode changes as valid motion.
  # Decreasing this value will make motion detection more likely to ignore large amounts of motion such as a person approaching
  # a doorbell camera.
  lightning_threshold: 0.8
  # Optional: Minimum size in pixels in the resized motion image that counts as motion (default: shown below)
  # Increasing this value will prevent smaller areas of motion from being detected. Decreasing will
  # make motion detection more sensitive to smaller moving objects.
  # As a rule of thumb:
  #  - 10 - high sensitivity
  #  - 30 - medium sensitivity
  #  - 50 - low sensitivity
  contour_area: 30
  # Optional: Alpha value passed to cv2.accumulateWeighted when averaging frames to determine the background (default: shown below)
  # Higher values mean the current frame impacts the average a lot, and a new object will be averaged into the background faster.
  # Low values will cause things like moving shadows to be detected as motion for longer.
  # https://www.geeksforgeeks.org/background-subtraction-in-an-image-using-concept-of-running-average/
  frame_alpha: 0.01
  # Optional: Height of the resized motion frame  (default: 100)
  # Higher values will result in more granular motion detection at the expense of higher CPU usage.
  # Lower values result in less CPU, but small changes may not register as motion.
  frame_height: 100
  # Optional: motion mask
  # NOTE: see docs for more detailed info on creating masks
#   NOTE: see docs for more detailed info on creating masks
 # mask: 0,900,1080,900,1080,1920,0,1920
  # Optional: improve contrast (default: shown below)
  # Enables dynamic contrast improvement. This should help improve night detections at the cost of making motion detection more sensitive
  # for daytime.
  improve_contrast: true
  # Optional: Delay when updating camera motion through MQTT from ON -> OFF (default: shown below).
  mqtt_off_delay: 30


record:
  # Optional: Enable recording (default: shown below)
  # WARNING: If recording is disabled in the config, turning it on via
  #          the UI or MQTT later will have no effect.
  enabled: true
  # Optional: Number of minutes to wait between cleanup runs (default: shown below)
  # This can be used to reduce the frequency of deleting recording segments from disk if you want to minimize i/o
  expire_interval: 60
  # Optional: Sync recordings with disk on startup and once a day (default: shown below).
  sync_recordings: false
  # Optional: Retention settings for recording
  retain:
    # Optional: Number of days to retain recordings regardless of events (default: shown below)
    # NOTE: This should be set to 0 and retention should be defined in events section below
    #       if you only want to retain recordings of events.
    days: 31
    # Optional: Mode for retention. Available options are: all, motion, and active_objects
    #   all - save all recording segments regardless of activity
    #   motion - save all recordings segments with any detected motion
    #   active_objects - save all recording segments with active/moving objects
    # NOTE: this mode only applies when the days setting above is greater than 0
    mode: all
  # Optional: Recording Export Settings
  export:
    # Optional: Timelapse Output Args (default: shown below).
    # NOTE: The default args are set to fit 24 hours of recording into 1 hour playback.
    # See https://stackoverflow.com/a/58268695 for more info on how these args work.
    # As an example: if you wanted to go from 24 hours to 30 minutes that would be going
    # from 86400 seconds to 1800 seconds which would be 1800 / 86400 = 0.02.
    # The -r (framerate) dictates how smooth the output video is.
    # So the args would be -vf setpts=0.02*PTS -r 30 in that case.
    timelapse_args: -vf setpts=0.04*PTS -r 30
  # Optional: Event recording settings
  events:
    # Optional: Number of seconds before the event to include (default: shown below)
    pre_capture: 5
    # Optional: Number of seconds after the event to include (default: shown below)
    post_capture: 5
    # Optional: Objects to save recordings for. (default: all tracked objects)
    objects:
      - person
    # Optional: Restrict recordings to objects that entered any of the listed zones (default: no required zones)
    #required_zones: []
    # Optional: Retention settings for recordings of events
    retain:
      # Required: Default retention days (default: shown below)
      default: 31
      # Optional: Mode for retention. (default: shown below)
      #   all - save all recording segments for events regardless of activity
      #   motion - save all recordings segments for events with any detected motion
      #   active_objects - save all recording segments for event with active/moving objects
      #
      # NOTE: If the retain mode for the camera is more restrictive than the mode configured
      #       here, the segments will already be gone by the time this mode is applied.
      #       For example, if the camera retain mode is "motion", the segments without motion are
      #       never stored, so setting the mode to "all" here won't bring them back.
      mode: motion
      # Optional: Per object retention days
      objects:
        person: 31
        car: 14







# Optional: Configuration for the jpg snapshots written to the clips directory for each event
# NOTE: Can be overridden at the camera level
snapshots:
  # Optional: Enable writing jpg snapshot to /media/frigate/clips (default: shown below)
  enabled: true
  # Optional: save a clean PNG copy of the snapshot image (default: shown below)
  clean_copy: true
  # Optional: print a timestamp on the snapshots (default: shown below)
  timestamp: false
  # Optional: draw bounding box on the snapshots (default: shown below)
  bounding_box: true
  # Optional: crop the snapshot (default: shown below)
  crop: false
  # Optional: height to resize the snapshot to (default: original size)
  #height: 175
  # Optional: Restrict snapshots to objects that entered any of the listed zones (default: no required zones)
  #required_zones: []
  # Optional: Camera override for retention settings (default: global values)
  retain:
    # Required: Default retention days (default: shown below)
    default: 62
    # Optional: Per object retention days
    objects:
      person: 62
  # Optional: quality of the encoded jpeg, 0-100 (default: shown below)
  quality: 70





version: 0.14

Latest Log


s6-rc: info: service nginx: stopping
s6-rc: info: service certsync-log: stopping
s6-rc: info: service certsync-log successfully stopped
2024-06-30 14:57:40.015492108  [INFO] Service NGINX exited with code 0 (by signal 0)
s6-rc: info: service nginx successfully stopped
s6-rc: info: service nginx-log: stopping
s6-rc: info: service frigate: stopping
s6-rc: info: service frigate successfully stopped
s6-rc: info: service trt-model-prepare: stopping
s6-rc: info: service go2rtc: stopping
s6-rc: info: service frigate-log: stopping
s6-rc: info: service nginx-log successfully stopped
2024-06-30 14:57:40.021400176  exit with signal: terminated
s6-rc: info: service trt-model-prepare successfully stopped
s6-rc: info: service frigate-log successfully stopped
2024-06-30 14:57:40.029643370  [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 trt-model-prepare: starting
s6-rc: info: service log-prepare: starting
No models to convert.
s6-rc: info: service trt-model-prepare successfully started
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 nginx-log successfully started
s6-rc: info: service frigate-log successfully started
s6-rc: info: service go2rtc-log successfully started
s6-rc: info: service go2rtc: starting
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
2024-06-30 14:57:45.549510972  [INFO] Preparing Frigate...
2024-06-30 14:57:45.551407226  [INFO] Starting NGINX...
2024-06-30 14:57:45.552568130  [INFO] Preparing new go2rtc config...
2024-06-30 14:57:45.565547356  [INFO] Starting Frigate...
2024-06-30 14:57:45.991654651  [INFO] Starting go2rtc...
2024-06-30 14:57:46.170970505  14:57:46.170 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2024-06-30 14:57:46.170977426  14:57:46.170 INF config path=/dev/shm/go2rtc.yaml
2024-06-30 14:57:46.171812650  14:57:46.171 INF [api] listen addr=:1984
2024-06-30 14:57:46.171817720  14:57:46.171 INF [rtsp] listen addr=:8554
2024-06-30 14:57:46.172126115  14:57:46.172 INF [webrtc] listen addr=:8555/tcp
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
2024-06-30 14:57:46.680023896  [INFO] Starting certsync...
s6-rc: info: service legacy-services successfully started
2024-06-30 14:57:48.037405349  [2024-06-30 14:57:48] frigate.app                    INFO    : Starting Frigate (0.14.0-4e5a6eb)
2024-06-30 14:57:48.037517500  [2024-06-30 14:57:48] frigate.util.config            INFO    : Checking if frigate config needs migration...
2024-06-30 14:57:48.124396789  [2024-06-30 14:57:48] frigate.util.config            INFO    : frigate config does not need migration...
2024-06-30 14:57:48.164958922  [2024-06-30 14:57:48] frigate.config                 WARNING : lorex1 detect fps is set to 20. This does NOT need to match your camera's frame rate. High values could lead to reduced performance. Recommended value is 5.
2024-06-30 14:57:48.167092252  [2024-06-30 14:57:48] frigate.config                 WARNING : lorex2 detect fps is set to 20. This does NOT need to match your camera's frame rate. High values could lead to reduced performance. Recommended value is 5.
2024-06-30 14:57:48.170109435  [2024-06-30 14:57:48] frigate.config                 WARNING : lorex3 detect fps is set to 20. This does NOT need to match your camera's frame rate. High values could lead to reduced performance. Recommended value is 5.
2024-06-30 14:57:48.583457767  [2024-06-30 14:57:48] peewee_migrate.logs            INFO    : Starting migrations
2024-06-30 14:57:48.584626906  [2024-06-30 14:57:48] peewee_migrate.logs            INFO    : There is nothing to migrate
2024-06-30 14:57:48.613423824  [2024-06-30 14:57:48] frigate.app                    INFO    : Recording process started: 401
2024-06-30 14:57:48.613467330  [2024-06-30 14:57:48] frigate.app                    INFO    : Recording process started: 402
2024-06-30 14:57:48.618345011  [2024-06-30 14:57:48] frigate.app                    INFO    : go2rtc process pid: 105
2024-06-30 14:57:48.656775141  [2024-06-30 14:57:48] frigate.app                    INFO    : Output process started: 431
2024-06-30 14:57:48.670867162  [2024-06-30 14:57:48] detector.tensorrt              INFO    : Starting detection process: 429
2024-06-30 14:57:48.725485938  [2024-06-30 14:57:48] frigate.app                    INFO    : Camera processor started for lorex1: 460
2024-06-30 14:57:48.735246466  [2024-06-30 14:57:48] frigate.app                    INFO    : Camera processor started for lorex2: 465
2024-06-30 14:57:48.744281459  [2024-06-30 14:57:48] frigate.app                    INFO    : Camera processor started for lorex3: 472
2024-06-30 14:57:48.756364784  [2024-06-30 14:57:48] frigate.app                    INFO    : Capture process started for lorex1: 485
2024-06-30 14:57:48.757364806  [2024-06-30 14:57:48] frigate.app                    INFO    : Capture process started for lorex2: 493
2024-06-30 14:57:48.767068840  [2024-06-30 14:57:48] frigate.app                    INFO    : Capture process started for lorex3: 499
2024-06-30 14:57:48.916814585  [2024-06-30 14:57:48] frigate.detectors.plugins.tensorrt INFO    : Loaded engine size: 184 MiB
2024-06-30 14:57:49.121764229  [2024-06-30 14:57:49] frigate.detectors.plugins.tensorrt INFO    : [MemUsageChange] Init cuBLAS/cuBLASLt: CPU +7, GPU +8, now: CPU 320, GPU 261 (MiB)
2024-06-30 14:57:49.127996109  [2024-06-30 14:57:49] frigate.detectors.plugins.tensorrt INFO    : [MemUsageChange] Init cuDNN: CPU +1, GPU +10, now: CPU 321, GPU 271 (MiB)
2024-06-30 14:57:49.141024174  [2024-06-30 14:57:49] frigate.detectors.plugins.tensorrt INFO    : [MemUsageChange] TensorRT-managed allocation in engine deserialization: CPU +0, GPU +184, now: CPU 0, GPU 184 (MiB)
2024-06-30 14:57:49.155766780  [2024-06-30 14:57:49] frigate.detectors.plugins.tensorrt INFO    : [MemUsageChange] Init cuBLAS/cuBLASLt: CPU +0, GPU +8, now: CPU 137, GPU 264 (MiB)
2024-06-30 14:57:49.155938210  [2024-06-30 14:57:49] frigate.detectors.plugins.tensorrt INFO    : [MemUsageChange] Init cuDNN: CPU +0, GPU +8, now: CPU 137, GPU 272 (MiB)
2024-06-30 14:57:49.158565840  [2024-06-30 14:57:49] frigate.detectors.plugins.tensorrt INFO    : [MemUsageChange] TensorRT-managed allocation in IExecutionContext creation: CPU +0, GPU +29, now: CPU 0, GPU 213 (MiB)
2024-06-30 14:57:55.550301292  [INFO] Starting go2rtc healthcheck service...

NickM-27 · 2024-06-14T12:44:08Z

NickM-27
Jun 14, 2024
Collaborator Sponsor

What is your docker compose? Sounds like you're using port 5000 for access which, as the docs explain, is unauthenticated

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Beta 2 authentication #11957

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 2 comments 3 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

Select a reply

Beta 2 authentication #11957

ondrejmo Jun 14, 2024

Describe the problem you are having

Steps to reproduce

Version

Frigate config file

Relevant log output

Operating system

Install method

Network connection

Camera make and model

Any other information that may be helpful

Replies: 2 comments · 3 replies

hawkeye217 Jun 14, 2024 Collaborator

ondrejmo Jun 14, 2024 Author

hawkeye217 Jun 14, 2024 Collaborator

JSkye3293 Jun 30, 2024

Docker compose

config.yml

Latest Log

NickM-27 Jun 14, 2024 Collaborator Sponsor

ondrejmo
Jun 14, 2024

Replies: 2 comments 3 replies

hawkeye217
Jun 14, 2024
Collaborator

ondrejmo Jun 14, 2024
Author

hawkeye217 Jun 14, 2024
Collaborator

NickM-27
Jun 14, 2024
Collaborator Sponsor