Rules for enabling access to port 2082 for CPanel access[RESOLVED]

I’m trying to create a website on a new web host that I’ve just joined. They use CPanel (Hosting Platform of Choice) for administering member websites. The problem is that I cannot access the CPanel because it uses port 2082 and it looks like Comodo is blocking that port (or is it McAfee???).

How do I setup the rules in Comodo to allow port 2082? I’m totally clueless when it comes to setting up firewall rules…

I’m using Comodo Firewall Pro 3 on Windows XP Pro SP2 (and McAfee VirusScan Enterprise 8.5.0i).


Do you know if you need an incoming connection, only outgoing, both directions?

Also, is there a specific application you know that it uses to connect? If there is then we can work an app rule (probably best way to go).

Alternatively you could always switch the firewall into custom policy mode in the advanced->behavior section, sort through all the pop ups (provided they all haven’t already been set), and fire up the connect and then allow it whenever you need it, or remember allow it so you don’t have to keep allowing it (you can always get rid of the rule later if you need).

Thanks so much.

I’ve asked the isp for an answer to your first question (Do you know if you need an incoming connection, only outgoing, both directions?), but I think (and I really could be wrong!) that I only need an outgoing connection. I don’t think the CPanel needs to connect back to me.

As for your second question, the only application that is involved is the CPanel application on the server at the webhost (but again, I could be very wrong!) The only application that I use is my web browser - I tried both Firefox 2 and IE7 with the same results on both.

I was able to establish an ftp connection from UltraEdit (my html/text editor) and upload a .php & .html page to the site. The .php page contained the PhpInfo() command and it displayes correctly in my browser.

I tried connecting to my site from my office computer - which isn’t running Comodo - and I get the same CPanel connection problem! The only applications that the the two computers have in common is that they are both running McAfee VirusScan Enterprise 8.5.0i. I’m beginning to wonder if it could be McAfee that could be causing the problem???

I will try your other suggestion (switch the firewall into custom policy mode) this evening.


Don’t thank me yet, I don’t know much, but I’ll try and help and am glad you’ve found a work around in the meanwhile. I don’t know much about McAfee, but then again I don’t see why it’s blocking your connection if it’s a antivirus (does it have some kind of firewall capability or something). Well you could always test by shutting down mcafee temporarily and trying the connection. Try the one without comodo first and then the comodo machine.

Okay now we have an application, can you fire up your logs (view firewall logs) and then click on more, and tell me if there are any reports for firefox?

In the meanwhile. Lets see about outgoing.

So, lets try firefox first, can you tell me what rule is currently defined for firefox in applications. Go to advanced, network security policy (did you use a custom or predefined is what I’m getting at). I usually just predefine the thing as web browser without any problems. Basically, highlight the firefox entry and hit edit.

Okay, what we’re going to do is set it to custom policy mode, and copy whatever predefined policy you have, if you’re using a predefined (In my case, I would set it to custom->copy from->predefined->web browser). Okay you’ll get a bunch of allows (greens), which aren’t really important to us at this point, but the significant ones are the blocks (red). We’re basically going to set a new allow for firefox to connect to that specific port. Click on add and you’ll get a new pop up for the specifics.

-Obviously we’ll want it to allow
-TCP or UDP if you don’t know the type, if you know the specific type then by all means define it. The stricter we can make this the better for security.
-For direction you’ll want an out
-Description you can type anything in to help remember what this is for, you can use “Cpanel” for example
-You can leave the source IP as is, since that’s going to be you because we already defined this thing as outgoing, and destination IP as is as well, unless you know how to set host names and the like (I don’t, sorry).
-Source Port, if you know the specific port this thing goes out from, by all means set a source. Destination port is 2082.

Okay now that we have this rule, you have to make sure it’s above any block rules. Comodo uses a top down approach, so in my case since I use a web browser policy there’s a block all at the end. Basically had I placed any new rule after the block all, the block all would void them. Just highlight the new rule and press move up until it clears the blocks.

Tell your web hosting provider to use cPanel 11.23 or later. In 11.23, you can login to cPanel/WHM over port 80 by going to:

Where is your domain.

Thanks for the replies guys. I managed to fix the problem - and it wasn’t caused by the Comodo Firewall or McAfee VirusScan. My router actually has it’s own built-in firewall and I just had to open port 2082 in there. When I did that I was able to access the CPanel on my website.

Thanks for the help… :■■■■

Ah heh, well glad to see you’ve worked it out.