2 months ago
Hello,
I have a hono-bun/drizzle app connection using DATABASE_URL fails but DATABASE_PUBLIC_URL works I think there is a bug. both apps are in the same project and on railway remote. I use public url for now but would like to switch to private url once this is fixed
9 Replies
2 months ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
2 months ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open brody • about 2 months ago
2 months ago
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?
Attachments
2 months ago
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.
Status changed to Solved orenaksakal • about 2 months ago
2 months ago
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
orenaksakal
this is related to backup dump, when I recover from a backup dump.sql using psql the internal url no longer worksbackup was a simple dump and verified this also happens when I only recover with COPY statements of the data tablesthis backup belonged to railway postgres db so no version mismatch or errors visible on recover or afterwards just internal url stops workingedit: verified dump.sql is not the problem here by recovering local and coolify dbs both works, railway doesn't
2 months ago
A shot in the dark here, but after dumping the data have you tried redeploying the service?
2 months ago
yeap tried multiple times
2 months ago
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?
2 months ago
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
2 months ago
this was fixed silently same flow I followed is working now
Status changed to Solved brody • about 2 months ago