Open marcvandecoevering opened 1 month ago
I just hope i'm missing a simple thing.
How could that be? It was running via terminal. Just locally.
Docker interacts with the firewall differently. Did you check the 21 link?
I did; cant figure out what is left for me to do. I even added this in my pg_hba.conf file.
I might not be totally sure what to look for.
@marcvandecoevering have you tried to delete the entire "docker compose" deployment and deploy it again? The first thing that comes to my mind would be have you had another username, password or database configured in the past, before this run?
Check if the username and password for the database match in config.toml
match one that you have in the docker-compose.yml
.
The command bellow will destroy your database and start over a new one:
docker compose rm demo-app demo-db
docker compose up demo-app demo-db
This is my config.toml which is connected. The password/username matches with my docker compose file in the 'docker compose' which i have installed on Unraid.
I have zero old databases or volumes left right now.
The commands find nothing.
The commands find nothing.
I'm unsure what your level of expertise is. Usually that happens when you don't cd
to the location of the config.toml before running the commands. But you seem to know what you're doing. If you're a novice I'd suggest looking through the tutorials in the docs.
What does docker ps
return?
What about docker networks ls
/ docker networks inspect listmonk/[xyz]
Seems possibly related to:
Hello everyone, i had listmonk running a few days ago - i installed it via terminal and LOVED it. I deleted the whole installation / folders / volumes etc.
Now i want to install Listmonk via Docker Compose for easier restarting etc. Im getting stuck at the database connection after starting up via docker compose.
Does anyone have a clue? I've tried everything - i believe.