[Config Support]: How to handle special characters (e.g "@") in RTSP passwords? #14454
Unanswered
victorhooi
asked this question in
Config Support
Replies: 1 comment
-
in general the best way to handle this would be use to url encoded special characters, I don't believe anything has changed here with Frigate and many of my cameras with |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Describe the problem you are having
I'm on the "develop" branch for Frigate.
Recently (~ 2-3 weeks), an upgrade (or something else that happened to occur at a similar time) has broken the RTSP authentication in Frigate, and they don't seem to be able to connect to the cameras anymore.
My cameras are Axis P3248-LV cameras. The password does contain special characters (*, and @, for example). The cameras are able to be connected with other NVR software (e.g. NX Witness), and
ffprobe
seems to be able to read them as well:Previously, my Frigate config.yaml just had the password as is - and it magically worked.
However, after the breakage - I did try escaping the @ character with a backslash - that didn't seem to work. I've also now tried escaping the entire password string with single quotes (which is the config pasted below) - that doesn't seem to work either.
Does anybody know what might be happening here, or if the behaviour might have changed somehow? Or what is the "correct" way in Frigate to pass a RTSP password with special characters?
Version
0.15.0-2137de3
Frigate config file
Relevant Frigate log output
Relevant go2rtc log output
Frigate stats
No response
Operating system
Debian
Install method
Docker Compose
docker-compose file or Docker CLI command
Object Detector
Coral
Screenshots of the Frigate UI's System metrics pages
No response
Any other information that may be helpful
No response
Beta Was this translation helpful? Give feedback.
All reactions