Turns out the docker compose install ignores the custom password in the yml file during install and always uses the default one regardless.
On Mon, Nov 21, 2022 at 5:55 PM Ashesh Vashi <ashesh.va...@enterprisedb.com> wrote: > On Mon, Nov 21, 2022 at 12:44 AM Frank Rueter <fr...@ohufx.com> wrote: > >> 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 <https://github.com/khezen/compose-postgres> >> - 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. >> >> It is difficult to guess from this message what could be the issue. > To start with - you can check the pg_hba.conf > <https://www.postgresql.org/docs/current/auth-pg-hba-conf.html> and > listen_address > <https://www.postgresql.org/docs/current/runtime-config-connection.html> > of PostgreSQL to allow connection from the pgAdmin docker. > > -- Ashesh > >> >> - 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. >> >> Cheers, >> frank >> >
