Hi there,
Just hoping there's a work around for this issue. Spent ages on google, couldn't find anything, so trying to use as many keywords as possible so others with the same issue can find this thread.
If you're on an ipad, using safari, on 3g, you can't use cpanel webmail without Cookie IP Validation off. Every request you make to webmail kicks you out with the standard "Your ip address has changed" error. If you're on wifi, or if you're using chrome on the ipad via 3g, it works fine.
Strangely, the ip address isn't actually changing. Running some tests echoing out $_SERVER from a test server, REMOTE_ADDR doesn't change from one request to the next. What DOES change is the port number at REMOTE_PORT. So I'm guessing when cpanel checks for an ip address change, they're actually checking a combination of the ip address and port.
I'd really prefer not to turn off Cookie IP Validation, but getting a fair few complaints with the current implementation. I'm wondering if it's possible to change the routine at all to check the ip address, but not the port number? Is there some template file I could modify to achieve this? Or would this also be quite dangerous and I'd be better off leaving the port number detection in place?
Any assistance would be greatly appreciated.
Just hoping there's a work around for this issue. Spent ages on google, couldn't find anything, so trying to use as many keywords as possible so others with the same issue can find this thread.
If you're on an ipad, using safari, on 3g, you can't use cpanel webmail without Cookie IP Validation off. Every request you make to webmail kicks you out with the standard "Your ip address has changed" error. If you're on wifi, or if you're using chrome on the ipad via 3g, it works fine.
Strangely, the ip address isn't actually changing. Running some tests echoing out $_SERVER from a test server, REMOTE_ADDR doesn't change from one request to the next. What DOES change is the port number at REMOTE_PORT. So I'm guessing when cpanel checks for an ip address change, they're actually checking a combination of the ip address and port.
I'd really prefer not to turn off Cookie IP Validation, but getting a fair few complaints with the current implementation. I'm wondering if it's possible to change the routine at all to check the ip address, but not the port number? Is there some template file I could modify to achieve this? Or would this also be quite dangerous and I'd be better off leaving the port number detection in place?
Any assistance would be greatly appreciated.