⚠️ Database error — could not load merchants. Please try refreshing
rameshsbr
PROOP

2 months ago

I have a application on railway and this application has 3 portal admin, merchant and superadmin. In side the super admin portal i have details and accounts information of the merchant and since yesterday night till today i cant login or do anything on the merchant portal and also cant get any details in the merchant's page inside the super admin portal. When i check it shows that railway postgress has an issue cause this is the error i get "⚠ Database error — could not load merchants. Please try refreshing" while the entire platforms works without any issue in my localhost and it was working fine yesterday evening GMT +8 5pm

But when i check my postgress database in the railway it has the valid data and everything is there but why in the portal i dont see anything

$20 Bounty

4 Replies

Railway
BOT

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 Railway 2 months ago


ardasenguzeldev
FREE

2 months ago

Hey! Since it works perfectly on your localhost and the database has the valid data when checked directly, this sounds like an infrastructure or resource issue on Railway rather than a bug in your code. Here is what you should check:

  1. Check Backend Logs: The UI error is just a generic fallback. Check your backend service logs on Railway. Look for errors like timeout, too many connections, or OOM.
  2. Connection Leaks: It’s possible your app exhausted the database connection pool overnight. Try restarting your backend service on Railway. If it starts working immediately after the restart, you likely have a connection leak in your code.
  3. Resource Limits: Check the 'Metrics' tab on Railway for both your App and Postgres service. Did either of them max out on RAM/Memory?
  4. Internal Routing: Double-check if your app uses the Railway Internal Database URL. Sometimes public routing has hiccups, but internal routing remains stable

nadartech
PRO

2 months ago

Last night some of my databases also crashed. Sometimes even the ones I am not actively using crash unexpectedly, and I have to redeploy them to make them work again.


Status changed to Solved rameshsbr 2 months ago


ardasenguzeldev

Hey! Since it works perfectly on your [localhost](http://localhost) and the database has the valid data when checked directly, this sounds like an infrastructure or resource issue on Railway rather than a bug in your code. Here is what you should check: 1. **Check Backend Logs:** The UI error is just a generic fallback. Check your backend service logs on Railway. Look for errors like `timeout`, `too many connections`, or `OOM`. 2. **Connection Leaks:** It’s possible your app exhausted the database connection pool overnight. Try **restarting your backend service** on Railway. If it starts working immediately after the restart, you likely have a connection leak in your code. 3. **Resource Limits:** Check the 'Metrics' tab on Railway for both your App and Postgres service. Did either of them max out on RAM/Memory? 4. **Internal Routing:** Double-check if your app uses the Railway Internal Database URL. Sometimes public routing has hiccups, but internal routing remains stable

rameshsbr
PROOP

2 months ago

Hi

Thanks for the suggestions

You were right i check for the error and found out there were some migrations not been done that had caused this whole mess.

Thanks for your assitance


Status changed to Awaiting Railway Response Railway 2 months ago


Status changed to Open brody 2 months ago


rameshsbr

Hi Thanks for the suggestions You were right i check for the error and found out there were some migrations not been done that had caused this whole mess. Thanks for your assitance

ardasenguzeldev
FREE

2 months ago

You are welcome. Have a good day. Could you change the status :)


Welcome!

Sign in to your Railway account to join the conversation.

Loading...