postgres auth
[cpet@prod server]$ ./main
INFO[0000]main.go:108 main Booting up local server with commit #
INFO[0000]main.go:886 setupDatabase Setting up db
INFO[0000]main.go:893 setupDatabase Connected to DB
panic: pq: Ident authentication failed for user "ente" goroutine 1 [running]: main.setupDatabase() /opt/ente/server/cmd/museum/main.go:896 +0x32b main.main() /opt/ente/server/cmd/museum/main.go:128 +0x48c [cpet@prod server]$
INFO[0000]main.go:886 setupDatabase Setting up db
INFO[0000]main.go:893 setupDatabase Connected to DB
panic: pq: Ident authentication failed for user "ente" goroutine 1 [running]: main.setupDatabase() /opt/ente/server/cmd/museum/main.go:896 +0x32b main.main() /opt/ente/server/cmd/museum/main.go:128 +0x48c [cpet@prod server]$
11 Replies
The error "pq: Ident authentication failed for user 'ente'" indicates an issue with the PostgreSQL authentication configuration.
This can occur if you're using a stale Docker volume. If you are using Docker Compose for running Ente from source, you might not have set the same credentials in
.env and museum.yaml inside server/config directory. Edit the values to make sure the correct credentials are being used. More information can be found at https://help.ente.io/self-hosting/troubleshooting/docker#postgres-authentication-failed.
-# If your issue is resolved, feel free to use the /solved command to close this thread. If you'd like to ask me another question use /docsearchTroubleshooting Docker-related errors - Self-hosting | Ente Help
Fixing Docker-related errors when trying to self-host Ente
rocky linux 9 manuel setup
@Keerthana
Hey can you remove all the Docker volumes and restart the cluster with
Stale volumes could be causing this. scram should be used for authentication instead... can you confirm if above command works for you?
im not using docker
Can you share a sanitized version of your config and describe the path in which the Go binary for museum is running along with edited museum.yaml's path from example.yaml file?
If the file's not detected properly, this may be caused. Will try to replicate based on your inputs
how do i sanitize
Removing the actual credentials while sending the configuration file here works
@Keerthana
@Staff @Staff
Hey please don't ping staff for support. Self-hosting support is community managed
@Brogio sorry must of been my cat