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.

web site problem

Discussion in 'General Discussion' started by yanirda, Dec 1, 2011.

  1. yanirda

    yanirda Registered

    Joined:
    Dec 1, 2011
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Root Administrator
    i have just install a fresh installation of cpnanel
    the install cd was from the cpanel site,
    the cpanel built in installation with centos

    the cpanel and the whm working

    i can enter the port 2083 and 2087
    but i build a site and i cant make ftp to it, the connectin refuse

    same as the 80\http port i cant view the site..

    what is the problem??

    my site public ip :
    212.29.253.72

    my privat ip:
    10.16.0.100

    both cant have telnet in 80 or 21..

    please give me a help..

    i dont where is the problem...


    in iis on windows it is so simple.....


    thnx in advance...
     
  2. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,678
    Likes Received:
    651
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    Hello :)

    Please ensure you do not have any firewall rules that could be blocking access to the FTP or Apache services. You can do so via a command such as:

    Code:
    # iptables -L
    If there are rules there, you may want to temporarily stop the "iptables" service to see if that allows access to FTP or Apache:

    Code:
    # /sbin/service iptables stop
    Thank you.
     
  3. yanirda

    yanirda Registered

    Joined:
    Dec 1, 2011
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Root Administrator
    thank you for replay ,

    i do it and receve:

    root@server [~]# iptables -L
    Chain INPUT (policy ACCEPT)
    target prot opt source destination
    acctboth all -- anywhere anywhere
    Chain FORWARD (policy ACCEPT)
    target prot opt source destination
    Chain OUTPUT (policy ACCEPT)
    target prot opt source destination
    acctboth all -- anywhere anywhere
    Chain acctboth (2 references)
    target prot opt source destination
    root@server [~]# /sbin/service iptables stop
    Flushing firewall rules: [ OK ]
    Setting chains to policy ACCEPT: filter [ OK ]
    Unloading iptables modules: [ OK ]
    root@server [~]#


    but i still cant connect with ftp,
    telnet to 21 is refuse...

    telnet port 80 is open,
    but when i try to surf i cant get the page...


    please help...
     
  4. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,678
    Likes Received:
    651
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    Hello :)

    I suggest opening a support ticket with our staff so we can login and investigate further:

    Submit A Ticket

    You can post the ticket number here so we may track the issue.

    Thank you.
     
  5. cPanne

    cPanne Member
    Staff Member

    Joined:
    Oct 4, 2011
    Messages:
    7
    Likes Received:
    0
    Trophy Points:
    1
    Location:
    Cypress, Texas, United States
    cPanel Access Level:
    Website Owner
    There is a firewall between your server and the Internet.

    I can only connect via ssh. I can not connect to WHM, cPanel or httpd on your public ip.

    It would seem that your Data Center has a firewall in place that is preventing access to these ports.

    This issue must be addressed by your Data Center.

    Here are the ports that should be opened for cPanel to work:

    Linux FAQ

    Ports that must be open to run cPanel behind a firewall:

    20 — FTP TCP inbound/outbound
    21 — FTP TCP, UDP inbound/outbound
    22 — SSH TCP inbound
    25 — SMTP TCP inbound/outbound
    26 — SMTP TCP inbound/outbound
    37 — rdate TCP outbound
    43 — whois TCP outbound
    53 — DNS TCP/UDP inbound/outbound
    (inbound is only needed if you run your own public DNS server)
    80 — HTTP TCP inbound/outbound
    110 — POP3 TCP inbound
    113 — ident TCP outbound
    143 — IMAP4 TCP inbound
    443 — HTTPS TCP inbound
    465 — SMTP TLS/SSL TCP/UDP inbound/outbound
    783 — SpamAssassin TCP/UDP inbound
    873 — rsync TCP/UDP outbound
    993 — IMAP4 SSL TCP inbound
    995 — POP3 SSL TCP inbound
    2077 — WebDAV TCP/UDP inbound/outbound
    2078 — WebDAV SSL TCP/UDP inbound/outbound
    2082 — cPanel TCP inbound
    2083 — cPanel SSL TCP inbound
    2086 — WHM TCP inbound
    2087 — WHM SSL TCP inbound
    2089 — cPanel license TCP outbound
    2095 — Webmail TCP inbound
    2096 — Webmail SSL TCP inbound
    3306 — MySQL TCP (only if you need to connect remotely)
    6666 — Chat TCP inbound

    Please check with your Data Center and let us know when those ports have been opened for your ips.

    Best Regards,
     
  6. cPanelTristan

    cPanelTristan Quality Assurance Analyst
    Staff Member

    Joined:
    Oct 2, 2010
    Messages:
    7,623
    Likes Received:
    21
    Trophy Points:
    38
    Location:
    somewhere over the rainbow
    cPanel Access Level:
    Root Administrator
    Also, given you mention a private IP, it might well be your NAT setup isn't properly translating the private IP to the public one. That is also something your datacenter or NOC would need to investigate. It seems unlikely that is the case when ports 2083 and 2087 are working, but in case there is any type of routing issue going on beside a firewal, it would be something to keep in mind when speaking with the dataceter or NOC.
     
  7. yanirda

    yanirda Registered

    Joined:
    Dec 1, 2011
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Root Administrator
    all the port was open!!

    i event submit a ticket no:2044773

    the problem isnt solve
    the cpanel and the wHM working..

    why the site isnt???
     
  8. amw3000

    amw3000 Member

    Joined:
    Aug 22, 2010
    Messages:
    21
    Likes Received:
    0
    Trophy Points:
    1
    We will need some more information.

    1. What type of firewall do you have and who manages it?
    2. Does it work locally? From the server, are you able to telnet into port 80? 21? If it works locally, its most likely a NAT or firewall issue.
     
  9. cPanelTristan

    cPanelTristan Quality Assurance Analyst
    Staff Member

    Joined:
    Oct 2, 2010
    Messages:
    7,623
    Likes Received:
    21
    Trophy Points:
    38
    Location:
    somewhere over the rainbow
    cPanel Access Level:
    Root Administrator
    The issue was already indicated in ticket 2044773. Your machine doesn't have ports 953 and 53 opened for TCP and UDP traffic. Because of this, your named service cannot respond for DNS requests for the site. You can either take your firewall down entirely to open all ports, or you can open the applicable ports needed in the firewall for 953 and 53 for TCP and UDP traffic.
     
Loading...

Share This Page