The SSL Checking service did indeed point out the error. I will admit to my
own stupidity on this one. We're using Elastic Load Balancing on
*.example.co
ELB had only our other SSL Cert configured and not our new one. Darn it. We
don't use ELB for example.co because you can't CNAME the root doma
Thanks for the tip. I have replaced the config with
server_name example.co *.example.co
with
server_name .example.co
While that is definitely more concise it didn't solve the problem.
http://example.co - seems fine.
http://test.example.co - curl: (51) SSL peer certificate or SSH remote key
wa
Sorry to be vague.
http://example.co - works fine and as expected.
http://blah.example.co - returns curl: (60) SSL certificate problem: Invalid
certificate chain
This is actually picking up the SSL cert for the default site on the server.
So the server_name is picking up example.co but *.example.
Hey there, I'm struggling to find the correct answer and unsure if there
even is one.
We have a domain say, example.co and we've purchased a wildcard SSL
certificate for it. We want to be able to provide what amounts towith
minimal configuration.
https://example.co
https://blah.example.co
htt
