Wildcard SSL certificates do not work with naked domains

Kheldar Ambar

I have deployed a wildcard certificate (Comodo PlatinumSSL) *.example.comon Apache/Ubuntu 14.04 . Everything works fine if the client accesses, https://www.example.combut https://example.comin Firefox it throws this error:

example.com uses an invalid security certificate. 
The certificate is only valid for *.example.com 
(Error code: ssl_error_bad_cert_domain)

Extract from vhost file:

<IfModule mod_ssl.c>
    <VirtualHost *:443>
        SSLEngine on
        ServerName example.com
        ServerAlias www.example.com *.example.com
        DocumentRoot /var/www/html
        SSLCertificateFile      /etc/ssl/localcerts/example_com.cer
        SSLCertificateKeyFile /etc/ssl/localcerts/example_com.key
        SSLCertificateChainFile /etc/ssl/localcerts/example_com_interm.cer
    </VirtualHost>
</IfModule>

How can I get both https://www.example.comand https://example.comwork without warning?

Steffen Ullrich

Wildcards match a single leftmost label. That's a *.example.commatch, www.example.combut not an example.comor sub.foo.example.com. This means that you either need to get a certificate that includes *.example.comand is example.comthe subject alternative name , or if you just need wwwthe naked domain name, you can get a cheap certificate that only includes www.example.comand example.com.

Related

Wildcard SSL certificates do not work with naked domains

Kheldar Ambar I have deployed a wildcard certificate (Comodo PlatinumSSL) *.example.comon Apache/Ubuntu 14.04 . Everything works fine if the client accesses, https://www.example.combut https://example.comin Firefox it throws this error: example.com uses an inv

Wildcard SSL Certificates, Custom Domains and Cloudflare

swt83 I have a domain ( https://domainA.com ) with a wildcard SSL certificate. I have users using a custom subdomain ( https://user1.domainA.com ). I have some users who want to use custom domains that point to their subdomains (CNAME records from https://doma

Wildcard SSL Certificates, Custom Domains and Cloudflare

swt83 I have a domain ( https://domainA.com ) with a wildcard SSL certificate. I have users using a custom subdomain ( https://user1.domainA.com ). I have some users who want to use custom domains that point to their subdomains (CNAME records from https://doma

Wildcard SSL Certificates, Custom Domains and Cloudflare

swt83 I have a domain ( https://domainA.com ) with a wildcard SSL certificate. I have users using a custom subdomain ( https://user1.domainA.com ). I have some users who want to use custom domains that point to their subdomains (CNAME records from https://doma

Wildcard SSL Certificates, Custom Domains and Cloudflare

swt83 I have a domain ( https://domainA.com ) with a wildcard SSL certificate. I have users using a custom subdomain ( https://user1.domainA.com ). I have some users who want to use custom domains that point to their subdomains (CNAME records from https://doma

Wildcard SSL Certificates, Custom Domains and Cloudflare

swt83 I have a domain ( https://domainA.com ) with a wildcard SSL certificate. I have users using a custom subdomain ( https://user1.domainA.com ). I have some users who want to use custom domains that point to their subdomains (CNAME records from https://doma

Do browsers trust wildcard SSL certificates?

Paul J I've set up a development server where I need to test a lot of LAMP sites. Their domain names are in the following format: https://webapp1.test.example.com https://anotherwebapp.test.example.com https://anotherclientssite.test.example.com I want to get

Are wildcard SSL certificates recommended?

Sivalingaamorthy I'm in the following domains, is there a benefit to buying a single wildcard certificate? Or do I need to buy a separate SSL certificate. abc.example.com。au abc.example.com。nz abc.api.module.example.com abc.api.global.example.com Are there any

AWS ACM wildcard SSL certificate doesn't work with domains

John I created an SSL certificate for my site using Amazon Certificate Manager. The certificate is for *.example.com. Then I attached this certificate to my ELB and kept the instance protocol as http. So the SSL chain is only between the client and the ELB. I

AWS ACM wildcard SSL certificate doesn't work with domains

John I created an SSL certificate for my site using Amazon Certificate Manager. The certificate is for *.example.com. Then I attached this certificate to my ELB and kept the instance protocol as http. So the SSL chain is only between the client and the ELB. I

AWS ACM wildcard SSL certificate doesn't work with domains

John I created an SSL certificate for my site using Amazon Certificate Manager. The certificate is for *.example.com. Then I attached this certificate to my ELB and kept the instance protocol as http. So the SSL chain is only between the client and the ELB. I

AWS ACM wildcard SSL certificate doesn't work with domains

John I created an SSL certificate for my site using Amazon Certificate Manager. The certificate is for *.example.com. Then I attached this certificate to my ELB and kept the instance protocol as http. So the SSL chain is only between the client and the ELB. I

WildFly Multiple Domains and SSL Certificates

kefkaz I have two different domains example1.com example2.com Each domain has its own SSL certificate. What I want to do now is use both domains for the same WildFly instance, with SSL support. The WildFly documentation states that I can only reference a singl

WildFly Multiple Domains and SSL Certificates

kefkaz I have two different domains example1.com example2.com Each domain has its own SSL certificate. What I want to do now is use both domains for the same WildFly instance, with SSL support. The WildFly documentation states that I can only reference a singl

WildFly Multiple Domains and SSL Certificates

kefkaz I have two different domains example1.com example2.com Each domain has its own SSL certificate. What I want to do now is use both domains for the same WildFly instance, with SSL support. The WildFly documentation states that I can only reference a singl

Naked domains don't work in Firebase and Google domains

Joseph Selvaragi I created a free hosting account in Firebase and uploaded a one page site. it works I have a custom domain with Google Domains. I connected my custom domain and added the two IP addresses given by Firebase to the Google Domain DNS A records. c

Only redirect to naked domains

Lerio Feeta On my Apache 2.4 webserver I have a virtual host configured to redirect all requests on http to https and it works fine. I would like to improve it by adding the following rules: If user requests http://www.domain.example redirect to https://domain

Only redirect to naked domains

Lerio Feeta On my Apache 2.4 webserver I have a virtual host configured to redirect all requests on http to https and it works fine. I would like to improve it by adding the following rules: If user requests http://www.domain.example redirect to https://domain

Only redirect to naked domains

Lerio Feeta On my Apache 2.4 webserver I have a virtual host configured to redirect all requests on http to https and it works fine. I would like to improve it by adding the following rules: If user requests http://www.domain.example redirect to https://domain

Only redirect to naked domains

Lerio Feeta On my Apache 2.4 webserver I have a virtual host configured to redirect all requests on http to https and it works fine. I would like to improve it by adding the following rules: If user requests http://www.domain.example redirect to https://domain

Only redirect to naked domains

Lerio Feeta On my Apache 2.4 webserver I have a virtual host configured to redirect all requests on http to https and it works fine. I would like to improve it by adding the following rules: If user requests http://www.domain.example redirect to https://domain

Only redirect to naked domains

Lerio Feeta On my Apache 2.4 webserver I have a virtual host configured to redirect all requests on http to https and it works fine. I would like to improve it by adding the following rules: If user requests http://www.domain.example redirect to https://domain