You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What did you do?
I tried to deploy postgres-exporter to connect to my postgres db.
What did you expect to see?
I expected to connect with that password also I tried to change { to %7D but didn't work too.
I used this environment for password POSTGRES_PASSWORD.
And for solving that problem I changed my postgres password and then It authenticated successfully.
Also I guess this problem is about when you want create DATA_SOURCE_NAME by merging these environment togethere: DATA_SOURCE_URI and DATA_SOURCE_USER and DATA_SOURCE_PASSWORD .
What did you see instead? Under which circumstances?
It didn't connect and I faced to that log I sent.
postgres_exporter version:
postgres-exporter:v0.15.0
PostgreSQL version:
15.3
Logs:
postgres_exporter | ts=2024-09-07T13:55:48.449Z caller=collector.go:176 level=error msg="Error opening connection to database" err="error querying postgresql version: pq: password authentication failed for user \"postgres\""
I like to work on this bug and contribute to this project but I don't know from where I should search for this bug, maybe I need some help about it.
The text was updated successfully, but these errors were encountered:
aaii-z
changed the title
If my password contains '{
If my password contains '{' or '}' it can't authenticate
Sep 7, 2024
What did you do?
I tried to deploy postgres-exporter to connect to my postgres db.
What did you expect to see?
I expected to connect with that password also I tried to change { to %7D but didn't work too.
I used this environment for password POSTGRES_PASSWORD.
And for solving that problem I changed my postgres password and then It authenticated successfully.
What did you see instead? Under which circumstances?
It didn't connect and I faced to that log I sent.
postgres_exporter version:
postgres-exporter:v0.15.0
PostgreSQL version:
15.3
Logs:
I like to work on this bug and contribute to this project but I don't know from where I should search for this bug, maybe I need some help about it.
The text was updated successfully, but these errors were encountered: