[Config Support]: Error saving config with plus model #20054
-
Describe the problem you are havingPython error when saving config with Frigate+ and plus model. Your configuration is invalid. Traceback (most recent call last): Version0.16.1-e664cb2 Frigate config filedatabase:
path: /data/db/frigate.db
detectors:
hailo8l:
type: hailo8l
device: PCIe
model:
path: plus://b0a742c132a6f96f86cfe08942a11182
ffmpeg:
hwaccel_args: preset-rpi-64-h264
telemetry:
stats:
network_bandwidth: trueRelevant Frigate log outputunknown | 2025-09-13 09:20:15 | unknown | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
unknown | 2025-09-13 09:20:15 | unknown | File "/opt/frigate/frigate/plus.py", line 81, in _get_authorization_header
unknown | 2025-09-13 09:20:15 | unknown | self._refresh_token_if_needed()
unknown | 2025-09-13 09:20:15 | unknown | File "/opt/frigate/frigate/plus.py", line 77, in _refresh_token_if_needed
unknown | 2025-09-13 09:20:15 | unknown | raise Exception(f"Unable to refresh API token: {r.text}")
unknown | 2025-09-13 09:20:15 | unknown | Exception: Unable to refresh API token: {"message":"Incorrect api key for user"}Relevant go2rtc log outputN/AFrigate statsNo response Operating systemDebian Install methodDocker Compose docker-compose file or Docker CLI commandservices:
frigate-hailo:
container_name: frigate-hailo
privileged: true
restart: unless-stopped
image: ghcr.io/blakeblackshear/frigate:0.16.1
shm_size: 1024mb
devices:
- /dev/hailo0:/dev/hailo0
environment:
- PLUS_API_KEY="97883ec5-****-****-****-27ef15b9c7bd:6***b"
volumes:
- /etc/localtime:/etc/localtime:ro
- ./config/:/config
- ./data/db/:/data/db
- ./data/storage:/media/frigate
- type: tmpfs
target: /tmp/cache
tmpfs:
size: 1g
ports:
- 5000:5000
- 8554:8554
- 8555:8555
- 1984:1984Object DetectorOther Screenshots of the Frigate UI's System metrics pagesNo response Any other information that may be helpfulFrigate+ Settings |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 4 replies
-
|
The error "Unable to refresh API token: {"message":"Incorrect api key for user"}" indicates your Frigate+ API key is invalid or has been revoked(1). To resolve this issue:
Your docker-compose configuration looks correct with the environment variable set: environment:
- PLUS_API_KEY="97883ec5-****-****-****-27ef15b9c7bd:6***b"
model:
path: plus://<your_model_id> Model IDs are not secret values and can be shared freely - access to your model is protected by your API key(2), (3). After regenerating and updating your API key, restart your Frigate container. The model will be downloaded into the 📚 Sources: Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
-
|
I have regenerated the API key, no difference. |
Beta Was this translation helpful? Give feedback.
-
|
Not sure why this would be the case, maybe @blakeblackshear has an idea |
Beta Was this translation helpful? Give feedback.
-
|
The Frigate UI only validates that your API key is formatted correctly. It doesn't actually validate it with the server. In every case I have seen so far, this has always been that you are using an older API key. Each time you generate a key, it invalidates any older ones. Also, make sure you have actually run "docker compose up -d" after changing it again. Restarting the container and/or the machine does not apply changes in your compose file. |
Beta Was this translation helpful? Give feedback.
-
|
Also, be sure you haven't also set an API key in your Frigate config file. |
Beta Was this translation helpful? Give feedback.
-
|
The API key was already set correctly, docker compose up -d allowed to update the config with the model in the correct place (root level), before that the config would not allow saving. |
Beta Was this translation helpful? Give feedback.
-
|
Frigate is now starting almost cleanly, except these warnings. 2025-09-13 16:38:25.554059588 [INFO] Starting Frigate... |
Beta Was this translation helpful? Give feedback.
-
|
Those are normal, looks like it's resolved. |
Beta Was this translation helpful? Give feedback.
The Frigate UI only validates that your API key is formatted correctly. It doesn't actually validate it with the server. In every case I have seen so far, this has always been that you are using an older API key. Each time you generate a key, it invalidates any older ones. Also, make sure you have actually run "docker compose up -d" after changing it again. Restarting the container and/or the machine does not apply changes in your compose file.