-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not able to connect to DB #7
Comments
Hi! Sometimes plugin fails to correctly parse config files and secrets. Please try specifying connection string |
Hi - I tried this also at the time but had the same result: I tried it again with the latest version of the add-on and I get the below URI malformed error. Just to confirm I entered the connection string in the addon config as below and it's exactly how I have it in my HA configuration which looks the same as you mentioned: One thought - could it be an issue with special characters in the password? I do use non-alphanumeric characters. I dont want to go playing with the passwords at that level on my main instance, so when I get a moment I may spin up another test instance to check with a simple password.
|
Yeah, it looks like you are right - connection string should be a proper URL, and if it's not encoded,then parsing it as URL with fail, for example like in typeorm/typeorm#3716 So special chars like Seems like HA itself somehow works around this case, but it doesn't seem trivial. For example, if your connection string is
And it can be even
x_x |
Thanks for coming back to me with the info and suggestion. I can confirm that special characters in the password is exactly the issue. Thanks |
Hi,
I have a similar issue to that mentioned in: #4
I am on HA ersion 2024.07.4
And using V0.5.8 of the addon.
I am using maria DB with the recorder url:
Extract of the logs:
In my configuration.yaml i am referencing the recorder settings using a secret:
Relevant content of the secrets.yaml:
Is this a supported method or am I doing someting wrong here?
Thanks
The text was updated successfully, but these errors were encountered: