Reputation
Top tag
Next privilege 200 Rep.
See reduced ads
Badges
2 13
Impact
~21k people reached

  • 0 posts edited
  • 0 helpful flags
  • 2 votes cast
Feb
22
awarded  Popular Question
Jan
31
comment Passing multiple https domains through Elastic Load Balancer
There's no way to get the request through ELB if the certificate doesn't match the domain, without the user getting the warning in the browser about the connection being insecure.
Jan
29
comment Passing multiple https domains through Elastic Load Balancer
I don't want have to run a separate EC2 instance to just do a redirect.
Jan
29
awarded  Popular Question
Jan
28
comment Passing multiple https domains through Elastic Load Balancer
1) The load balancer doesn't care what the domains are, so they don't need to be specified anywhere. 2) The load balancer has a certificate for the second brand, so will not let other domains through without a successful SSL handshake, or user consent in their browser 3) Load balancers cannot have multiple certificates from what I can tell.
Jan
27
accepted Passing multiple https domains through Elastic Load Balancer
Jan
27
comment Passing multiple https domains through Elastic Load Balancer
What do you mean, "take the old domain out of the ELB"? ELB currently knows nothing about that old domain. And that old domain can't get past the SSL handshake that happens at the ELB level, to get to the nginx server block, without the user getting the ssl warning.
Jan
25
comment Passing multiple https domains through Elastic Load Balancer
Oh man, that's amazing. The bummer is that's only in the East region now, and the stack I'm dealing with is in the West. Argh.
Jan
24
asked Passing multiple https domains through Elastic Load Balancer
Sep
28
awarded  Popular Question
Jul
5
awarded  Notable Question
Mar
19
awarded  Curious
Aug
7
awarded  Popular Question
Jul
24
awarded  Supporter
Jan
24
awarded  Popular Question
Jul
12
awarded  Notable Question
Oct
27
awarded  Popular Question
Mar
7
comment Dovecot with Postfix on Ubuntu: warning: SASL: Connect to private/auth-client failed: No such file or directory
The thing is I don't see any blocks that look remotely like that in the dovecot.conf or included files. See gist.github.com/1994578
Mar
3
comment Dovecot with Postfix on Ubuntu: warning: SASL: Connect to private/auth-client failed: No such file or directory
Right, but as I mentioned I don't know which file that goes in. None of my dovecot config files look like the ones I see people refer to.
Mar
3
comment Dovecot with Postfix on Ubuntu: warning: SASL: Connect to private/auth-client failed: No such file or directory
If you are going to downvote a post, please tell why.