The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

2087 refused

Discussion in 'General Discussion' started by mahesh123, Apr 22, 2014.

  1. mahesh123

    mahesh123 Well-Known Member

    Joined:
    Nov 2, 2013
    Messages:
    50
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    india
    cPanel Access Level:
    Root Administrator
    Dear cpanel experts

    root@Cpanel [~]# telnet 103.15.xx.xx 2087
    Trying 103.15.xx.xx...
    telnet: connect to address 103.15.xx.xx: Connection refused

    But we getting https://103.15.xx.xx:2087
    but displaying whmcpanel


    please help me

    Thank you
     
  2. vanessa

    vanessa Well-Known Member
    PartnerNOC

    Joined:
    Sep 26, 2006
    Messages:
    817
    Likes Received:
    22
    Trophy Points:
    18
    Location:
    Virginia Beach, VA
    cPanel Access Level:
    DataCenter Provider
    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?
     
  3. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,854
    Likes Received:
    676
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    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.
     
  4. mahesh123

    mahesh123 Well-Known Member

    Joined:
    Nov 2, 2013
    Messages:
    50
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    india
    cPanel Access Level:
    Root Administrator
    Dear sir

    please once check it .....sir

    Code:
    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

    - - - Updated - - -

    ..

    sry vanesssa My English very hard .....
     
  5. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,854
    Likes Received:
    676
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    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.
     
  6. mahesh123

    mahesh123 Well-Known Member

    Joined:
    Nov 2, 2013
    Messages:
    50
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    india
    cPanel Access Level:
    Root Administrator
    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
     
  7. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,854
    Likes Received:
    676
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    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.
     
Loading...

Share This Page