3 months ago
Hi,
Since a week or so, maybe longer the X-Real-IP no longer seems correct
We used to have trusted proxies for internal ip ranges
Ive tried to add fastlys ip ranges, but I think you have a private static IP. So ive added 157.52.108.0
This also doesnt seem to work
Pinned Solution
3 months ago
yeah I agree with you, I'm just giving options...anyway, looking at the X-Forwarded-For I can see the real ip (my ip) + another one starting with 157.52.x.x
4 Replies
3 months ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • 3 months ago
3 months ago
can you try using the Fastly-Client-Ip or the X-Forwarded-For
have a look at this:
https://utilities-us-east.up.railway.app/raw
yet it's a shame the key has been changed without an official communication
3 months ago
The X-Forwarded-For is also incorrect as its missing the actual client real ip. and I would like a fix where im able to use the X-Real-IP as this should always be the client IP.
I really shouldnt have to care that railway uses fastly, I dont want any fastly specific code to be honest
3 months ago
yeah I agree with you, I'm just giving options...anyway, looking at the X-Forwarded-For I can see the real ip (my ip) + another one starting with 157.52.x.x
3 months ago
Ohh yeah, I see it was added to the x-forwarded-for after adding fastly as trusted for me now too. After also adding it to express as trusted it should work, at least its in a standard header now.
Status changed to Solved brody • 3 months ago