Internal hosts don't work after region migration
It seems that the internal hosts e.g. postgresql://postgres:[email protected]:5432/railway don't work after doing a region migration. The proxy ones do still. Bug or is there something that should be added when using EU region??
Solution:Jump to solution
i just deployed nocodb, then changed the region on both databases to eu, then changed the region on nocodb to eu too - no issues
maybe try deploying nocodb again from the template, but please dont change the service variables...
16 Replies
Project ID:
daf664ef-3747-4e2f-8abe-77b1317b3273
Project ID:
daf664ef-3747-4e2f-8abe-77b1317b3273
daf664ef-3747-4e2f-8abe-77b1317b3273
same for redis private url
just did a test connecting to the database via public and private in the original region it was deployed to (us-west) - no issues
migrated the database to us-east, re-ran the test - no issue
migrated the testing service to us-east, re-ran the test - no issue
can you please be more specific when you say "don't work"
Hi Brody, Just ran a test using nocodb, span up with original region - no issues. Switched to EU region for both service and PG and started getting Error: getaddrinfo ENOTFOUND
That was from the nocodb logs. Using the proxy public host works fine.
will try to reproduce with nocodb
NOPE: pg://postgres.railway.internal:5432?u=${{Noco DB.PGUSER}}&p=${{Noco DB.PGPASSWORD}}&d=railway
YEP: pg://${{Noco DB.PGHOST}}:${{Noco DB.PGPORT}}?u=${{Noco DB.PGUSER}}&p=${{Noco DB.PGPASSWORD}}&d=railway
Same for redis
how long ago did you originally deploy nocodb?
1 hour maybe
neither of those variable strings are correct
Solution
i just deployed nocodb, then changed the region on both databases to eu, then changed the region on nocodb to eu too - no issues
maybe try deploying nocodb again from the template, but please dont change the service variables
yeah something is awry because I get the same for redis too
i have not been able to reproduce any errors, maybe try deploying nocodb again from the template, but please dont change the service variables
Yep, now it worked 🤷♂️
Sorry for the bother
no worries!