Re: [Puppet Users] client connection errors: SSL, SNI and DNS_ALT_NAMES Oh My

2013-06-05 Thread Josh Cooper
On Mon, May 20, 2013 at 12:37 PM, Jonathan Proulx j...@jonproulx.com wrote: So turns out to be a very simple solution, all I needed was to set a ServerAlias apache directive for the alternate dns name. Since this is the only service apache on these systems serves I'd been sloppy and didn't

Re: [Puppet Users] client connection errors: SSL, SNI and DNS_ALT_NAMES Oh My

2013-05-20 Thread Jonathan Proulx
So turns out to be a very simple solution, all I needed was to set a ServerAlias apache directive for the alternate dns name. Since this is the only service apache on these systems serves I'd been sloppy and didn't specify any ServerName or ServerAlias, relying on everything being the default

Re: [Puppet Users] client connection errors: SSL, SNI and DNS_ALT_NAMES Oh My

2013-05-18 Thread Nabil Servais
Hello, I tried different configuration with SNI and authentication (classic certificates or puppet), I could say it's impossible. Maybe I miss something but I don't think so. You have to use an another dns name or use a different port. good luck. On Fri, May 17, 2013 at 9:46 PM, Jonathan

[Puppet Users] client connection errors: SSL, SNI and DNS_ALT_NAMES Oh My

2013-05-17 Thread Jonathan Proulx
Hi All, I've run into a bit of a tangle. I currently have two puppet masters which are load balanced with round robin DNS (one is also the CA). I'm using dns_alt_names to let them each answer to puppet.my.domain.com For the past year this has been fine. About a week ago I tried to add a