Wildcard SSL certificates + ISPConfig?

Discussion in 'General' started by Xenocide, Dec 6, 2010.

  1. Xenocide

    Xenocide Member

    Hi Guys,

    We've got a wildcard ssl certificate to use with some of the sites on our server.

    So we've got:


    and ssl cerficiates for (for example)..

    How would we add these in ISPconfig? Alias domains are not shown in the drop down when you select which site you want securing.

  2. till

    till Super Moderator Staff Member ISPConfig Developer

    Thats not a problem as they are not relevant for serving ssl sites, thhey are only used to create a new ssl certificate. As you have already a ssl cert, the selcted ssl domain does not matter.
  3. Xenocide

    Xenocide Member

    Ahh yes ofcourse i hadn't considered that. Just ip and away you go I guess. Cheers yet again till. I'm going to paint a picture of you and hang you on my wall.
  4. Xenocide

    Xenocide Member

    Sorry, Till. One more question. I can't find it mentioned in the manual. The IP addresses that you add in system->IP addresses. Should they be the public IP's or the internal IPs if they're natted?

    I'm guessing internal but just wanted to check. :)
  5. till

    till Super Moderator Staff Member ISPConfig Developer

    Inside a NAT enviroment, you use internal IP addresses for websites and external IP addresses for DNS records.
  6. Xenocide

    Xenocide Member

    Hi, sorry there seems to be something weird here.

    I had an error which said that localhost.localdomain isn't the correct certificate for the requested hostname so i moved /etc/conf/ssl.conf which is default centos installation and restarted httpd.

    I added the site in ispconfig with the server in debug mode and in the log you can see that it's creating the ssl cert it /var/www/site.com/ssl/* and the last modified time of /etc/httpd/conf/sites-available/site.com/vhost is when the update is however there's no mention in that file of any ssl setup and running netstat shows httpd isn't listening on 443.

    The file is thus:

    <Directory /var/www/sitea.com>
        AllowOverride None
        Order Deny,Allow
        Deny from all
        DocumentRoot /var/www/clients/client83/web106/web
        ServerName sitea.com
        ServerAlias *.sitea.com
        ServerAlias sitea.ssldomain.com
        ServerAdmin [email protected]
        ErrorLog /var/log/ispconfig/httpd/sitea.com/error.log
        ErrorDocument 400 /error/400.html
        ErrorDocument 401 /error/401.html
        ErrorDocument 403 /error/403.html
        ErrorDocument 404 /error/404.html
        ErrorDocument 405 /error/405.html
        ErrorDocument 500 /error/500.html
        ErrorDocument 503 /error/503.html
        <Directory /var/www/sitea.com/web>
            Options FollowSymLinks
            AllowOverride All
            Order allow,deny
            Allow from all
        <Directory /var/www/clients/client83/web106/web>
            Options FollowSymLinks
            AllowOverride All
            Order allow,deny
            Allow from all
        # suexec enabled
        SuexecUserGroup web106 client83
        # Clear PHP settings of this website
        <FilesMatch "\.ph(p3?|tml)$">
            SetHandler None
        # suphp enabled
        <Directory /var/www/clients/client83/web106/web>
                    <IfModule mod_suphp.c>
            suPHP_Engine on
            # suPHP_UserGroup web106 client83
            AddHandler x-httpd-suphp .php .php3 .php4 .php5
            suPHP_AddHandler x-httpd-suphp
        # add support for apache mpm_itk
        <IfModule mpm_itk_module>
          AssignUserId web106 client83
        <IfModule mod_dav_fs.c>
          # WEBDAV BEGIN
          # WEBDAV END
    FYI here is ssl.conf (which isn't being used by apache now)

    # This is the Apache server configuration file providing SSL support.
    # It contains the configuration directives to instruct the server how to
    # serve pages over an https connection. For detailing information about these
    # directives see <URL:http://httpd.apache.org/docs/2.2/mod/mod_ssl.html>
    # Do NOT simply read the instructions in here without understanding
    # what they do.  They're here only as hints or reminders.  If you are unsure
    # consult the online docs. You have been warned.
    LoadModule ssl_module modules/mod_ssl.so
    # When we also provide SSL we have to listen to the
    # the HTTPS port in addition.
    Listen 443
    ##  SSL Global Context
    ##  All SSL configuration in this context applies both to
    ##  the main server and all SSL-enabled virtual hosts.
    #   Some MIME-types for downloading Certificates and CRLs
    AddType application/x-x509-ca-cert .crt
    AddType application/x-pkcs7-crl    .crl
    #   Pass Phrase Dialog:
    #   Configure the pass phrase gathering process.
    #   The filtering dialog program (`builtin' is a internal
    #   terminal dialog) has to provide the pass phrase on stdout.
    SSLPassPhraseDialog  builtin
    #   Inter-Process Session Cache:
    #   Configure the SSL Session Cache: First the mechanism
    #   to use and second the expiring timeout (in seconds).
    #SSLSessionCache        dc:UNIX:/var/cache/mod_ssl/distcache
    SSLSessionCache         shmcb:/var/cache/mod_ssl/scache(512000)
    SSLSessionCacheTimeout  300
    #   Semaphore:
    #   Configure the path to the mutual exclusion semaphore the
    #   SSL engine uses internally for inter-process synchronization.
    SSLMutex default
    #   Pseudo Random Number Generator (PRNG):
    #   Configure one or more sources to seed the PRNG of the
    #   SSL library. The seed data should be of good random quality.
    #   WARNING! On some platforms /dev/random blocks if not enough entropy
    #   is available. This means you then cannot use the /dev/random device
    #   because it would lead to very long connection times (as long as
    #   it requires to make more entropy available). But usually those
    #   platforms additionally provide a /dev/urandom device which doesn't
    #   block. So, if available, use this one instead. Read the mod_ssl User
    #   Manual for more details.
    SSLRandomSeed startup file:/dev/urandom  256
    SSLRandomSeed connect builtin
    #SSLRandomSeed startup file:/dev/random  512
    #SSLRandomSeed connect file:/dev/random  512
    #SSLRandomSeed connect file:/dev/urandom 512
    # Use "SSLCryptoDevice" to enable any supported hardware
    # accelerators. Use "openssl engine -v" to list supported
    # engine names.  NOTE: If you enable an accelerator and the
    # server does not start, consult the error logs and ensure
    # your accelerator is functioning properly.
    SSLCryptoDevice builtin
    #SSLCryptoDevice ubsec
    ## SSL Virtual Host Context
    <VirtualHost _default_:443>
    # General setup for the virtual host, inherited from global configuration
    #DocumentRoot "/var/www/html"
    #ServerName www.example.com:443
    # Use separate log files for the SSL virtual host; note that LogLevel
    # is not inherited from httpd.conf.
    ErrorLog logs/ssl_error_log
    TransferLog logs/ssl_access_log
    LogLevel warn
    #   SSL Engine Switch:
    #   Enable/Disable SSL for this virtual host.
    SSLEngine on
    #   SSL Protocol support:
    # List the enable protocol levels with which clients will be able to
    # connect.  Disable SSLv2 access by default:
    SSLProtocol -all +SSLv3 +TLSv1
    #   SSL Cipher Suite:
    # List the ciphers that the client is permitted to negotiate.
    # See the mod_ssl documentation for a complete list.
    #   Server Certificate:
    # Point SSLCertificateFile at a PEM encoded certificate.  If
    # the certificate is encrypted, then you will be prompted for a
    # pass phrase.  Note that a kill -HUP will prompt again.  A new
    # certificate can be generated using the genkey(1) command.
    SSLCertificateFile /etc/pki/tls/certs/localhost.crt
    #   Server Private Key:
    #   If the key is not combined with the certificate, use this
    #   directive to point at the key file.  Keep in mind that if
    #   you've both a RSA and a DSA private key you can configure
    #   both in parallel (to also allow the use of DSA ciphers, etc.)
    SSLCertificateKeyFile /etc/pki/tls/private/localhost.key
    #   Server Certificate Chain:
    #   Point SSLCertificateChainFile at a file containing the
    #   concatenation of PEM encoded CA certificates which form the
    #   certificate chain for the server certificate. Alternatively
    #   the referenced file can be the same as SSLCertificateFile
    #   when the CA certificates are directly appended to the server
    #   certificate for convinience.
    #SSLCertificateChainFile /etc/pki/tls/certs/server-chain.crt
    #   Certificate Authority (CA):
    #   Set the CA certificate verification path where to find CA
    #   certificates for client authentication or alternatively one
    #   huge file containing all of them (file must be PEM encoded)
    #SSLCACertificateFile /etc/pki/tls/certs/ca-bundle.crt
    #   Client Authentication (Type):
    #   Client certificate verification type and depth.  Types are
    #   none, optional, require and optional_no_ca.  Depth is a
    #   number which specifies how deeply to verify the certificate
    #   issuer chain before deciding the certificate is not valid.
    #SSLVerifyClient require
    #SSLVerifyDepth  10
    #   Access Control:
    #   With SSLRequire you can do per-directory access control based
    #   on arbitrary complex boolean expressions containing server
    #   variable checks and other lookup directives.  The syntax is a
    #   mixture between C and Perl.  See the mod_ssl documentation
    #   for more details.
    #<Location />
    #SSLRequire (    %{SSL_CIPHER} !~ m/^(EXP|NULL)/ \
    #            and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd." \
    #            and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"} \
    #            and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \
    #            and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20       ) \
    #           or %{REMOTE_ADDR} =~ m/^192\.76\.162\.[0-9]+$/
    #   SSL Engine Options:
    #   Set various options for the SSL engine.
    #   o FakeBasicAuth:
    #     Translate the client X.509 into a Basic Authorisation.  This means that
    #     the standard Auth/DBMAuth methods can be used for access control.  The
    #     user name is the `one line' version of the client's X.509 certificate.
    #     Note that no password is obtained from the user. Every entry in the user
    #     file needs this password: `xxj31ZMTZzkVA'.
    #   o ExportCertData:
    #     This exports two additional environment variables: SSL_CLIENT_CERT and
    #     SSL_SERVER_CERT. These contain the PEM-encoded certificates of the
    #     server (always existing) and the client (only existing when client
    #     authentication is used). This can be used to import the certificates
    #     into CGI scripts.
    #   o StdEnvVars:
    #     This exports the standard SSL/TLS related `SSL_*' environment variables.
    #     Per default this exportation is switched off for performance reasons,
    #     because the extraction step is an expensive operation and is usually
    #     useless for serving static content. So one usually enables the
    #     exportation for CGI and SSI requests only.
    #   o StrictRequire:
    #     This denies access when "SSLRequireSSL" or "SSLRequire" applied even
    #     under a "Satisfy any" situation, i.e. when it applies access is denied
    #     and no other module can change it.
    #   o OptRenegotiate:
    #     This enables optimized SSL connection renegotiation handling when SSL
    #     directives are used in per-directory context.
    #SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
    <Files ~ "\.(cgi|shtml|phtml|php3?)$">
        SSLOptions +StdEnvVars
    <Directory "/var/www/cgi-bin">
        SSLOptions +StdEnvVars
    #   SSL Protocol Adjustments:
    #   The safe and default but still SSL/TLS standard compliant shutdown
    #   approach is that mod_ssl sends the close notify alert but doesn't wait for
    #   the close notify alert from client. When you need a different shutdown
    #   approach you can use one of the following variables:
    #   o ssl-unclean-shutdown:
    #     This forces an unclean shutdown when the connection is closed, i.e. no
    #     SSL close notify alert is send or allowed to received.  This violates
    #     the SSL/TLS standard but is needed for some brain-dead browsers. Use
    #     this when you receive I/O errors because of the standard approach where
    #     mod_ssl sends the close notify alert.
    #   o ssl-accurate-shutdown:
    #     This forces an accurate shutdown when the connection is closed, i.e. a
    #     SSL close notify alert is send and mod_ssl waits for the close notify
    #     alert of the client. This is 100% SSL/TLS standard compliant, but in
    #     practice often causes hanging connections with brain-dead browsers. Use
    #     this only for browsers where you know that their SSL implementation
    #     works correctly.
    #   Notice: Most problems of broken clients are also related to the HTTP
    #   keep-alive facility, so you usually additionally want to disable
    #   keep-alive for those clients, too. Use variable "nokeepalive" for this.
    #   Similarly, one has to force some clients to use HTTP/1.0 to workaround
    #   their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and
    #   "force-response-1.0" for this.
    SetEnvIf User-Agent ".*MSIE.*" \
             nokeepalive ssl-unclean-shutdown \
             downgrade-1.0 force-response-1.0
    #   Per-Server Logging:
    #   The home of a custom SSL log file. Use this when you want a
    #   compact non-error SSL logfile on a virtual host basis.
    CustomLog logs/ssl_request_log \
              "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"
  7. Xenocide

    Xenocide Member

    Any ideas?
  8. till

    till Super Moderator Staff Member ISPConfig Developer

    The ssl config is only written if all required ssl files are there in ssl directory of the website (the crt and the .key file). When that requirement is met, ispconfig writes the ssl configuration and tries to restart apache, if the restart of apache fails, it rolls back to the last working configuration state (vhost file) and stores a copy of the non working vhost configuration in the sites-available folder with a extension to the name. The extension is .error or so if I remember correctly.
  9. Xenocide

    Xenocide Member

    That's great cheers Till. So where does the key file go? in the ssl dir there's sitea.com.crt sitea.com.csr and sitea.com.bundle which field should be the .key?
  10. till

    till Super Moderator Staff Member ISPConfig Developer

    The key is not in the ispconfig interface for security reasons. Normally you create certificates in ispconfig and the key is stored in the key file only. If you have created a external certificate, you will have to add the key file manually in the ssl folder. It has the base file name like the other files in the ssl folder and ends with .key
  11. Xenocide

    Xenocide Member

    Thanks till. Working on one of my servers now :).

    Heres your painting:

  12. gawry

    gawry New Member

    Are there plans to support Wildcard Certificates? It doesnt seem very complicated. I've managed to make it work by editing the vhost file but I know that if i change anything in the configuration of that site, the SSL will stop working.

    I've just added the SSL certificates in the extra apache directives and changed the vhost to the 443 port
  13. till

    till Super Moderator Staff Member ISPConfig Developer

    We will add support for wildcard ssl future.
  14. Xenocide

    Xenocide Member

    That would be sweet and save us a massive headache till!

    Do you accept donations for features? :)
  15. gawry

    gawry New Member

    That's going to be really good. Till I would like to develop some addons. Could you send me some code samples?
  16. till

    till Super Moderator Staff Member ISPConfig Developer

    The ISPConfig developer tutorial can be found here online:


    The coee of that tutorial is aleeady part of ISPConfig and is inside the ispconfig.tar.gz that you can download from ispconfig.org
  17. gawry

    gawry New Member

    Great! i'm going to write couple modules and I'll release some of them as GPL.
  18. cbj4074

    cbj4074 Member

    I, too, am eagerly awaiting support for wildcard SSL certificates in ISPConfig.

    Gawry, were you implying that you would be working to write modules that added such support before it was supported officially? If so, I would be most interested in your efforts and willing to assist/test in whatever capacity would be helpful.

    Thank you!
  19. RodolpheB

    RodolpheB New Member

    Hi all,

    What about this very important feature ?

  20. spazio

    spazio Member HowtoForge Supporter

    Hi all !
    Is it possible to install a wildcard certificate in ispconfig 3 version
    I'm trying to create the request nothing happens and read this old post!
    And this feature request from 2012:
    Ispconfig does not let me create the request. Is this a bug/request or just not compatible?

    Where are we on this topic?


Share This Page