[Support]: Unable to use Faces UI to add a new face. #20416

iambenmitchell · 2025-10-10T17:07:43Z

iambenmitchell
Oct 10, 2025

Checklist

I have updated to the latest available Frigate version.
I have cleared the cache of my browser.
I have tried a different browser to see if it is related to my browser.
I have tried reproducing the issue in incognito mode to rule out problems with any third party extensions or plugins I have installed.
I have asked the AI at https://docs.frigate.video about my issue.

Describe the problem you are having

This is a new install of frigate, I am trying out the features and want to try the face detection. I have enabled it in the config, restarted frigate but when I navigate to the faces page in the WebUI, click add face, enter a name and then upload a picture... the WebUI hangs as soon as I press "Next" after selecting the photo.

Frigate doesn't completely crash, the docker eventually reports it as unhealthy but the web server responds to requests.. I just displays a blank screen. If I reload the faces UI, the loading circle spins indefinitely. If I try to edit the config via the web, the config doesn't load. The entire thing just completely hangs and there are no logs in the docker log.

Steps to reproduce

Enable Face detection in config.
Navigate to Faces in the webui
Click on "Add Face"
Enter the name
Select a photo
Press "Next"
Notice frigate hangs/crashes

Version

0.16.1-e664cb2

In which browser(s) are you experiencing the issue with?

Safari 21622.1.22.11.15, Chrome 141.0.7390.66

Frigate config file

mqtt:
  enabled: false

telemetry:
  # Optional: Configure system stats
  stats:
    # Optional: Enable Intel GPU stats (default: shown below)
    intel_gpu_stats: true
  version_check: true

ffmpeg:
  hwaccel_args: preset-intel-qsv-h265

semantic_search:
  enabled: True
  model: "jinav1"
  model_size: small

face_recognition:
  enabled: true
  model_size: small

lpr:
  enabled: True
  device: GPU
  known_plates:
    Tesla:
      - "XXXXX"
    MINI:
      - "XXXXXX"

detectors:
  ov:
    type: openvino
    device: GPU

model:
  model_type: yolo-generic
  width: 640 # <--- should match the imgsize set during model export
  height: 640 # <--- should match the imgsize set during model export
  input_tensor: nchw
  input_dtype: float
  path: /config/model_cache/yolov9-m-640.onnx
  labelmap_path: /labelmap/coco-80.txt

cameras:
  name_of_your_camera: # <------ Name the camera
    enabled: false
    ffmpeg:
      inputs:
        - path: rtsp://10.0.10.10:554/rtsp # <----- 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
detect:
  enabled: true
version: 0.16-0

docker-compose file or Docker CLI command

services:
  frigate:
    container_name: frigate
    privileged: true # this may not be necessary for all setups
    restart: always
    cap_add:
      - CAP_PERFMON
    stop_grace_period: 30s # allow enough time to shut down the various services
    image: ghcr.io/blakeblackshear/frigate:stable
    shm_size: "2gb" # update for your cameras based on calculation above
    devices:
      - /dev/dri:/dev/dri # For intel hwaccel, needs to be updated for your hardware
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /mnt/Lambo/Docker-Configs/Frigate/config:/config
      - /mnt/Lambo/Docker-Configs/Frigate/storage:/media/frigate
      - type: tmpfs # Optional: 1GB of memory, reduces SSD/SD Card wear
        target: /tmp/cache
        tmpfs:
          size: 1000000000
    networks:
      lan_net:
        ipv4_address: 192.168.20.28
        ipv6_address: xxxx::28
    environment:
      FRIGATE_RTSP_PASSWORD: "xxxx"

networks:
  lan_net:
    name: lan_net
    external: true

Relevant Frigate log output

