I have a customer who is is trying to access their Cpanel interface at http://www.<their_site>.com/cpanel. When they go to that URL, cPanel properly redirects them to the URL with port 2082 in it. But it will get no further.
1. This is _not_ a cPanel problem
2. I'm hoping to find help from a MAC user who has had this problem and has resolved it
Customer running OS-X - unsure what version. In both Firefox and Safari he is not able to access his cPanel interface at 2082.
3. telnet to port 2082 from terminal on same machine works fine and produces desired results
4. The MAC _CAN_ access :2083 (via httpS). Obviously this is preferred anyway, and the customer is using this.
But does anybody know of what might be happening on his MAC that he is unable to access port TCP 2082 outbound specifically? If you don't own and/or aren't familiar with a MAC, please do not respond.
We've tried adding Firefox as an allowed application in the firewall - that did not work. We also did an about:config in Firefox and added the string network.security.ports.banned.override with a value of 2082 and that did not help.
For those of you who have experienced this problem in the past, just have the customer use port 2083 as a workaround if they are able (using httpS instead of http).
Anybody have an idea what's going on?
Thanks,
Mike
1. This is _not_ a cPanel problem
2. I'm hoping to find help from a MAC user who has had this problem and has resolved it
Customer running OS-X - unsure what version. In both Firefox and Safari he is not able to access his cPanel interface at 2082.
3. telnet to port 2082 from terminal on same machine works fine and produces desired results
4. The MAC _CAN_ access :2083 (via httpS). Obviously this is preferred anyway, and the customer is using this.
But does anybody know of what might be happening on his MAC that he is unable to access port TCP 2082 outbound specifically? If you don't own and/or aren't familiar with a MAC, please do not respond.
We've tried adding Firefox as an allowed application in the firewall - that did not work. We also did an about:config in Firefox and added the string network.security.ports.banned.override with a value of 2082 and that did not help.
For those of you who have experienced this problem in the past, just have the customer use port 2083 as a workaround if they are able (using httpS instead of http).
Anybody have an idea what's going on?
Thanks,
Mike