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 domain so that hit our server directly and of course with the tweaked config worked fine. Now I'veby braindeaf - Nginx Mailing List - English
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 was not OK However, this is definitely a different error message so it doesn't appear toby braindeaf - Nginx Mailing List - English
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.co seems to be ignored. Interesting, the wildcard SSL Key is the most basic RapidSSL Wildcardby braindeaf - Nginx Mailing List - English
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 to....with minimal configuration. https://example.co https://blah.example.co https://somerandomsubdomain.example.co all pointing at the same server so something like serby braindeaf - Nginx Mailing List - English