2 months ago
The issue is that Railway's load balancer is not properly forwarding the real client IP. The problem is that Railway is setting x-forwarded-for and x-real-ip to 127.0.0.1, which means Railway's load balancer is not configured to pass through the real client IP.
0 Replies
[IP-DEBUG] Direct connection: 127.0.0.1
🔍 [IP-DEBUG] Found proxy headers: { xff: '127.0.0.1', real: '127.0.0.1' }
✅ [IP-DEBUG] Using x-real-ip: 127.0.0.1
🌐 [HTTP-REQUEST] GET / - IP: 127.0.0.1 - UA: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36
📡 [PROXY-HEADERS] { 'x-forwarded-for': '127.0.0.1', 'x-real-ip': '127.0.0.1' }
✅ [HTTP-RESPONSE] GET / - 200 - 1596ms2 months ago
Looks to be working fine:
2 months ago
That would be an issue with your application or configuration. I will let the community assist with that.
2 months ago
Yes, though that is not applicable.
I'm u sing Docker -> nginx -> proxy (node app). and i always get 127.0.0.1
2 months ago
That would be an issue with your application or configuration.
2 months ago
x-forwarded-for and x-real-ip 127.0.0.1
2 months ago
The first IP here is the user's IP
2 months ago
The other IP's are the proxies it went through
2 months ago
!s
Status changed to Solved medim • 2 months ago