2 years ago
This happened today, frontend could not reach this API through its railway domain (standard domain generated by Railway).. Service logs doesn't say anything wrong. It was also green.
Then I tried curl to the domain, and got this 404 from railway-edge? I re-deployed the service and eventually the error is gone. I'm trying to understand what could be happened, and to avoid future scenario like this
8 Replies
2 years ago
please redeploy
As I explained in the post, I redeployed, and the error is gone. I opened this post to understand what happened and what can we do to avoid issues like this in the future. Because people couldn't use the product without knowing what's happening, and logs false reported this as CORS issue
2 years ago
ah my bad -- our network control plane briefly failed to update a small subset of endpoints, thus users would see a 404 until they redeployed, we have since found and fixed the bug.
2 years ago
it wasnt, i'm not too sure as to why tbh
2 years ago
!s
Status changed to Solved brody • over 1 year ago