#DB connection
9 messages · Page 1 of 1 (latest)
Can’t help with zero information
I don't have much information either, but I assume that as support, you at least have access to the log files — otherwise, what’s the point of the project ID?
Here are the cases:
Local build + local database → works
Local build + Railway database → works
Railway build + Railway database → doesn't work
strapi start
[2025-05-12 15:58:38.115] debug: ⛔️ Server wasn't able to start properly.
[2025-05-12 15:58:38.117] error: connect ECONNREFUSED 127.0.0.1:5432
Error: connect ECONNREFUSED 127.0.0.1:5432
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16)
loudbook is not a Railway employee, so they only have the information you provide them.
Railway employees do not offer project help, we can only provide support for the Railway platform or product.
I don’t quite understand. My project isn’t working on your hosting.
Are you basically suggesting that I should run it on a different hosting provider?
I mean, I’ve actually been thinking about that, yes.
I'm sorry but we cannot provide support for application level issues or configuration errors, that is where our community comes in!
Railway was originally a product that made it easy to quickly deploy websites.
It’s really unfortunate that you’ve made the interface and configuration so complicated that I now have to move my projects off your hosting.
You where attempting to connect to Postgres via localhost (127.0.0.1)
I'd love feedback on how the platform could help you better understand those kinds of configuration errors.
First, please explain why DATABASE_HOST=yamabiko.proxy.rlwy.net:54234 works, while DATABASE_HOST=postgres.railway.internal causes an error.