Cannot access Cpanel non-SSL port (2082) on MAC

[mtindor]

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

 

[Voltar]

Just a thought, but can your customer access another cPanel, possibly on a different server? You could try the demos if needed.

Are they using a proxy server, like Squid that may be interfering with the web access? That would be my only thought since telnet works, since https isn't proxied by default.


Not a Apple expert but just those just came to mind, hope it helps.

 

[mtindor]

Just a thought, but can your customer access another cPanel, possibly on a different server? You could try the demos if needed.

Are they using a proxy server, like Squid that may be interfering with the web access? That would be my only thought since telnet works, since https isn't proxied by default.


Not a Apple expert but just those just came to mind, hope it helps.

Normal HTTPS (port 443) works to anywhere
Nonstandard HTTPS (port 2083 Cpanel) works to anywhere
Normal HTTP (port 80) works to anywhere

Normal HTTP (port 2082) does NOT work from the MAC to anywhere when he is on his Airport wireless card

Normal HTTP (port 2082) DOES work from the MAC to anywhere when he is plugged in via ethernet

telnet from MAC terminal to port 2082 works fine
- sitename.com 2082 - connects
- GET / HTTP/1.0 < and enter twice >
- the typical HTTP is spewed back from the server

So the underlying OS (as whatever user the terminal is run as) can access outbound 2082. But FireFox/Safari cannot access outbound 2082.

Mike

 

[cPanelDavidG]

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

I use a Mac for my workstation and have never experienced this issue in the many years I've used Macs. Is it possible your customer is running some client-side firewall that is blocking port 2082?

 

[Eric]

I would highly recommend installing and testing with tcptraceroute. You can run it from his mac and it becomes clear very quickly.

Tcptraceroute version 1.5beta7 - How to Download and Install on Mac OS X

Thanks!

 

[mtindor]

A tcp traceroute? Hmm. I already indicated that I can telnet to port 2082 and get the appropriate response. So the underlying OS has no problem gaining access.

It has to be some sort of firewall issue with FireFox / Safari, or a Firefox / Safari issue itself.

But it's odd because the customer does not have this problem using ethernet - only when he is using his Airport wireless. I'm not absolutely sure that this happens at EVERY wireless location he uses his laptop, but he did tell me that it has happened in multiple locations when he was using wireless - but when he would plug into ethernet somewhere it would work.

Being that it si a MAC, I know nothing about how the firewall operates - or if you ccan modify settings based upon whether it is connected to ethernet vs wireless.

All I can say is that currently he is on wireless and cannot access port 2082 via a web browser - but CAN access it via a terminal session using telnet.

Mike

 

[Eric]

A tcp traceroute? Hmm. I already indicated that I can telnet to port 2082 and get the appropriate response. So the underlying OS has no problem gaining access.

It has to be some sort of firewall issue with FireFox / Safari, or a Firefox / Safari issue itself.

But it's odd because the customer does not have this problem using ethernet - only when he is using his Airport wireless. I'm not absolutely sure that this happens at EVERY wireless location he uses his laptop, but he did tell me that it has happened in multiple locations when he was using wireless - but when he would plug into ethernet somewhere it would work.

Being that it si a MAC, I know nothing about how the firewall operates - or if you ccan modify settings based upon whether it is connected to ethernet vs wireless.

All I can say is that currently he is on wireless and cannot access port 2082 via a web browser - but CAN access it via a terminal session using telnet.

Mike

It's good for fishing out proxy servers since you see where your data is going. I had some problems myself with the Safari4 update.

 

[mtindor]

I use a Mac for my workstation and have never experienced this issue in the many years I've used Macs. Is it possible your customer is running some client-side firewall that is blocking port 2082?

It is possible. He is running some firewall within OS X. The strange part is that it seems to only happen on his wireless and not when he is connected via ethernet.

A lot of questions remain unanswered though - such as, when he is using wireless is it always at some hotspot somewhere? and if so, that hotspot may be disallowing it.

But I did Google a bit and saw there were some random posts from other people experiencing the same problem. But as usual, when somebody posts about a problem and then they find a resolution, they don't report back in their original post that they did

It's difficult for me to troubleshoot with him since I have no familiarity with a mAC.

At any rate, he is able to access over SSL so he is doing that now. But that's a workaround to his problem.

Keep in mind i never indicated this was a cpanel problem - but I figured if there were others with MACs who may had had this problem they could let me know what they did to correct it.

Mike

 

[Eric]

That really sounds like the work of some security software. If it were a PC I'd be looking eying the anti-virus scanner about now.

 

[mtindor]

It's good for fishing out proxy servers since you see where your data is going. I had some problems myself with the Safari4 update.

Doh, I wasn't even thinking about a damned proxy server! Unreal. Thanks for bringing that up. It may or may not be it, but what a brain fart on my end.

Mike