https://railway.com/project/a774cc0a-3e6c-4e8d-a6da-3544d6aca5ed/service/c240c5bc-7201-4643-8dc5-d7343a13ab3f?environmentId=22fa5702-54d9-48fa-a23b-0f75d81f6717

Hey guys, we are presenting the site for a client and we need it to be up

😦

Now its taking longer to initialize

Hi! There's an ongoing incident right now where builds may take longer to deploy #🚨｜incidents

But we were not building it, it just went down, then my colleague restarted

We were using the api normally

Do you know what is going on?

Seems like he redeployed it resulting in a new Build

You can try aborting that build and redeploying it again

Also, github is down so if this service of yours is linked to a repo then it will also be affected by the incident

Oh, he said to me he actually redeployed, but i want to know why the service went down, we looked at the logs in chrome devtools and it was throwing CORS, then i tried to access the api and it showed this:

Did u follow the 'Fixing common errors' page that it suggests?

Also, cors errors are unrelated to the platform you deploy on, you configure that on your code.

But we configured it correctly, we had that problem before and managed to make it work in our api, so its not in our side, i noticed when a service is down the request in the chrome shows CORS for some reason

It just suddenly went down, we were using the api and accessing the frontend and it was working fine.

Anything in the logs?

I really doubt this is related to Railway, more users would've reported this.

But i'm willing to help you on this one if you give me some logs 😉

Logs were normal in railway, nothing wrong ahaha, thats why its so strange

and what do you mean by "it went down"?

u receive a bad status code or a req just hangs indefinitely?

Now its working again, we rebuilded.

But what i mean by went down is that we couldn access the service.

Strange, right? 😅

yep

can you do a cntrl + k -> download deployment logs

and paste them here for me to take a look?

Of course! here it is:

1384624453467766794

Is it successfully connecting to the Redis instance? because according to the last logs seems like it is struggling to do so?

Asked my colleague that made that redis feature, he said its working fine

Im doing reqs to your API through the included swagger docs just fine

I'm also not receiving that application failed to respond

What I think is happening is that some endpoint is crashing your API

Oh, so we had some crashes lately in production environment, but in railway's dashboard it was showing "CRASHED", and in the logs we spotted the problem, but this time, occurred in DEV and it had no logs, no "CRASHED" status haha…

Maybe an unhandled error? Seems to be just fine from Railway's side

Test those endpoints 😉

Or It could have been a temporary error, right? But thanks for the help @Medim, if it happens again i can go back to this thread?

We use NestJs and it is very robust against errors, that's why we suspect something on Railway's side.

Sure, I will keep this thread open for some time if you have any other issue.

!s