Provision PostgreSQL's weird changes
What happened to Provision PostgreSQL? Ever since this change, I've been unable to connect my TortoiseORM to my database.
socket.gaierror: [Errno -2] Name or service not known (when using DATABASE_PRIVATE_URL)
asyncpg.exceptions.InvalidPasswordError: password authentication failed for user "postgres" (when using DATABASE_URL)
21 Replies
Project ID:
N/AN/A
do you have another service for you app in this project?
Sorry, what do you mean exactly?
do you have another railway service in this project
No, just Postgres
you can only connect to the database via the private url from another service within that same project
if you want to connect to that database from outside of that project you would need to use the non private url
I tried the non-private URL, but I get this error:
Which has never happened before
I'm hosting 12 Postgres databases just fine on Railway
Even the symbol in the dashboard is different for this project
(the green circle)
I tried creating a new project with Provision Postgres, but it's the same
I have provisioned plenty of the new postgres databases and have never had any issues with authentication
is your client compatible with postgres 16?
I believe so
I'm just not sure why this is suddenly an issue this morning
can you connect to the database with a different kind of client like pgadmin or dbgate?
Let me try
Yeah I'm able to connect to it just fine on pgAdmin4
Huh
this could be a copy issue, or your client isn't compatible with postgres 16
One issue though, what happened to the Query section in Postgres? It went from this:
To this:
Solution
postgres is now just a regular service with a docker image and a volume
pro tip, read railways weekly changelogs
I see I see, alright thank you very much for your time and assistance!
no problems