Error: P1001: Can't reach database server at `timescale-postgis.railway.internal`:`5432`

My service cannot seem to connect to my db using the private database url. the regular database url does seem to work
6 Replies
Percy
Percy6mo ago
Project ID: f9724669-2787-46a8-bfcd-3dd6e9944ba6
thomasmol
thomasmol6mo ago
f9724669-2787-46a8-bfcd-3dd6e9944ba6 i didn't change anything in my setup, this started happening when i pushed a new commit. There were no changes related to the db. Am using Prisma to connect okay i just disabled and enabled private networking and now it seems to work again 🤷‍♂️ "just turn it off and on again" same thing happened on my production env jus tnow @Brody can you look into this? seemed to happen randomly
dkrusenstrahle
dkrusenstrahle6mo ago
Same issues for me on both Postgres and Redis.
trust!NICKOL
trust!NICKOL6mo ago
yesterday a restart fixed the problem for me, today it is down again i think it is for all networking between private networks
Patrick
Patrick6mo ago
I'm experiencing something similar where my Postgres and Redis on Digital Ocean can't be reached from Railway services 😬
trust!NICKOL
trust!NICKOL6mo ago
when using public url the app performance seems to degrade as if it is in different regions or something else