mirror of
https://github.com/blakeblackshear/frigate.git
synced 2026-07-14 16:01:13 +03:00
NVR with realtime local object detection for IP cameras
aicameragoogle-coralhome-assistanthome-automationhomeautomationmqttnvrobject-detectionrealtimertsptensorflow
25b1db3118
joserfc 1.x requires symmetric-algorithm keys to be `OctKey` instances
rather than raw strings. Since `requirements-wheels.txt` pins
`joserfc == 1.2.*`, every call to `create_encoded_jwt()` currently raises
`joserfc.errors.MissingKeyError` at `jwt.encode`, which nginx surfaces as
`500 Internal Server Error` on `POST /api/login`. The symmetric-verify
path in `is_logged_in_without_redirect` has the same problem on
`jwt.decode`.
Reproduction
docker exec <container> pip show joserfc # 1.2.2
curl -X POST -H 'Content-Type: application/json' \
-d '{"user":"<valid-user>","password":"<valid-pw>"}' \
http://<frigate>:5000/api/login
# -> 500 Internal Server Error
# log shows: joserfc.errors.MissingKeyError: missing_key
Minimal repro inside the container:
python3 -c "
from joserfc import jwt
jwt.encode({'alg':'HS256'}, {'sub':'t','exp':0}, 'some-secret')
"
# ValueError: Invalid key
python3 -c "
from joserfc import jwt
from joserfc.jwk import OctKey
print(jwt.encode({'alg':'HS256'}, {'sub':'t','exp':0},
OctKey.import_key('some-secret'))[:40])
"
# eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9...
The Home Assistant Frigate integration trips this path on every
configuration attempt because it always does `POST /api/login` with the
credentials supplied in the HA config flow, producing a confusing
"failed to connect" symptom rather than an auth error.
Fix
Wrap the secret with `OctKey.import_key(...)` at the two sites that call
into `joserfc.jwt`. The stored secret file format and everything else
stays the same; `get_jwt_secret()` continues to return a string.
AI disclosure
AI-assisted. I reviewed and tested the change end-to-end against a live
Frigate 0.17.1 container running joserfc 1.2.2: reproduced the 500 via
Home Assistant, identified the stack (auth.py line 366 in 0.17.1 / 404
on dev, and the decode call on 680), verified `OctKey.import_key(str)`
accepts the existing secret format, applied the patch in-container,
restarted, and confirmed `POST /api/login` now returns a clean
`401 {"message":"Login failed"}` for bad credentials and issues a valid
JWT cookie for good credentials. No new dependencies; `OctKey` is part
of `joserfc` which is already pinned.
|
||
|---|---|---|
| .cspell | ||
| .cursor/rules | ||
| .devcontainer | ||
| .github | ||
| .vscode | ||
| config | ||
| docker | ||
| docs | ||
| frigate | ||
| migrations | ||
| notebooks | ||
| web | ||
| .dockerignore | ||
| .gitignore | ||
| .pylintrc | ||
| audio-labelmap.txt | ||
| benchmark_motion.py | ||
| benchmark.py | ||
| CODEOWNERS | ||
| CONTRIBUTING.md | ||
| cspell.json | ||
| docker-compose.yml | ||
| generate_config_translations.py | ||
| labelmap.txt | ||
| LICENSE | ||
| Makefile | ||
| netlify.toml | ||
| package-lock.json | ||
| process_clip.py | ||
| pyproject.toml | ||
| README_CN.md | ||
| README.md | ||
| TRADEMARK.md | ||
Frigate NVR™ - Realtime Object Detection for IP Cameras
EnglishA complete and local NVR designed for Home Assistant with AI object detection. Uses OpenCV and Tensorflow to perform realtime object detection locally for IP cameras.
Use of a GPU or AI accelerator is highly recommended. AI accelerators will outperform even the best CPUs with very little overhead. See Frigate's supported object detectors.
- Tight integration with Home Assistant via a custom component
- Designed to minimize resource use and maximize performance by only looking for objects when and where it is necessary
- Leverages multiprocessing heavily with an emphasis on realtime over processing every frame
- Uses a very low overhead motion detection to determine where to run object detection
- Object detection with TensorFlow runs in separate processes for maximum FPS
- Communicates over MQTT for easy integration into other systems
- Records video with retention settings based on detected objects
- 24/7 recording
- Re-streaming via RTSP to reduce the number of connections to your camera
- WebRTC & MSE support for low-latency live view
Documentation
View the documentation at https://docs.frigate.video
Donations
If you would like to make a donation to support development, please use Github Sponsors.
License
This project is licensed under the MIT License.
- Code: The source code, configuration files, and documentation in this repository are available under the MIT License. You are free to use, modify, and distribute the code as long as you include the original copyright notice.
- Trademarks: The "Frigate" name, the "Frigate NVR" brand, and the Frigate logo are trademarks of Frigate, Inc. and are not covered by the MIT License.
Please see our Trademark Policy for details on acceptable use of our brand assets.
Screenshots
Live dashboard
Streamlined review workflow
Multi-camera scrubbing
Built-in mask and zone editor
Translations
We use Weblate to support language translations. Contributions are always welcome.
Copyright © 2026 Frigate, Inc.