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.

[help!] Oh no :( I broke WHM. Page not displayed.

Discussion in 'General Discussion' started by missione, Jun 6, 2006.

  1. missione

    missione Registered

    Joined:
    Jun 5, 2006
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    1
    Well I was configuring my business's new web server, tweaking with settings in whm, DNS, apache, nameservers, added IPs, etc. Everything seemed to be working. THEN I decided to reboot the box. Ever since I rebooted, mydomain/whm will no longer come up, (page not displayed).

    I've already tried these things:

    * Shelled in and verified that HTTPD and CPSRVD were running, they are.
    * Killed the cpanel file and did the ./cleanmd5 ./upcp bit to reinstall cpanel.
    * Rebooted about 5 more times.
    * Tried to connect using the server's IP, and using :2087 instead of /whm, same thing.
    * If I go to my domain by itself, I get the normal no site cpanel error page!
    * I shelled in and tried to LYNX to /whm locally just to see if it would even connect, AND IT DID!!! (got an HTTP Auth message).

    Something is preventing remote access it seems? Any suggestions would really help, as I am running out of ideas.

    Another point that could possibly be related is that before I rebooted I rebuilt apache via the whm page, turning on serveral additional modules. HTTPD is clearly running right now, so I'm not sure what to do.

    Thanks!!!
     
  2. chirpy

    chirpy Well-Known Member

    Joined:
    Jun 15, 2002
    Messages:
    13,475
    Likes Received:
    20
    Trophy Points:
    38
    Location:
    Go on, have a guess
    You most likely have some kind of rudimentary iptables firewall installed. Try:

    iptables -L -n

    If it's got port restrictions in it and you haven't installed a firewall configuration script, then check in /etc/sysconfig/iptables

    If that has port restrictions in it, there's the problem. A simple fix is to:

    service iptables stop
    service iptables save
    service iptables start
     
  3. missione

    missione Registered

    Joined:
    Jun 5, 2006
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    1
    I love you Chirpy!! That was it!

    Clearing the IP tables was something I did before, but I didn't realize they had to be 'saved', and so then i rebooted....makes sense!

    Thanks!!
     
Loading...

Share This Page