Skip to main content

2087 refused

Comments

6 comments

  • vanessa
    May just be a language barrier here, but I'm having trouble understanding the question. Are you saying that you can access WHM through a browser, but not through telnet?
    0
  • cPanelMichael
    Hello :) Check to see if you have any default iptables firewall rules installed that could be blocking access to port 2087. Note that you may want to consider using a third-party firewall management tool such as CSF if you are new to firewall rules. Thank you.
    0
  • mahesh123
    Dear sir please once check it .....sir root@gd [~]# vi /etc/sysconfig/iptables # Generated by iptables-save v1.4.7 on Tue Apr 22 14:36:54 2014 *filter :INPUT ACCEPT [14500:3285229] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [20569:7020219] :acctboth - [0:0] :cP-Firewall-1-INPUT - [0:0] -A INPUT -j cP-Firewall-1-INPUT -A FORWARD -j cP-Firewall-1-INPUT -A OUTPUT -j acctboth -A cP-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp --dport 993 -j ACCEPT -A cP-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp --dport 2078 -j ACCEPT -A cP-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp --dport 53 -j ACCEPT -A cP-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp --dport 21 -j ACCEPT -A cP-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp --dport 2082 -j ACCEPT -A cP-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp --dport 443 -j ACCEPT -A cP-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp --dport 2077 -j ACCEPT -A cP-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp --dport 80 -j ACCEPT -A cP-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp --dport 26 -j ACCEPT -A cP-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp --dport 8080 -j ACCEPT -A cP-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp --dport 143 -j ACCEPT -A cP-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp --dport 22 -j ACCEPT -A cP-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp --dport 995 -j ACCEPT -A cP-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp --dport 110 -j ACCEPT -A cP-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp --dport 25 -j ACCEPT -A cP-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp --dport 2086 -j ACCEPT -A cP-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp --dport 2087 -j ACCEPT -A cP-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp --dport 2095 -j ACCEPT -A cP-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp --dport 465 -j ACCEPT -A cP-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp --dport 2096 -j ACCEPT -A cP-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp --dport 3306 -j ACCEPT -A cP-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp --dport 2083 -j ACCEPT -A cP-Firewall-1-INPUT -p udp -m state --state NEW -m udp --dport 53 -j ACCEPT COMMIT # Completed on Tue Apr 22 14:36:54 2014 # Generated by iptables-save v1.4.7 on Tue Apr 22 14:36:54 2014 *nat :PREROUTING ACCEPT [1427:77525] :POSTROUTING ACCEPT [166:10350] :OUTPUT ACCEPT [166:10350] COMMIT
    Thank you [COLOR="silver">- - - Updated - - - [quote="vanessa, post: 1627072">May just be a language barrier here, but I'm having trouble understanding the question. Are you saying that you can access WHM through a browser, but not through telnet?
    .. sry vanesssa My English very hard .....
    0
  • cPanelMichael
    Have you considered using a third-party firewall management tool such as CSF? Or, have you temporarily stopped the iptables service to see if the issue continues? Note that third-party firewall rules fall outside our scope of support. Thank you.
    0
  • mahesh123
    yes .. i am not using csf firewall ..and i given command to server.. service iptables stop .. but getting same issue ..please help me sir Thank you
    0
  • cPanelMichael
    Feel free to open a support ticket using the link in my signature so we can take a closer look. You can post the ticket number here so we can update this thread with the outcome. Thanks.
    0

Please sign in to leave a comment.