"Wrong credentials" means that pgAdmin successfully connected to the Postgresql server. OP just couldn't log in.
On 11/21/22 01:38, Holger Jakobs wrote:
Hi Frank
Using pgAdmin is generally fine, but not helpful in case you're trying to find an error regarding connecting to the server.
Be aware that the pgAdmin mailing list isn't this one. pgAdmin is a different project.
Try to connect using psql, which is the only "official" frontend.
Watch out for the setting listen_addresses in postgresql.conf and appropriate entries in pg_hba.conf, as without correct values there no connection is possible. Often, listen_addresses doesn't allow remote connections with the default setting.
If you are connecting with pgAdmin from the same machine (NOT via TCP/IP), then you can use a local socket (AF_UNIX) and enter the path of the socket files instead of the IP address or the name of the server. pgAdmin can handle this, as psql, but DBeaver for instance cannot.
Best Regards,
Holger
Am 20.11.22 um 19:59 schrieb Frank Rueter:
Hi,
I have to install postgres on my QNAP TVS-1271U-RP but am no pro, so hopefully this is an easy beginners mistake:
via DockerStation on the QNAP I installed postgres and pgadmin via this docker compose
the only thing I changed in the process was the POSTGRES_PASSWORD in the yml.
after successful install I went to pgadmin, clicked "add new server" and entered the server's ip address along with the POSTGRES_USER and POSTGRES_PASSWORD values from the yml file.
However, pgadmin says that those are the wrong user credentials.
I logged into the docker terminal for my docker container and checked the environment which confirms the above values are indeed correct.
I used to have this running once in the past but decided to uninstall everything and start from scratch for several reasons. After several hours of trying I just cannot figure out what I am missing to get this going.
If someone would be able to assist with this, that would be amazing.
