Hey there! We've found the following might help you get unblocked faster:

• 🧵 Postgres DATABASE_URL either invalid or internal networking is down, application connected to DB crashing

• 🧵 Urgent — Public proxy cannot reach Postgres (ENETUNREACH to IPv6)

• 🧵 Can't get correct DB connection

• 🧵 Custom variables not loaded

If you find the answer from one of these, please let us know by solving the thread!

what error do you get? tbh I would really surprised if this was a railway issue....did you copy paste the url or did you set the variable using the drop down after clicking the link in the screenshot?

hmm I was thinking I will get railway support to help out here as I'm on a pro plan. Yes I have been using railway for a while now and the issue started happening recently with new project, tried both env reference to db and copy paste the value directly.

this is related to backup dump, when I recover from a backup dump.sql using psql the internal url no longer works
backup was a simple dump and verified this also happens when I only recover with COPY statements of the data tables

this backup belonged to railway postgres db so no version mismatch or errors visible on recover or afterwards just internal url stops working

edit: verified dump.sql is not the problem here by recovering local and coolify dbs both works, railway doesn't

A shot in the dark here, but after dumping the data have you tried redeploying the service?

yeap tried multiple times

probably you already tried all I can suggest, but I'll still write down, in case just ignore the message:

• can you check that the internal/public url uses the same credentials & the same db name?

• when you recover the db, is it recovered with the right db name?

• do you have any particular user/role that might not be included in the dump?

• yes they are same dbs /railway

• yeap for recovery i use public url with "psql mypublicurl < dump.sql"

• not really, tried to recover with only sql COPY commands commenting out everything else the result was the same

this was fixed silently same flow I followed is working now