Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am trying to configure a wildcard SSL certificate to serve on subdomains as well as on the main domain for a server. In order to get the SSL cert to work, it seems that I must define the main site's sites-available file as such:

<VirtualHost *:443>

When I try to use <VirtualHost> then Firefox complains:

An error occurred during a connection to

SSL received a record that exceeded the maximum permissible length.
(Error code: ssl_error_rx_record_too_long)
The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.

Google Chrome is less specific:

SSL connection error

To what could I change <VirtualHost *:443> so that I could serve as a different Virtual Host with SSL as well?

This is on Ubuntu Server 12.04 LTS (3.2 kernel) with Apache 2.2.22 and a Godaddy SSL certificate.

Edit:: Here is the Apache sites-enabled file for the domain.

<IfModule mod_ssl.c>
#<VirtualHost *:443>           # With this line, the site serves fine
<VirtualHost> # With this line, browsers throw the error
        DocumentRoot /var/www/someSite/public_html


        <Directory />
                Options FollowSymLinks
                AllowOverride None
        <Directory /var/www/someSite/public_html/>
                Options Indexes FollowSymLinks MultiViews
                AllowOverride None
                Order allow,deny
                allow from all

        ErrorLog ${APACHE_LOG_DIR}/error.log
        LogLevel warn
        CustomLog ${APACHE_LOG_DIR}/ssl_access.log combined

        SSLEngine on
        SSLCertificateFile    /etc/apache2/ssl/
        SSLCertificateKeyFile /etc/apache2/ssl/someSite.key

        <FilesMatch "\.(cgi|shtml|phtml|php)$">
                SSLOptions +StdEnvVars
        <Directory /usr/lib/cgi-bin>
                SSLOptions +StdEnvVars

        BrowserMatch "MSIE [2-6]" \
                nokeepalive ssl-unclean-shutdown \
                downgrade-1.0 force-response-1.0
        BrowserMatch "MSIE [17-9]" ssl-unclean-shutdown

share|improve this question
paste configuration file of apache, ssl virtualhost – B14D3 Jul 3 '13 at 6:44
@B14D3: Thanks, I added it to the question. – dotancohen Jul 3 '13 at 6:55
up vote 2 down vote accepted

Apache recommends against using a hostname in the <VirtualHost> directive for a variety of reasons.

The best practice is to specify the IP address or * in <VirtualHost> and the hostname(s) of the virtual host in the ServerName and ServerAlias directives.

So to resolve this:

  • If you want all of the wildcard subdomains to be served by the existing virtual host, add ServerAlias * to it.
  • If you want all the wildcard subdomains to be served by a completely different virtual host, add a new <VirtualHost> block with a ServerName and ServerAlias *
share|improve this answer
Thank you Michael. – dotancohen Jul 8 '13 at 9:47
For posterity: I had to add NameVirtualHost *:443 to ports.conf as well. – dotancohen Aug 14 '13 at 19:34

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.