2 months ago
I’m having an issue where X-Forwarded-For and X-Real-IP are only showing the Fastly proxy IP instead of the actual client IP. Does anyone know how to fix this?
It was working until this afternoon MST
24 Replies
2 months ago
I think you can use X-Forwarded-For to get the real client IP.
Oh damn, I hope things go back to the way they were before, I felt like everything was fine.
Yeah, it’s unfortunate. The issues seem to be happening more frequently, and that’s especially frustrating in production apps.
It's possible, and I really like Railway as a service, but it's difficult when these things happen in production and you can't manage them. I hope this error doesn't last more than 10 hours and that things are restored as soon as possible.
2 months ago
I also encountered the same issue after this update without making any code changes — the real IP of the requesting user was lost. I then added debug logging to the response and confirmed that the real client IP is completely absent from all request headers.
Status changed to Awaiting Railway Response Railway • about 2 months ago
@Brody can we get the ball rolling on this as this is not only impacting me but other railway users. Sorry to ping you but I’m not sure what else to get support on a issue like this.
Status changed to Awaiting User Response Railway • about 2 months ago
2 months ago
Acknowledging this issue, we have raised it to our networking engineer.
2 months ago
Hey,
This has been fixed, no action is needed on your end.
We are sorry for introducing this regression and will be more diligent about changes to the behavior of headers going forward.
2 months ago
Hey,
This has been fixed, no action is needed on your end.
We are sorry for introducing this regression and will be more diligent about changes to the behavior of headers going forward.
2 months ago
No problem!
Status changed to Solved brody • about 2 months ago