#Suddenly Requests are not been accepted by the server (deployed on Railway)

15 messages · Page 1 of 1 (latest)

vivid latch
#

Hi, I have been using Railway for quite some time now. After yesterday there was an outage, the outage cleared, everything went back to normal. However today onwards, I am seeing this problems, where when I am trying to visit the app (which is deployed on railway), I am not able to see the app loading.

In the logs also, its not even showing anything like /health or just / There is no problem of the database, and the worst part, this is old code. It was all good before, suddenly (without even deploying any new code), I re-deployed it, but nothing happened.

lament rockBOT
golden spindle
#

Can you define "I am not able to see the app loading." please?

vivid latch
#

Some updates, I deployed the app in railway, a fastapi backend server.

  1. The first server when deployed and I click the deployed link, it does not works, I think there is some DNS resolve issues

  2. I re-deployed the same app in a different railway project, and it worked

vivid latch
#

Would love to chat in dm, so I can share some more info @golden spindle Thanks

golden spindle
#

Sorry, but we do not offer support in DMs.

#

Either way, please define "it does not works"

vivid latch
#

So suppose my deployed url is this:

https://xxxxxxxxx.up.railway.app/

When I try to go into this url, it does not load, and its very in-consistent lately after the outage. Where sometimes it takes couple of minutes to load (even 10 or 20 minutes), sometimes it loads, and sometimes it does not.

golden spindle
#

You would want to look into what the difference is that is causing your code to respond slowly.

vivid latch
#

No, these services have been running properly for the last 20 days, with no push of new code.

#

As I said, same code when deployed on new project works. And it should have solved the issue, but the problem is the volumes are not shared, hence I need to go back to my previous project and make it work somehow, so that the data is not lost.

#

Or atleast I can ssh into that (which is also I am not able to, because of timeout), and make a backup.

vivid latch
#

Hi its not solved yet

#

My data is out there