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
Describe the bug
I am using pgadmin4 chart version 1.15.2.
Helm version: 3.10.1.
Kubernetes version: 1.25.
In my configuration I am using pgpassfile. It works for connect to any databases. But if I am trying to do backup database via context menu in UI, I get the error:
Backing up an object on the server 'someServer1 (someHost1:5432)' from database 'someDb1'
Running command:
/usr/local/pgsql-14/pg_dump --file "/var/lib/pgadmin/storage/pgadmin123/test" --host "someHost1" --port "5432" --username "someUser1" --no-password --verbose --role "someUser1" --format=c --blobs "someDb1"
My values seems like that (I am using pgadmin4 via dependency):
If I do this without pgpassfile, backup is successful.
Also this problem occurs when I'm trying to execute script (for example, materialized view) via context menu. I am getting the error:
psql: error: connection to server at "someHost1" (someIP1), port 5432 failed: fe_sendauth: no password supplied.
Looks like this is a problem with all commands that using psql. Psql is not seeing passwords from pgpassfile and return the errors.
The text was updated successfully, but these errors were encountered:
Describe the bug
I am using pgadmin4 chart version 1.15.2.
Helm version: 3.10.1.
Kubernetes version: 1.25.
In my configuration I am using pgpassfile. It works for connect to any databases. But if I am trying to do backup database via context menu in UI, I get the error:
My values seems like that (I am using pgadmin4 via dependency):
If I do this without pgpassfile, backup is successful.
Also this problem occurs when I'm trying to execute script (for example, materialized view) via context menu. I am getting the error:
Looks like this is a problem with all commands that using psql. Psql is not seeing passwords from pgpassfile and return the errors.
The text was updated successfully, but these errors were encountered: