Remote IP stopped work in July
Hello,
I have a few servers that use remote_ip module in apache to get the client IP when connecting from a proxy. All was working well with host#1 through June of the this year when in July of this year host#1 remote_ip will only show local loop 127.0.0.1
I have another server host#2 that still works correctly. I tried to compare the two and they look like the same configuration.
I've working with CloudLinux support for over a week now.
Both serves run Imunify360.
Host#2 remote_ip functions correctly.
Client IP HTTP_X_SUCURI_CLIENTIP: [client IP]
Client IP HTTP_X_FORWARDED_FOR: [empty]
Client IP HTTP_X_REAL_IP: [client IP]
Client IP REMOTE_ADDR: [client IP]
and host104 does NOT function correctly:
Client IP HTTP_X_SUCURI_CLIENTIP: [client IP]
Client IP HTTP_X_FORWARDED_FOR: [client IP], [proxy IP]
Client IP HTTP_X_REAL_IP: [client IP]
Client IP REMOTE_ADDR: [local Loop IP]
If Imunify360 is disabled on host#1 then REMOTE_ADDR will show [proxy IP].
We have tried many things. I cannot give support unattended remote access.
Any thoughts on this?
Where should I start looking on host#1 for why remote_ip is showing local loop.
-
Hey there! Unfortunately I don't have any other details to add. I see you had one ticket with CloudLinux opened since November 2, and another one is still ongoing that I can't see on my end (236354). If they aren't able to find anything with direct access to the server, I'm not going to be much help over the Forums.
I'm sorry I don't have more to offer, but I'd keep working through that ticket to see if they can get to the bottom of the issue.
0 -
Okay, thanks.
I've working the ticket for weeks now.
I was hoping someone might chime in if they had any comments.
0
Please sign in to leave a comment.
Comments
2 comments