2025-10-10 17:56:17.550421200  [INFO] Starting go2rtc healthcheck service...
2025-10-10 17:56:17.761895969  192.168.1.117 - - [10/Oct/2025:17:56:17 +0100] "GET /api/config HTTP/1.1" 200 12384 "https://192.168.20.28:8971/faces" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/26.0.1 Safari/605.1.15" "-"
2025-10-10 17:56:17.761906323  192.168.1.117 - - [10/Oct/2025:17:56:17 +0100] "GET /api/profile HTTP/1.1" 200 35 "https://192.168.20.28:8971/faces" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/26.0.1 Safari/605.1.15" "-"
2025-10-10 17:56:17.761992310  192.168.1.117 - - [10/Oct/2025:17:56:17 +0100] "GET /api/event_ids?ids= HTTP/1.1" 200 2 "https://192.168.20.28:8971/faces" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/26.0.1 Safari/605.1.15" "-"
2025-10-10 17:56:17.762475330  192.168.1.117 - - [10/Oct/2025:17:56:17 +0100] "GET /api/faces HTTP/1.1" 200 2 "https://192.168.20.28:8971/faces" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/26.0.1 Safari/605.1.15" "-"
2025-10-10 17:56:19.021043513  192.168.1.117 - - [10/Oct/2025:17:56:19 +0100] "GET /fonts/Inter-SemiBold.woff2 HTTP/1.1" 200 111588 "https://192.168.20.28:8971/faces" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/26.0.1 Safari/605.1.15" "-"
2025-10-10 17:56:19.021088735  192.168.1.117 - - [10/Oct/2025:17:56:19 +0100] "GET /fonts/Inter-Bold.woff2 HTTP/1.1" 200 111040 "https://192.168.20.28:8971/faces" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/26.0.1 Safari/605.1.15" "-"
2025-10-10 17:56:29.946947671  192.168.1.117 - - [10/Oct/2025:17:56:29 +0100] "GET /api/config HTTP/1.1" 200 12384 "https://192.168.20.28:8971/faces" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/26.0.1 Safari/605.1.15" "-"
2025-10-10 17:56:29.946963124  192.168.1.117 - - [10/Oct/2025:17:56:29 +0100] "GET /api/profile HTTP/1.1" 200 35 "https://192.168.20.28:8971/faces" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/26.0.1 Safari/605.1.15" "-"
2025-10-10 17:56:29.947375778  192.168.1.117 - - [10/Oct/2025:17:56:29 +0100] "GET /api/faces HTTP/1.1" 200 2 "https://192.168.20.28:8971/faces" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/26.0.1 Safari/605.1.15" "-"
2025-10-10 17:56:29.947586799  192.168.1.117 - - [10/Oct/2025:17:56:29 +0100] "GET /api/event_ids?ids= HTTP/1.1" 200 2 "https://192.168.20.28:8971/faces" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/26.0.1 Safari/605.1.15" "-"
2025-10-10 17:56:30.564147067  2025/10/10 17:56:30 [warn] 206#206: *25 a client request body is buffered to a temporary file /usr/local/nginx/client_body_temp/0000000017 while sending to client, client: 192.168.1.117, server: , request: "POST /api/faces/Ben/register HTTP/1.1", host: "192.168.20.28:8971", referrer: "https://192.168.20.28:8971/faces"
2025-10-10 17:56:45.677563754  192.168.1.117 - - [10/Oct/2025:17:56:45 +0100] "GET /api/config HTTP/1.1" 499 0 "https://192.168.20.28:8971/faces" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/26.0.1 Safari/605.1.15" "-"
2025-10-10 17:56:45.677706230  192.168.1.117 - - [10/Oct/2025:17:56:45 +0100] "GET /api/profile HTTP/1.1" 499 0 "https://192.168.20.28:8971/faces" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/26.0.1 Safari/605.1.15" "-"
2025-10-10 17:56:45.677715934  192.168.1.117 - - [10/Oct/2025:17:56:45 +0100] "GET /api/faces HTTP/1.1" 499 0 "https://192.168.20.28:8971/faces" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/26.0.1 Safari/605.1.15" "-"
2025-10-10 17:56:45.677897178  192.168.1.117 - - [10/Oct/2025:17:56:45 +0100] "POST /api/faces/Ben/register HTTP/1.1" 499 0 "https://192.168.20.28:8971/faces" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/26.0.1 Safari/605.1.15" "-"
2025-10-10 17:56:45.678094114  192.168.1.117 - - [10/Oct/2025:17:56:45 +0100] "GET /api/event_ids?ids= HTTP/1.1" 499 0 "https://192.168.20.28:8971/faces" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/26.0.1 Safari/605.1.15" "-"
2025-10-10 17:56:45.712219267  192.168.1.117 - - [10/Oct/2025:17:56:45 +0100] "GET /faces HTTP/1.1" 200 2649 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/26.0.1 Safari/605.1.15" "-"
2025-10-10 17:56:45.719372865  192.168.1.117 - - [10/Oct/2025:17:56:45 +0100] "GET /ws HTTP/1.1" 101 10674 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/26.0.1 Safari/605.1.15" "-"
2025-10-10 17:56:45.742189015  192.168.1.117 - - [10/Oct/2025:17:56:45 +0100] "GET /fonts/Inter-Regular.woff2 HTTP/1.1" 200 108488 "https://192.168.20.28:8971/faces" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/26.0.1 Safari/605.1.15" "-"
s6-rc: info: service s6rc-fdholder: starting
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started

