[Config Support]: Proxy auth_secret Error

[5yNc3d]

Describe the problem you are having

When trying to use Nginx Reverse Proxy manager to disable authentication and add an auth_secret value, I am met with "X-Proxy-Secret header does not match configured secret value". I believe I have confirmed that the correct header is set, shown in the inspect screenshot so I am not sure why this is happening.

I cant tell if this is a bug or if I am doing something wrong, but I have found little information on any issues like this when searching online. I first tested with an actual 64 character key, then simplified the key to "abc" for testing purposes.

Version

0.14.1-f4f3cfa

Frigate config file

logger:
  # Optional: default log level (default: shown below)
  default: debug

auth:
  enabled: False

tls:
  enabled: false

proxy:
  auth_secret: "abc"

mqtt:
  host: 192.168.1.98
  port: 1883
  topic_prefix: frigate
  client_id: frigate
  user: mqtt
  password: mqttuser
  stats_interval: 60

detectors:
  coral:
    type: edgetpu
    device: pci:0

ffmpeg:
  hwaccel_args: preset-nvidia-h265
  output_args:
    record: preset-record-generic-audio-aac

go2rtc:
  log:
     exec: debug

Relevant Frigate log output

2024-12-30 00:17:43.783185307  [2024-12-30 00:17:43] frigate.record.maintainer      DEBUG   : Copied /media/frigate/recordings/2024-12-30/06/front-door/17.29.mp4 in 0.040036916732788086 seconds.
2024-12-30 00:17:43.798731275  [2024-12-30 00:17:43] frigate.record.maintainer      DEBUG   : Copied /media/frigate/recordings/2024-12-30/06/backyard/17.29.mp4 in 0.02733302116394043 seconds.
2024-12-30 00:17:43.800825839  [2024-12-30 00:17:43] peewee.sqliteq                 DEBUG   : received query INSERT INTO "recordings" ("id", "camera", "path", "start_time", "end_time", "duration", "motion", "objects", "dBFS", "segment_size", "regions") VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?), (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)
2024-12-30 00:17:43.800955121  [2024-12-30 00:17:43] peewee                         DEBUG   : ('INSERT INTO "recordings" ("id", "camera", "path", "start_time", "end_time", "duration", "motion", "objects", "dBFS", "segment_size", "regions") VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?), (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)', ['1735539449.0-tbb758', 'front-door', '/media/frigate/recordings/2024-12-30/06/front-door/17.29.mp4', 1735539449.0, 1735539458.983594, 9.98359375, 3, 0, 0, 1.9, 53, '1735539449.0-8ri4cr', 'backyard', '/media/frigate/recordings/2024-12-30/06/backyard/17.29.mp4', 1735539449.0, 1735539458.966797, 9.966796875, 1, 0, 0, 1.9, 1])
2024-12-30 00:17:44.161000808  [2024-12-30 00:17:44] frigate.api.auth               DEBUG   : X-Proxy-Secret header does not match configured secret value
2024-12-30 00:17:44.162136758  [2024-12-30 00:17:44] frigate.api.auth               DEBUG   : X-Proxy-Secret header does not match configured secret value
2024-12-30 00:17:44.163904380  [2024-12-30 00:17:44] frigate.api.auth               DEBUG   : X-Proxy-Secret header does not match configured secret value
2024-12-30 00:17:44.223767533  [2024-12-30 00:17:44] frigate.api.auth               DEBUG   : X-Proxy-Secret header does not match configured secret value

Relevant go2rtc log output

2024-12-30 00:13:56.305946303  [INFO] Preparing new go2rtc config...
2024-12-30 00:13:56.872846955  [INFO] Starting go2rtc...
2024-12-30 00:13:57.048648891  00:13:57.048 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2024-12-30 00:13:57.048657691  00:13:57.048 INF config path=/dev/shm/go2rtc.yaml
2024-12-30 00:13:57.049423395  00:13:57.049 INF [api] listen addr=:1984
2024-12-30 00:13:57.049477385  00:13:57.049 INF [rtsp] listen addr=:8554
2024-12-30 00:13:57.049701027  00:13:57.049 INF [webrtc] listen addr=:8555/tcp
2024-12-30 00:14:06.302508325  [INFO] Starting go2rtc healthcheck service...

Frigate stats

No response

Operating system

Debian

Install method

Docker Compose

docker-compose file or Docker CLI command

services:
  frigate:
    container_name: frigate
    privileged: true
    restart: unless-stopped
    image: ghcr.io/blakeblackshear/frigate:stable
    shm_size: "290mb"
    devices:
      - /dev/apex_0:/dev/apex_0 # passes a PCIe Coral, follow driver instructions here https://coral.ai/docs/m2/get-started/#2a-on-linux
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /home/user/docker/frigate/config.yml:/config/config.yml
      - /mnt/cctv/frigate:/media/frigate
      - /home/user/docker/frigate/config:/config
      - type: tmpfs
        target: /tmp/cache
        tmpfs:
          size: 2000000000
    ports:
      - "5000:5000"
      - "8554:8554" # RTSP feeds
      - "8555:8555/tcp" # WebRTC over tcp
      - "8555:8555/udp" # WebRTC over udp
      - "1984:1984" #go2rtc
      - "8971:8971" #remote access
    environment:
      FRIGATE_RTSP_PASSWORD: "***"
    runtime: nvidia
    deploy:
      resources:
        reservations:
          devices:
            - capabilities: [gpu]

Object Detector

Coral

Screenshots of the Frigate UI's System metrics pages

No response

Any other information that may be helpful

No response

[blakeblackshear]

how are you setting the header?

[5yNc3d]

Thanks for the quick response! I am manually putting it in the conf. The header shows up when I curl -I my url and when I inspect on both firefox and chrome. Even when I cut out authelia and just try to pass the header with no other proxy configurations, it still says the secret value does not match

location / {
    include /snippets/proxy.conf;
    include /snippets/authelia-authrequest.conf;
    add_header X-Proxy-Secret abc always;
    proxy_pass $forward_scheme://$server:$port;
}

user@server:~/home/$ curl -I https://cam.website.com
HTTP/2 302 
date: Mon, 30 Dec 2024 16:52:45 GMT
content-type: text/html
location: https://auth.website.com/?rd=https%3A%2F%2Fcam.website.com%2F&rm=HEAD
x-proxy-secret: abc
cf-cache-status: DYNAMIC
report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v4?s=HzWis%2BHL1OUJFt0CkRvCJRWn9P27JLpwTAWu8q%2FY2tNkpa9k2BoMTrqSY%2FBxemCGV3ERVEcr2%2FOTS3w9%2FqS8fTgTT8vQBMcMDve%2FlCKBJGkYy%2BYV%2BAtE0oL80rdk4rY%3D"}],"group":"cf-nel","max_age":604800}
nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
server: cloudflare
cf-ray: 8fa38ac8e92c2339-ORD
alt-svc: h3=":443"; ma=86400
server-timing: cfL4;desc="?proto=TCP&rtt=9355&min_rtt=8276&rtt_var=2334&sent=6&recv=9&lost=0&retrans=0&sent_bytes=3376&recv_bytes=779&delivery_rate=301258&cwnd=213&unsent_bytes=0&cid=a7cd879b49989f9a&ts=103&x=0"

[chrislawso]

were you able to make any progress on your issue?

[5yNc3d]

I have not I've just been using double authentication but maybe it gets fixed in one of the beta updates