a year ago
Hi everyone!
Unfortunatelly I'm unable to connect to my Umami postgress db. Previously I turned on the public networking for the db because I tried to connect to a pgadmin. For a couple of minutes I also disabled private networking, but right after I restarted, non of the service or pgadmin was able to connect to the database. From the Postgres I can see that the db are ready to go, but always refusing any incomming connection due some password authenticaion failure.
2024-02-22 18:09:00.083 UTC [121] FATAL: password authentication failed for user "railway"
2024-02-22 18:09:00.083 UTC [121] DETAIL: Connection matched pghba.conf line 100: "host all all all scram-sha-256" 2024-02-22 18:09:04.911 UTC [122] FATAL: password authentication failed for user "railway" 2024-02-22 18:09:04.911 UTC [122] DETAIL: Connection matched pghba.conf line 100: "host all all all scram-sha-256"
I already tried to reroll the previous deployments, also rewrite all of the environmental settings.
The whole project was started from a railway source, and the project ID is the following: 0dfb3481-24bb-4b76-b325-d31f1c4cf72d
0 Replies
a year ago
also rewrite all of the environmental settings.
please explain what this entailed
Recreated a similar environment on my colleges user, and double check the settings. While I tried to reconnect umami to the db I also tried different environment settings. The thing what I’m trying to say whit this, the the env settings are fine, the issue is not related to this. It seems that the db cannot be reached with the correct credentials.
a year ago
i think you may have misconfigured something
I don't think so, before the connection lost I did not modified the environmental settings. Also, on the same project I added a brand new postgress db with the same settings, and I can connect it to pgadmin without any issue. I think the main problem is related to the private networking… Is there any option or troubleshoot step to check if the db user/password are match?!
a year ago
have you changed the database username or password?
When the issue started, the db password unchanged. Once I tried to change it, but right now the db password is the same as the original.
a year ago
is there important data in the database
a year ago
besides asking you to put everything on the database service back to how it was, there's not much more I can do for you here unfortunately
a year ago
not sure what you mean by that
The main reason why we want to connect to the db with pgadmin, to create a backup and download it
a year ago
the database would need to be operational in order to do that
a year ago
oh you got it working?
a year ago
but no there's no native filebrowser / ssh access
The db was always operational, the main issue with the connection. In the logs we can see all of the rejected connections, also, if we are trying to attempt any connection from a fake account. I have to say, we still have the priginal user and password, so that's could cause the issue. Now we are able to attach the volume to a volume file browser container and access the db data via file manager. Is there any way to modify the db with a new connection credentials?