Wrong postgres address after fresh quick install?
When installing either with docker compose and quick install script or with portainer and museum and compose.yml scripts from the github. Postgres always starts but the parameter "host" is probably not loaded.
This is how its in the museum.yml:
db:
host: postgres
port: ...
name: ente_db
user: ...
password: ...
these are the last logs of the museum container:
postgres-1 | 2025-06-20 00:00:38.041 UTC [1] LOG: starting PostgreSQL 15.13 (Debian 15.13-1.pgdg120+1) on aarch64-unknown-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
postgres-1 | 2025-06-20 00:00:38.042 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
postgres-1 | 2025-06-20 00:00:38.042 UTC [1] LOG: listening on IPv6 address "::", port 5432
postgres-1 | 2025-06-20 00:00:38.047 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres-1 | 2025-06-20 00:00:38.062 UTC [82] LOG: database system was shut down at 2025-06-20 00:00:37 UTC
postgres-1 | 2025-06-20 00:00:38.077 UTC [1] LOG: database system is ready to accept connections
museum-1 | INFO[0000]main.go:104 main Booting up local server with commit #026669b0d0b292b482a52b20b1693242f0a605a6
museum-1 | INFO[0000]main.go:842 setupDatabase Setting up db
museum-1 | INFO[0000]main.go:849 setupDatabase Connected to DB
museum-1 | panic: dial tcp [::1]:5432: connect: connection refused museum-1 | museum-1 | goroutine 1 [running]: museum-1 | main.setupDatabase() museum-1 | /etc/ente/cmd/museum/main.go:852 +0x2d8 museum-1 | main.main() museum-1 | /etc/ente/cmd/museum/main.go:124 +0x380 museum-1 exited with code 2 To recreate: get homeassistant os on a raspberry, install compose v2 and try to run quickstart
museum-1 | INFO[0000]main.go:849 setupDatabase Connected to DB
museum-1 | panic: dial tcp [::1]:5432: connect: connection refused museum-1 | museum-1 | goroutine 1 [running]: museum-1 | main.setupDatabase() museum-1 | /etc/ente/cmd/museum/main.go:852 +0x2d8 museum-1 | main.main() museum-1 | /etc/ente/cmd/museum/main.go:124 +0x380 museum-1 exited with code 2 To recreate: get homeassistant os on a raspberry, install compose v2 and try to run quickstart
24 Replies
Remember to use /solved to mark your thread as solved once your question is answered.
Hey are you sure that it's host? I think having stale volumes could also cause this thing
I wish it was but I deleted every volume in docker and checked that the museum.yaml really is where it needs to be mounted from. Still sadly this error in logs:
INFO[0000]main.go:104 main Booting up local server with commit #026669b0d0b292b482a52b20b1693242f0a605a6
INFO[0000]main.go:842 setupDatabase Setting up db
INFO[0000]main.go:849 setupDatabase Connected to DB
panic: dial tcp [::1]:5432: connect: connection refused goroutine 1 [running]: main.setupDatabase() /etc/ente/cmd/museum/main.go:852 +0x2d8 main.main() /etc/ente/cmd/museum/main.go:124 +0x380
INFO[0000]main.go:849 setupDatabase Connected to DB
panic: dial tcp [::1]:5432: connect: connection refused goroutine 1 [running]: main.setupDatabase() /etc/ente/cmd/museum/main.go:852 +0x2d8 main.main() /etc/ente/cmd/museum/main.go:124 +0x380
as you can see the volumes are mapped right as well
sorry for this quick reminder. Im desperate about this error @Keerthana
Thanks for reporting, will look into this
Thank you so much! I look forward to this!! Id be happy to become an ente member as well 😄
Do you think its because somehow the museum config still is not loaded properly?
Can you please check if you can connect to the database via CLI once to see if it's config or the DB's host name itself being incorrect?
How can I connect to the database through the cli? As far as I know the containers share a network and I do not know how to get inside of that network. I have to create a new container with a database connector and put it into this network, right?
Hey, assuming you're using Docker containers for this, you can always do a docker exec -it <container-name> and use psql command with the correct creds to see if you can connect via it, the service name specified in the config will be the one used for hostname too, so try that and let's know : )
I fixed it with this: (on a fresh install - DO NOT RUN ON YOUR PROD)
docker volume rm my-ente_minio-data
via: https://help.ente.io/self-hosting/troubleshooting/docker
"Then the issue is that the password you're using is not the password postgres is expecting (duh), and a potential scenario where that can happen is something like this:
On a machine, you create a new cluster with quickstart.sh.
Later you delete that folder, but then create another cluster with quickstart.sh. Each time quickstart.sh runs, it creates new credentials, and then when it tries to spin up the docker compose cluster, use them to connect to the postgres running within."
Docker Errors | Ente Help
Fixing docker related errors when trying to self host Ente
@Packesl
Exactly, stale volumes are the reason for this.
Thank you @no402 and @Keerthana for your answers but sadly as I said the stale volumes are not the problem here. I already checked that I have no stale volumes and I did again. Please take a look at my cli history:
From what I inspected, the file's name is museum.yml instead of museum.yaml according to this: https://discord.com/channels/948937918347608085/1386019641503256617/1386019641503256617
But I assume it's museum.yaml, if so, please check if the config's properly mounted once again, I am pretty sure that's the issue
Packesl
When installing either with docker compose and quick install script or with portainer and museum and compose.yml scripts from the github. Postgres always starts but the parameter "host" is probably not loaded.
This is how its in the museum.yml:
db:
host: postgres
port: ...
name: ente_db
user: ...
password: ...
these are the last logs of the museum container:
postgres-1 | 2025-06-20 00:00:38.041 UTC [1] LOG: starting PostgreSQL 15.13 (Debian 15.13-1.pgdg120+1) on aarch64-unknown-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
postgres-1 | 2025-06-20 00:00:38.042 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
postgres-1 | 2025-06-20 00:00:38.042 UTC [1] LOG: listening on IPv6 address "::", port 5432
postgres-1 | 2025-06-20 00:00:38.047 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres-1 | 2025-06-20 00:00:38.062 UTC [82] LOG: database system was shut down at 2025-06-20 00:00:37 UTC
postgres-1 | 2025-06-20 00:00:38.077 UTC [1] LOG: database system is ready to accept connections
museum-1 | INFO[0000]main.go:104 main Booting up local server with commit #026669b0d0b292b482a52b20b1693242f0a605a6
museum-1 | INFO[0000]main.go:842 setupDatabase Setting up db
museum-1 | INFO[0000]main.go:849 setupDatabase Connected to DB
museum-1 | panic: dial tcp [::1]:5432: connect: connection refused museum-1 | museum-1 | goroutine 1 [running]: museum-1 | main.setupDatabase() museum-1 | /etc/ente/cmd/museum/main.go:852 +0x2d8 museum-1 | main.main() museum-1 | /etc/ente/cmd/museum/main.go:124 +0x380 museum-1 exited with code 2 To recreate: get homeassistant os on a raspberry, install compose v2 and try to run quickstart
museum-1 | INFO[0000]main.go:849 setupDatabase Connected to DB
museum-1 | panic: dial tcp [::1]:5432: connect: connection refused museum-1 | museum-1 | goroutine 1 [running]: museum-1 | main.setupDatabase() museum-1 | /etc/ente/cmd/museum/main.go:852 +0x2d8 museum-1 | main.main() museum-1 | /etc/ente/cmd/museum/main.go:124 +0x380 museum-1 exited with code 2 To recreate: get homeassistant os on a raspberry, install compose v2 and try to run quickstart
Oh so you think the quick install script may create it wrong? I have to check it, thanks!
-# If your issue is resolved, you can use the /solved command to close the thread. If not, use /unsolve to cancel.
No sadly that is not the case...
It is yaml and looks right
I accidentally started the quick-install script in the wrong folder but it adapted to it and rewrote the config. So its right at the moment but still does not work
Sorry @no402 @Keerthana do you still think ita because of stale volumes? Im really lost and dont know what to do
Im new to this project, but for me it was the stale volume. Have you tried removing all the configuration anf stuff?
I don't think it is stale volume in your case, can you try renaming the current cluster to another name and running compose, will give an idea to validate it's not stale volumes