I've got a wildcard SSL certificate for *.example.com.
I'm using nginx, and redirecting all traffic for http to https, and also rewriting the URLs without a trailing www (if there is one).
So it has,
However, since my cert is for *.example.com, case 3 gets an SSL error in chrome ('This is probably not the site that you are looking for!'), but if you click through it gets redirected and all is well.
I understand why, since the initial connection is for https with a www (2 levels of subdomains), which doesn't match what is on the wildcard certificate.
I thought a solution would be to get an additional cert for
*.*.example.com to cover
www.*.example.com. But it seems like that won't work.
I spoke to agents from namecheap and comodo, and both said
*.*.example.com was not possible.
I also came across this article
Is there a solution to this? To be able to cover