Cpanel user logged as 127.0.0.1
Hi, when I login to cpanel and check log access history my ip is been shown as 127.0.0.1. I've upgraded to the latest version as the issue was highlighted as fixed in the latest version 134.0.40 but after upgrade my ip is still been logged as 127.0.0.1 in lastlogin file.
How do I fix this issue thanks.
-
Hey there! It looks like this case you're referencing didn't include a fix for the .lastlogin file. I've created case CPANEL-54038 and linked this thread to it so I'll be sure to post an update once I hear one!
0 -
Hi, I also updated to the latest cpanel version 136.0.23 still the same issue.
0 -
That's to be expected as this issue hasn't been resolved just yet. I'll be sure to post once this is fixed.
0 -
Hi I noticed that a new update has been released version 136.0.24. Has the issue been fixed in this version?
0 -
No - I'll be sure to post once this is resolved.
0 -
Okay thanks
0 -
Hey Rex hopefully it be resolved, cause it is also effect webshield and cpanel account protection for some reason.
2 -
Taking over 3 weeks for a paid product (which increases its prices annually by the way) to issue an update about this is frustrating to say the least.
0 -
I'm expecting this to be fixed as part of the larger work we took on through case CPANEL-54005. Are you still seeing this issue today?
0 -
Yes the issue is till there in Cpanel version 136.0.27
0 -
Could you create a ticket so this can be investigated directly?
0 -
You seem not to be sure that it was fixed. Can you confirm that case CPANEL-54038 was resolved in the latest update before I proceed to create a ticket thanks.
0 -
Also I found this post - https://support.cpanel.net/hc/en-us/articles/41347142868503-IP-addresses-show-as-127-0-0-1-in-logs-when-Imunify360-webshield-is-in-use?input_string=cpanel+user+logged+as+127.0.0.1
Seem it has not been fixed.
0 -
Javatech Systems- it's not so much that I'm not sure, it's just that this thread has spanned multiple similar issues at this point and it's getting confusing for everyone.
This thread has touched on the .laastlogin file, then you mentioned the proxy subdomain access, and now you've sent an Imunify link. While they all look related on paper, these three areas handle logins differently, which is why they've required different cases to handle.
0 -
We use imunify so seem the issue we are experiencing is related to the post. When are you going to fix it?
0 -
I don't have an update on that specific case but I see the team is working on that now. Hopefully that means there's a fix in place soon!
0
Please sign in to leave a comment.
Comments
16 comments