Configtest error

Discussion in 'Linux VPS/Dedicated - cPanel' started by LeMarque, Dec 3, 2008.

  1. LeMarque

    LeMarque Member

    Two questions really.

    Is there a way or an entry in http.conf that can be made so that when a new account is created in WHM either a default index.html file or an .htaccess file is created so that when you browse to the site you don't get "index of/" ?

    And lastly, running : /usr/sbin/apachectl configtest

    returns an error :

    [error] VirtualHost 67.222.xx.xxx:0 -- mixing * ports and non-* ports with a NameVirtualHost address is not supported, proceeding with undefined results
    Syntax OK

    Don't have a clue as to what that means.
     
  2. Wired Techie

    Wired Techie New Member

    Others please correct me if I am wrong here but I think this can be configured in WHM somewhere, however, I do know for certain that this can be configured via the domain's own cpanel interface as I've had to turn it off myself a few times.


    Well, neither do I. Oh well, at least you got one question answered and I'll take a an educated guess at the second question:

    Have you actually created your main domain in WHM yet? I'm talking about the one you signed up with and is your server name also set in WHM?

    Sounds like it's missing a NameVirtualHost directive (which SHOULD be taken care of after the first account is created in WHM.

    Am I close folks? :)

    Jeff
     
  3. Dan

    Dan Moderator

    Hello LeMarque,

    For your first question you can put some files into the skeleton directory which you will find at /root/cpanel3-skel in there you'll see the public_ftp and public_html. Put whatever files you want to be populated to new accounts in the public_html directory and you'll be good to go.

    For your httpd.conf problem have you made modifications to this file? Might help if you paste your virtualhost section here too although I'm not sure I could figure out what was wrong but perhaps someone else could.
     
  4. LeMarque

    LeMarque Member

    Thanks guys

    I'll post the http.conf later today. Playing catchup after the time off for Thanksgiving.
     
  5. LeMarque

    LeMarque Member

    Re the httpd.conf file, support reloaded Apache and that took care of the config error.
     

Share This Page