Unexpected error from Railway Proxy
i have my app deployed, when try to send any request by swagger any response from any endpoint return this msg: Unexpected error from Railway Proxy
Solution:Jump to solution
this doesnt seem like a message that railway is returning, looks like something your code is returning
25 Replies
Project ID:
cbfab0cc-7fc8-413e-b097-4dedc90d4e49cbfab0cc-7fc8-413e-b097-4dedc90d4e49
can you send a link to your docs so i could see this error for myself?
https://backend-api-tpo-production.up.railway.app/swagger-ui/index.html#/users-controller/signIn
this is the swagger
when you try to create new user, the endpoint return this msg
same happens with other
okay ill try that now
Solution
this doesnt seem like a message that railway is returning, looks like something your code is returning
I understand, in that case I will check the code, maybe someone in the team modified something
thanks for the help
no problem, let me know if you need any more help
but as it stands with just that as the error, there wouldn't be all that much i can help with
you were right, it was a problem of our code, it was a wrong error catch, we were able to fix it, thank you very much!
no problem!
though I'm curious and if you don't mind telling, what did the "railway proxy" mean in that message?
I'm not sure why the host returned that message, but when we tested locally our code returned a 403 because our identity provider returned an error that we were not taking into account, so the default error was a 403.
can it be a default message when a response has no body? is a good question.
not sure, maybe do a text search for that message in your project code? because if a response has no body railway is not going to be adding that message, I can promise you that much
is a possibility, but when I search for that message it does not exist in our code.
I think I have another case
with status 201
but in this case the endpoint should be return response
I don't know what to say, the message is very curious, but we will try to handle it from our code.
how are you sure that you where sending a 403 with an empty body?
as far as we can see yes, this is the error replicated from the project running local
with only header
okay, makes sense, I will try to reproduce
our project is made with java spring and for the security part we are using spring security so when it does not pass any validation of the request, it breaks in the security filter, returning only status 403.
i wasnt able to reproduce that message, meaning somehow your app is sending it
