Re: Wildcard SSL and Wildcard hostnames

hi if you are using amazon you can try their DNS service Route53. you can point the root domain to an ELB via ALIAS setting. regards, ron On Mon, May 11, 2015 at 11:23 PM, braindeaf wrote: > The SSL Checking service did indeed point out the error. I will admit to my > own stupidity on this on

Re: Wildcard SSL and Wildcard hostnames

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. It's offtopic but technically you can or life always finds a way -

Re: Wildcard SSL and Wildcard hostnames

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

Re: Wildcard SSL and Wildcard hostnames

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

Re: Wildcard SSL and Wildcard hostnames

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

Re: Wildcard SSL and Wildcard hostnames

braindeaf Wrote: --- > http://blah.example.co - returns curl: (60) SSL certificate problem: > Invalid certificate chain Forget one thing, you also need a wildcard DNS entry. DNS: so it arrives at your frontdoor Nginx.conf (server_name .example.c

Re: Wildcard SSL and Wildcard hostnames

itpp2012 provided you with the answer, also to be found in the server_name directive documentation. --- *B. R.* On Mon, May 11, 2015 at 3:54 PM, braindeaf wrote: > Sorry to be vague. > > http://example.co - works fine and as e

Re: Wildcard SSL and Wildcard hostnames

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.

Re: Wildcard SSL and Wildcard hostnames

braindeaf Wrote: --- > server { > port 443 > server_name .example.co; Would be a catch all. Posted at Nginx Forum: http://forum.nginx.org/read.php?2,258792,258796#msg-258796 ___ nginx mailing lis

Re: Wildcard SSL and Wildcard hostnames

This doesn't appear to work as I would expect it to. Would we need to set up a different server for each subdomain explicity. or could we get away with one config for example.co and another for *.example.co? Doesn't work in what way? (Does nginx or browser complain/what's the error?) Such c

Re: Wildcard SSL and Wildcard hostnames

What did you expect? What did you get? What did you think you configured? --- *B. R.* On Mon, May 11, 2015 at 1:11 PM, braindeaf wrote: > 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 SS

Wildcard SSL and Wildcard hostnames

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