DreamPhysix

Well-Known Member
Sep 30, 2009
78
0
56
I installed cpanel dnsonly on my centos 5.5 64-bit server and the network is configured for an external ip address, but when I try to access the web interface at port 2086 or 2087, it can't be found. I can still connect to the server via ssh. Any suggestions?
 

DreamPhysix

Well-Known Member
Sep 30, 2009
78
0
56
Try also :
[email protected] [~]# service cpanel start
Starting cPanel services: [ OK ]
Starting cPanel brute force detector services: [ OK ]
Starting cPanel dav services: [ OK ]
Starting pop3 services:
Starting cPanel Chat services:
Starting Melange Chat services:
Starting cPanel ssl services: Using Native SSL support (stunnel not needed)
[ OK ]
Starting cPanel Queue services: [ OK ]
Starting tailwatchd:
Starting cPanel Log services: /bin/bash: /usr/local/cpanel/cpanellogd: No such file or directory
[FAILED]
Starting mailman services: [ OK ]
 

cPanelTristan

Quality Assurance Analyst
Staff member
Oct 2, 2010
7,607
40
248
somewhere over the rainbow
cPanel Access Level
Root Administrator
Prior to stopping iptables, why not just check what rules it is loading?

Code:
/sbin/iptables -n -L
If port 2086 and 2087 aren't allowed, you can run this command to add them:

Code:
/sbin/iptables -I INPUT -p tcp -m tcp --dport 2086:2087 -j ACCEPT
After doing that command if it does work to allow access to WHM, then save the configuration:

Code:
service iptables save
I oftentimes wonder why people don't encourage checking the existing rules and whitelisting the ports first rather than shutting down the firewall. When the firewall is down, you aren't protected any longer. It seems more preferred to actually look at the rules and then add the exact port you need whitelisted over shutting the whole thing down initially. If that doesn't work and you still suspect the firewall, then by all means shut it down temporarily or flush it temporarily.
 

LinuxTechie

Well-Known Member
Jan 22, 2011
502
10
68
cPanel Access Level
Root Administrator
Prior to stopping iptables, why not just check what rules it is loading?

Code:
/sbin/iptables -n -L
If port 2086 and 2087 aren't allowed, you can run this command to add them:

Code:
/sbin/iptables -I INPUT -p tcp -m tcp --dport 2086:2087 -j ACCEPT
After doing that command if it does work to allow access to WHM, then save the configuration:

Code:
service iptables save
I oftentimes wonder why people don't encourage checking the existing rules and whitelisting the ports first rather than shutting down the firewall. When the firewall is down, you aren't protected any longer. It seems more preferred to actually look at the rules and then add the exact port you need whitelisted over shutting the whole thing down initially. If that doesn't work and you still suspect the firewall, then by all means shut it down temporarily or flush it temporarily.
Hey Tristan,

It is not like we aren't aware of Firewall. It is just for testing I asked him to stop iptables and check again. If that is the issue, then only we have to whitelist the ports in the firewall. In this case the customer sent me a PM and I have also sent him the rules to accept the Ports. Please don't misunderstand.
 

cPanelTristan

Quality Assurance Analyst
Staff member
Oct 2, 2010
7,607
40
248
somewhere over the rainbow
cPanel Access Level
Root Administrator
No worries, but people who stop the firewall don't always remember to restart the firewall. Stopping the firewall should be the last resort after checking the rules, then whitelisting the ports.