Please whitelist cPanel in your adblocker so that you’re able to see our version release promotions, thanks!

The Community Forums

Interact with an entire community of cPanel & WHM users!

Poblem to create an Account for whm

Discussion in 'General Discussion' started by tanota, Aug 20, 2011.

  1. tanota

    tanota Member

    Joined:
    Aug 19, 2011
    Messages:
    9
    Likes Received:
    0
    Trophy Points:
    51
    Hello. I tell them I'm pretty novice with whm dedicated and the problem I have is that when I create an Account with any domain, all domains are redirected to "/ cgi-sys/defaultwebpage.cgi" but depending on the account goes correctly, FTP, SQL, panel, etc..
    The server is brand new so it has 2 single Account
    I expect prompt replies.

    Greetings!
     
  2. cPanelTristan

    cPanelTristan Quality Assurance Analyst
    Staff Member

    Joined:
    Oct 2, 2010
    Messages:
    7,609
    Likes Received:
    32
    Trophy Points:
    238
    Location:
    somewhere over the rainbow
    cPanel Access Level:
    Root Administrator
    Without knowing what one of the specific domains that isn't working happens to be for us to check the DNS entries to see if they exist or are properly setup, it isn't possible to be certain exactly how to correct the issue.

    Usually a domain will not show up in a browser properly and show the default Apache page instead for the following reasons:

    1. The domain's IP A record in the DNS zone doesn't match the Apache /usr/local/apache/conf/httpd.conf IP listed for the domain's VirtualHost entry (a dig can be checked on the domain to see the DNS A record versus checking the httpd.conf entry for the domain)

    2. The user visiting the domain is cached to the prior location for the domain and not going to the right location (a proxy can be checked such as proxify.net or kproxy.con to see if this is the case)

    3. A NAT is being used where the server uses backend 192.x.x.x IPs and the Apache entry contains the frontend IP rather than the NAT IP, since Apache doesn't know how to handle the frontend IP due to using the backend IP, it cannot then show the correct location

    4. For some reason Apache didn't restart properly when the domain was added, which means the new httpd.conf didn't get loaded (restarting Apache would correct this issue)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Loading...

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice