sites-enabled file naming

Discussion in 'Installation/Configuration' started by gilas, Nov 22, 2011.

  1. gilas

    gilas New Member

    Hello
    always thank you for your precious work.

    I have a little problem, or better "annoying" problem.

    For unknown reason my server has not configured with a "server certificate" (speaking of Debian Lenny).

    Looking in another server (CentOS) I discovered a SSL certificate stored in this folder: /etc/httpd/ssl. It seems that the certs store in ssl folder are used for all my web sites if activated SSL option. This sound good.

    But the first server (Debian) have a different behavior. Probabilly the server cant find the SSL certs so that I discovered that apache uses the first site from the folder:

    /etc/apache2/sites-enabled

    i.e. all sites with the name starting with 000- doesn' respect this, so that the first site used for the SSL Certificate (for the other sites) is the first found in alphabetical order. I.e.:

    100-www.site1.com
    100-www.site2.com
    100-www.site3.com

    this mean that if I create a new site, I will have:

    100-www.site1.com
    100-www.site2.com
    100-www.site3.com
    www.newsite.com

    (note: without 100- prefix!)

    but when I modify the site 'newsite.com' I will have:
    100-www.newsite.com
    100-www.site1.com
    100-www.site2.com
    100-www.site3.com

    as you can see newsite is at beginning so that the (new) SSL cert is not taken from 100-www.site1.com but from 100-www.newsite.com.

    I can't understant what is the modification todo to:
    * write the server certificate and where and which lines put into (I suppose) into apache config files...
    * if (and ....why?) ISPConfig needs to rename the files above.

    thank you very much for your help
     
  2. till

    till Super Moderator

    If this folder contains ssl certs, then these are not created nor used by ispconfig. The ssl certs of a website in ispconfig are stored in the ssl folder of that site.

    So that might be the reason for your problem. If ssl is not configured for a website in ispconfig, then the ssl cert is not configured in the vhost file and apache will deliver the content of the first vhost that it finds on the same IP address.

    Sites are still in alphabetical order as before, they just have a prefix now as wildcard subdomains wont work correctly otherwise. See release notes:

    http://bugtracker.ispconfig.org/index.php?do=details&task_id=1653

    ISPConfig website vhost files dont start with 000- prefix. The 000-prefix is reserved for the ispconfig controlpanel vhost on port 8080, the apps vhost and the default files of the Linux distribution.
     
    Last edited: Nov 22, 2011

Share This Page