a year ago
I started a new postgres service in a new postgres project. I am trying to connect to it from my laptop just to verify that it's working.
Upon creation, it has a DATABASE_PUBLIC_URL value which seems to use the proxy domain that Railway setup automatically.
If I run psql <DATABASE_PUBLIC_URL>, I get an error password authentication failed for user "postgres". I triple checked the URL matches with the DATABASE_PUBLIC_URL variable. I also tried not specifying the password in the URL and providing it only on prompt. It's still not working. I also double checked that the password is correct by comparing to the PGPASSWORD variable and that the user is correct comparing to the PGUSER variable. Any suggestions on why it might be rejecting the password that railway created?
11 Replies
a year ago
If it helps, there's a spinning Database connection in the Data tab
Attachments
Status changed to Awaiting User Response Railway • about 1 year ago
a year ago
The second one worked. I guess I can move forward with that for now
Status changed to Awaiting Railway Response Railway • about 1 year ago
a year ago
Fwiw, I created a 3rd and 4th just to test. The third failed to come up in the same way. the 4th succeeded like the 2nd
a year ago
Glad that unblocked you-
Not that our scaling woes should affect you, but I have a few leads I can discuss with the team on why this was the case and how we can fix it.
Status changed to Awaiting User Response Railway • about 1 year ago
a year ago
An internal ticket has been attached to this thread. Updates will be relayed in this thread, so keep an eye out!
Status changed to In Progress Railway • about 1 year ago
a year ago
I was able to reproduce a path in product that will allow this to happen.
What I was able to do to reliably reproduce this was click that deploy button on the database service while the changes where applying, is this perhaps what you did too?
Status changed to Awaiting User Response Railway • about 1 year ago
a year ago
Update: An internal ticket linked to this thread has been changed to Todo.
a year ago
Unfortunately, I'm not sure. I was doing lots of experimentation, changing variables around, doing deploys, etc Sorry I didn't respond sooner.
Status changed to Awaiting Railway Response Railway • about 1 year ago
a year ago
Thank you for letting us know. We'll mark this thread as solved, but let us know in case you experience any other issues.
Status changed to Awaiting User Response Railway • about 1 year ago
Status changed to Solved christian • about 1 year ago
a year ago
Update: An internal ticket linked to this thread has been changed to Completed.
Status changed to Awaiting Railway Response Railway • about 1 year ago
a year ago
Update: An internal ticket linked to this thread has been changed to In Progress.
7 months ago
the same happened to me as well. The first database I created, I was not sure I needed it, so I marked it up for deletion. Then I created a new one, which never worked. My app was not able to connect to the 2nd DB I created. got the same error `password authentication failed for user "postgres"` both on public and private urls. Then I created a 3rd one, which worked smoothly.