cPanel installation

[Shef]

I installed cPanel,


2012-04-11 20:33:50 1762 ( INFO): Done
2012-04-11 20:33:50 236 ( INFO): cPanel install finished in 193 minutes and 37 seconds!

and it doesn't work when I put the IP in the browsers address:

IP(put servers IP here):2087

Any idea why?

[Infopro]

Did you make sure the firewall was disabled before running the installer?

This might be helpful:

Deactivating the firewall - cPanel Documentation

[Shef]

I dont think it comes with a firewall. My server is unmanaged. But if it does have it, do I need to reinstall the os since I already installed cPanel?

[thewebhosting]

Do you have CentOS distribution installed?

CentOS has default firewall rules that block access to cPanel ports. You can flush them with `iptables -F`. Also, remove them from /etc/sysconfig/iptables to prevent them coming back on a system reboot or service restart.

[cPanelTristan]

Hello,

Generally speaking, it isn't advisable to flush the firewall and be left without any rules at all. Rather than doing that, you might consider getting CSF:

ConfigServer Security & Firewall

Here's a post on how to install CSF for cPanel:

http://forums.cpanel.net/f185/china-...tml#post928932
It would open up the necessary ports for cPanel, WHM, webmail and so on. Otherwise, if you don't want to have a firewall to protect unused ports from attack, then at the very least don't edit /etc/sysconfig/iptables directly after flushing the firewall. Simply issue this command after you've cleared the rules:

service iptables save

That will save the new rules, which are basically no rules. If you edit /etc/sysconfig/iptables directly, you could end up causing iptables to not even function at all and, later on, if you wanted to use a firewall, you'd then not be able to get it working.

Thanks!

[Shef]

Do you have CentOS distribution installed?

CentOS has default firewall rules that block access to cPanel ports. You can flush them with `iptables -F`. Also, remove them from /etc/sysconfig/iptables to prevent them coming back on a system reboot or service restart.

CentOS distribution? Not sure, I got CentOS though.

I re-installed cPanel and I updated it and still can't access it.

[Shef]

root@server [~]# iptables -L -n -v
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
75489 101M acctboth all -- * * 0.0.0.0/0 0.0.0.0/0
75489 101M RH-Firewall-1-INPUT all -- * * 0.0.0.0/0 0.0.0.0/0
0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:993
0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:2078
0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:53
0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:21
0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:2082
0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:443
0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:2077
0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:80
0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:26
0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:8080
0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:143
0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:22
0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:995
0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:110
0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:25
0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:2086
0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:2087
0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:2095
0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:465
0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:2096
0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:3306
0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:2083
0 0 ACCEPT udp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW udp dpt:53

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
0 0 RH-Firewall-1-INPUT all -- * * 0.0.0.0/0 0.0.0.0/0

Chain OUTPUT (policy ACCEPT 40795 packets, 4231K bytes)
pkts bytes target prot opt in out source destination
40795 4231K acctboth all -- * * 0.0.0.0/0 0.0.0.0/0

Chain RH-Firewall-1-INPUT (2 references)
pkts bytes target prot opt in out source destination
1398 227K ACCEPT all -- lo * 0.0.0.0/0 0.0.0.0/0
1 28 ACCEPT icmp -- * * 0.0.0.0/0 0.0.0.0/0 icmp type 255
0 0 ACCEPT esp -- * * 0.0.0.0/0 0.0.0.0/0
0 0 ACCEPT ah -- * * 0.0.0.0/0 0.0.0.0/0
0 0 ACCEPT udp -- * * 0.0.0.0/0 224.0.0.251 udp dpt:5353
0 0 ACCEPT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpt:631
0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:631
70790 100M ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED
2 100 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:22
3298 482K REJECT all -- * * 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited

