-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Beta 2 authentication #11957
-
Describe the problem you are havingThe authentication can be bypassed / does not work. I enabled it using Steps to reproduce
Version0.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:https://{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 outputOperating systemUbuntu 22.04 server Install methodKubernetes Network connectionWired Camera make and modeldoes not matter Any other information that may be helpfulNo response |
Beta Was this translation helpful? Give feedback.
All reactions
Replies: 2 comments · 3 replies
-
What port are you using? Authentication is available on port 8080 as the docs indicate. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Thanks for the swift answer, could please point me to the particular part of documentation where this is explained? |
Beta Was this translation helpful? Give feedback.
All reactions
-
https://deploy-preview-11419--frigate-docs.netlify.app/configuration/authentication/ |
Beta Was this translation helpful? Give feedback.
All reactions
-
👍 1
-
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. Here is both my docker compose and Config, with the latest log that I have. Thanks! Docker compose
config.yml
Latest Log
|
Beta Was this translation helpful? Give feedback.
All reactions
-
What is your docker compose? Sounds like you're using port 5000 for access which, as the docs explain, is unauthenticated |
Beta Was this translation helpful? Give feedback.
What port are you using? Authentication is available on port 8080 as the docs indicate.