Relevant go2rtc log output

n/a

Operating system

Other Linux

Install method

Docker Compose

Network connection

Wired

Camera make and model

N/A

Screenshots of the Frigate UI's System metrics pages

Any other information that may be helpful

I have cameras arriving soon, will be using reolink POE cameras. Right now no camera is setup, I am just trying stuff out.

I have found discussions on Facebook talking about the issue, but I am unable to comment as I do not have a Facebook account.

NickM-27 · 2025-10-10T17:12:22Z

NickM-27
Oct 10, 2025
Collaborator Sponsor

We've seen a few reports of this, they were usually caused by an issue with the folder / permissions or a browser issue.

One user has permission issues meaning nginx couldn't write the face image inside of /media/frigate.

I'd suggest double checking that, and trying other browser.

11 replies

NickM-27 Oct 10, 2025
Collaborator Sponsor

No, for a workaround though you can just crop an image to the face and put it into the folder.

iambenmitchell Oct 10, 2025
Author

the storage/clips/faces directory right?

Do I need to create a directory for the name of the person and put the relevant photos there, or do I just throw the raw crops into the storage/clips/faces ?

NickM-27 Oct 10, 2025
Collaborator Sponsor

You need to create the names folder. That should be done first by the UI upload, which might indicate the problem.

iambenmitchell Oct 10, 2025
Author

I have manually created a folder inside faces called BenM and have uploaded 7 png files of my face cropped.

Can confirm they now show up in Train

iambenmitchell Oct 10, 2025
Author

If I view BenM in the webUI and add a new photo with the upload image button, it crashes like before.

This might hint at what the issue is?

neekz0r · 2025-11-12T00:18:51Z

neekz0r
Nov 12, 2025

I too am seeing this, and I have checked my permissions (777 for the folder). What is interesting is this throws frigate into an unresponsive state. Unresponsive here means that after getting this error, nothing on the frigate side loads.

Nginx reports outputs this log (in addition to the one posted above: *245 a client request body is buffered to a temporary file /usr/local/nginx/client_body_temp/0000000054 while sending to client)

