#Deployment server issue.

48 messages · Page 1 of 1 (latest)

half veldt
#

I’ve deployed my backend on Railway with a database connected. The issue is that it works fine for a while after I deploy, but then it just stops responding. Whenever I hit the backend with a request, it times out and doesn’t reply in time.
Right now I have to redeploy once or twice a day just to get it working again, which is pretty frustrating. I also have a big meeting today and really don’t want this to mess things up.
Can you please help me figure out what’s going on, or fix it from your side if possible?
project id: edf11695-2a90-4573-a360-85b19c89ac7d
service: f02f072c-d0d7-46f9-b79f-fb9f8de4cd1c
service 2: 5484d7cb-596b-46e6-92e1-7219766f47ad

Both of these services are same repo please fix this asap.

stoic flint
half veldt
#

i have a big meeting today. please help me out

#

yes i did the db takes too long to repond and always request fails after some time of deployement with 502

half veldt
stoic flint
#

Is the db serverless?

half veldt
#

no the db is not serverless i think we are using noraml db of yours

#

we are facing this same issue from friday

stoic flint
#

are the services in the same project?

half veldt
#

yes

stoic flint
#

hmm

half veldt
#

i have other services over there aswell every other service is working fine just facing issue with these 2 services

stoic flint
#

you should add some better logging to your backend to identify the exact issue

half veldt
#

we already did that it didn't helped much so we deployed on ngrok so we can identify issue in a better way

#

let me show you something

stoic flint
#

i honestly have no idea

#

hm

#

maybe someone else can help you, sorry

half veldt
#

HTTP Status Code: 502 (Bad Gateway) for ALL requests
Error Rate: 100.00% (1,000 out of 1,000 requests failed)
Response Time: Extremely high at 15.59 seconds average
📈 Performance Metrics
Response Times:
Average: 15.59 seconds (extremely slow)
Minimum: 15.55 seconds
Maximum: 15.74 seconds
95th Percentile: 15.68 seconds

half veldt
#
  • Server Overload: Your Railway deployment is likely overwhelmed by the load.
  • Resource Exhaustion: The server may have run out of memory, CPU, or database connections
  • Timeout Issues: The server is taking too long to respond, causing timeouts
#

can anyone can guide me on this
Railway rate limit of 500 logs/sec reached for replica, update your application to reduce the logging rate. Messages dropped: 2164

#

Brody can you help me out over here.

vale jungle
#

Where are you located geographically?

half veldt
#

Pakistan

#

Asia

#

i have added some better logging

image.png
vale jungle
#

I would start by making sure all your services are in the Asia region. Most of your services are not deployed to our Asia region.

half veldt
#

becuase our services are being used in us

#

so most are deployed on different region

vale jungle
#

Then make sure they are all located closest to the users.

The next step would be to make sure the connection to the database is done via the private network.

half veldt
#

how am i supposed to know this that the connection is via private or public

vale jungle
#

If you have your backend connect to the database via the TCP proxy, then you are connecting to it via the public network.

half veldt
#

we simply connected mysql with our node application using credetials provided by railway

half veldt
vale jungle
#

Have your backend connect to the database via the private network.

half veldt
#

how to do that

#

i dont have much time

#

like do i have to do extra things in my backend?

#

it'll be great if you could guide me

vale jungle
half veldt
#

i'm in a do or die situation.

#

the meeting is in us and my application would be tested there.

half veldt
#

please dont mind. if i miss anything

#

you just tell me it'll be done

vale jungle
#

I've bountied this thread so that other community members may come to your aid.

#🏆｜bounties-feed message

half veldt
#

tysm sir