Unexpected error from Railway Proxy
Anonymous
TRIALOP

a year ago

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

0 Replies

Anonymous
TRIALOP

a year ago

cbfab0cc-7fc8-413e-b097-4dedc90d4e49


brody
EMPLOYEE

a year ago

can you send a link to your docs so i could see this error for myself?



Anonymous
TRIALOP

a year ago

this is the swagger


Anonymous
TRIALOP

a year ago

when you try to create new user, the endpoint return this msg


Anonymous
TRIALOP

a year ago

same happens with other


brody
EMPLOYEE

a year ago

okay ill try that now


brody
EMPLOYEE

a year ago

this doesnt seem like a message that railway is returning, looks like something your code is returning


Anonymous
TRIALOP

a year ago

I understand, in that case I will check the code, maybe someone in the team modified something


Anonymous
TRIALOP

a year ago

thanks for the help


brody
EMPLOYEE

a year ago

no problem, let me know if you need any more help


brody
EMPLOYEE

a year ago

but as it stands with just that as the error, there wouldn't be all that much i can help with


Anonymous
TRIALOP

a year ago

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!


brody
EMPLOYEE

a year ago

no problem!


brody
EMPLOYEE

a year ago

though I'm curious and if you don't mind telling, what did the "railway proxy" mean in that message?


Anonymous
TRIALOP

a year ago

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.


Anonymous
TRIALOP

a year ago

can it be a default message when a response has no body? is a good question.


brody
EMPLOYEE

a year ago

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


Anonymous
TRIALOP

a year ago

is a possibility, but when I search for that message it does not exist in our code.


Anonymous
TRIALOP

a year ago

1261140691581407500


Anonymous
TRIALOP

a year ago

I think I have another case


Anonymous
TRIALOP

a year ago

1261141011413864400


Anonymous
TRIALOP

a year ago

with status 201


Anonymous
TRIALOP

a year ago

but in this case the endpoint should be return response


Anonymous
TRIALOP

a year ago

I don't know what to say, the message is very curious, but we will try to handle it from our code.


brody
EMPLOYEE

a year ago

how are you sure that you where sending a 403 with an empty body?


Anonymous
TRIALOP

a year ago

as far as we can see yes, this is the error replicated from the project running local


Anonymous
TRIALOP

a year ago

1261142738284318700


Anonymous
TRIALOP

a year ago

with only header


brody
EMPLOYEE

a year ago

okay, makes sense, I will try to reproduce


Anonymous
TRIALOP

a year ago

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.


brody
EMPLOYEE

a year ago

i wasnt able to reproduce that message, meaning somehow your app is sending it

1261158722286391300


Loading...