Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

error connecting to DB #1937

Closed
marcvandecoevering opened this issue Jul 12, 2024 · 9 comments
Closed

error connecting to DB #1937

marcvandecoevering opened this issue Jul 12, 2024 · 9 comments
Labels
question Further information is requested

Comments

@marcvandecoevering
Copy link

marcvandecoevering commented Jul 12, 2024

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.

Listmonk_DB-LOGS
Listmonk_DB-LOGS

DockerCompose-Logs
DockerCompose-Logs

DockerCompose-File
DockerCompose-File

@marcvandecoevering marcvandecoevering added the question Further information is requested label Jul 12, 2024
@marcvandecoevering
Copy link
Author

I just hope i'm missing a simple thing.

@MaximilianKohler
Copy link
Contributor

MaximilianKohler commented Jul 13, 2024

@marcvandecoevering
Copy link
Author

How could that be? It was running via terminal. Just locally.

@MaximilianKohler
Copy link
Contributor

Docker interacts with the firewall differently. Did you check the 21 link?

@marcvandecoevering
Copy link
Author

marcvandecoevering commented Jul 15, 2024

I did; cant figure out what is left for me to do.
I even added this in my pg_hba.conf file.

--log

I might not be totally sure what to look for.

@lmmendes
Copy link
Contributor

@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

@marcvandecoevering
Copy link
Author

marcvandecoevering commented Jul 19, 2024

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.
Config toml

I have zero old databases or volumes left right now.
350421758-b6045f93-1e0f-4a0d-9887-ce1e9769cb2f

The commands find nothing.
350422356-b83e3653-823d-412c-bc0c-eb1d89196df3

@MaximilianKohler
Copy link
Contributor

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.

@H0BB5
Copy link

H0BB5 commented Jul 25, 2024

What does docker ps return?
What about docker networks ls / docker networks inspect listmonk/[xyz]

Seems possibly related to:

  1. Firewall
  2. Your nginx/web server config on your host with your docker containers (check container ip)
  3. Docker containers might not be open / wrong ports

@knadh knadh closed this as completed Sep 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

5 participants