2025-11-12 00:09:12.761530594 2025/11/12 00:09:12 [error] 218#218: *333 auth request unexpected status: 504 while sending to client, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", host: "127.0.0.1:5000"
This leads me to believe that it is likely an issue on the frigate side, not the nginx side. No file is written that I can see.
I have checked the usual things; enough disk space, enough inodes, etc. I have done this both for the temporary location that the error complains about and the faces folder where I expect the images to be loaded. (not that this is overly helpful, but the docker container is responsive -- I can exec /bin/bash and things seem to be present.

You can see from this ps within the container that the call to version is failing -- which I presume is some form of health check.

root        2213  0.0  0.0  19564  8972 ?        S    00:14   0:00 curl --fail --silent --show-error http://127.0.0.1:5000/api/version
root        2342  0.0  0.0  19564  9000 ?        S    00:14   0:00 curl --fail --silent --show-error http://127.0.0.1:5000/api/version
root        2465  0.0  0.0  19564  8932 ?        S    00:15   0:00 curl --fail --silent --show-error http://127.0.0.1:5000/api/version
root        2598  0.0  0.0  19564  9008 ?        S    00:15   0:00 curl --fail --silent --show-error http://127.0.0.1:5000/api/version
root        2727  0.0  0.0  19564  8996 ?        S    00:15   0:00 curl --fail --silent --show-error http://127.0.0.1:5000/api/version
root        2850  0.0  0.0  19564  9112 ?        S    00:16   0:00 curl --fail --silent --show-error http://127.0.0.1:5000/api/version
root        2973  0.0  0.0  19564  9072 ?        S    00:16   0:00 curl --fail --silent --show-error http://127.0.0.1:5000/api/version
root        3104  0.0  0.0  19564  8952 ?        S    00:16   0:00 curl --fail --silent --show-error http://127.0.0.1:5000/api/version
root        3227  0.0  0.0  19564  9116 ?        S    00:17   0:00 curl --fail --silent --show-error http://127.0.0.1:5000/api/version
root        3350  0.0  0.0  19564  8984 ?        S    00:17   0:00 curl --fail --silent --show-error http://127.0.0.1:5000/api/version

I am using frigate:stable-rocm docker image, and this was done with firefox 145.0 (64-bit), the latest at time of writing.

Happy to provide more in depth if needed.

1 reply

NickM-27 Nov 12, 2025
Collaborator Sponsor

This is an odd issue as we can't reproduce, with that said things have been refactored in 0.17 so this may be fixed, and if nothing else there are more debug logs which would potentially help better understand what is going on

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

[Support]: Unable to use Faces UI to add a new face. #20416

Uh oh!

{{title}}

Uh oh!

Replies: 2 comments 12 replies

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Uh oh!

[Support]: Unable to use Faces UI to add a new face. #20416

Uh oh!

iambenmitchell Oct 10, 2025

Checklist

Describe the problem you are having

Steps to reproduce

Version

In which browser(s) are you experiencing the issue with?

Frigate config file

docker-compose file or Docker CLI command

Relevant Frigate log output

Relevant go2rtc log output

Operating system

Install method

Network connection

Camera make and model

Screenshots of the Frigate UI's System metrics pages

Any other information that may be helpful

Replies: 2 comments · 12 replies

Uh oh!

NickM-27 Oct 10, 2025 Collaborator Sponsor

Uh oh!

NickM-27 Oct 10, 2025 Collaborator Sponsor

Uh oh!

iambenmitchell Oct 10, 2025 Author

Uh oh!

NickM-27 Oct 10, 2025 Collaborator Sponsor

Uh oh!

iambenmitchell Oct 10, 2025 Author

Uh oh!

iambenmitchell Oct 10, 2025 Author

Uh oh!

neekz0r Nov 12, 2025

Uh oh!

NickM-27 Nov 12, 2025 Collaborator Sponsor

iambenmitchell
Oct 10, 2025

Replies: 2 comments 12 replies

NickM-27
Oct 10, 2025
Collaborator Sponsor

NickM-27 Oct 10, 2025
Collaborator Sponsor

iambenmitchell Oct 10, 2025
Author

NickM-27 Oct 10, 2025
Collaborator Sponsor

iambenmitchell Oct 10, 2025
Author

iambenmitchell Oct 10, 2025
Author

neekz0r
Nov 12, 2025

NickM-27 Nov 12, 2025
Collaborator Sponsor