Chain acctboth (2 references)
pkts bytes target prot opt in out source destination
0 0 tcp -- !lo * IP Hidden 0.0.0.0/0 tcp dpt:80
0 0 tcp -- !lo * 0.0.0.0/0 IP Hidden tcp spt:80
0 0 tcp -- !lo * IP Hidden 0.0.0.0/0 tcp dpt:25
0 0 tcp -- !lo * 0.0.0.0/0 IP Hidden tcp spt:25
0 0 tcp -- !lo * IP Hidden 0.0.0.0/0 tcp dpt:110
0 0 tcp -- !lo * 0.0.0.0/0 IP Hidden tcp spt:110
10 776 icmp -- !lo * IP Hidden 0.0.0.0/0
0 0 icmp -- !lo * 0.0.0.0/0 IP Hidden
40 5016 tcp -- !lo * IP Hidden 0.0.0.0/0
50 4752 tcp -- !lo * 0.0.0.0/0 IP Hidden
20 1593 udp -- !lo * IP Hidden 0.0.0.0/0
20 2421 udp -- !lo * 0.0.0.0/0 IP Hidden
70 7385 all -- !lo * 76.73.109.82 0.0.0.0/0
70 7173 all -- !lo * 0.0.0.0/0 76.73.109.82
208 24680 all -- !lo * 0.0.0.0/0 0.0.0.0/0
root@server [~]#

That's my firewall.

[thewebhosting]

Have you restarted your server after re-installing cPanel? please try out.

Also, check in cPanel logs to see if there is any error while installation. The location of cPanel error logs is /usr/local/cpanel/error_logs

[cPanelTristan]

It appears the rules to open the ports in the INPUT chain right now might be prevented from loading due to this line occurring before them:

75489 101M RH-Firewall-1-INPUT all -- * * 0.0.0.0/0 0.0.0.0/0

In that chain, this line in the firewall is blocking cPanel functioning if that's the case:

3298 482K REJECT all -- * * 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited

If that is what is happening, you'd need to add the cPanel ports and any others that need to be opened (such as port 25 for email) before it passes to the other chain:

/sbin/iptables -I INPUT -p tcp -m tcp --dport 2082:2083 -j ACCEPT
/sbin/iptables -I INPUT -p tcp -m tcp --dport 2086:2087 -j ACCEPT
/sbin/iptables -I INPUT -p tcp -m tcp --dport 2095:2096 -j ACCEPT
/sbin/iptables -I INPUT -p tcp -m tcp --dport 25 -j ACCEPT

Those are just some of the ports. You can see the full list in that INPUT chain such as port 53 tcp and udp and so on. You can always try flushing the firewall temporarily (without saving the firewall) to see if you can access WHM then. If you can, it is what I've stated above just now and you'd need to add the rules. Alternatively, you could use CSF instead as previously mentioned. It provides a firewall that typically is better configured than the default RedHat one, since it provides brute force detection with LFD with it.

[Shef]

It appears the rules to open the ports in the INPUT chain right now might be prevented from loading due to this line occurring before them:

75489 101M RH-Firewall-1-INPUT all -- * * 0.0.0.0/0 0.0.0.0/0

In that chain, this line in the firewall is blocking cPanel functioning if that's the case:

3298 482K REJECT all -- * * 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited

If that is what is happening, you'd need to add the cPanel ports and any others that need to be opened (such as port 25 for email) before it passes to the other chain:

/sbin/iptables -I INPUT -p tcp -m tcp --dport 2082:2083 -j ACCEPT
/sbin/iptables -I INPUT -p tcp -m tcp --dport 2086:2087 -j ACCEPT
/sbin/iptables -I INPUT -p tcp -m tcp --dport 2095:2096 -j ACCEPT
/sbin/iptables -I INPUT -p tcp -m tcp --dport 25 -j ACCEPT

Those are just some of the ports. You can see the full list in that INPUT chain such as port 53 tcp and udp and so on. You can always try flushing the firewall temporarily (without saving the firewall) to see if you can access WHM then. If you can, it is what I've stated above just now and you'd need to add the rules. Alternatively, you could use CSF instead as previously mentioned. It provides a firewall that typically is better configured than the default RedHat one, since it provides brute force detection with LFD with it.

That did the trick.

I'm getting flooded in my email with this:

lfd failed @ Fri Apr 13 07:50:47 2012. A restart was attempted automagically.

Service Check Method: [check command]

Number of Restart Attempts: 86

[cPanelTristan]

CSF and LFD aren't our services, so if you did install CSF and LFD is failing, please post on their forum:

CSF Forum