Ah sorry, just saw you tried this. But this is the correct way, I use 7 certificates with one apache as backend. Example:
Service HeadRequire "Host:.*www.example.com.*" BackEnd Address 1.1.1.1 Port 10443 HTTPS TimeOut 60 End End Am 15.01.2015 22:32 schrieb Adam Gold <[email protected]>: > > Hi there. I'm trying to get Pound to direct https for different domains > to the same server/IP (which is running Nginx). To do this I have been > using the following config: > > ListenHTTPS > Address 0.0.0.0 > Port 443 > Cert "domain1.pem" > Cert "domain2.pem" > Service > BackEnd > Address [local subnet IP] > Port 8080 > End > End > End > > It seems that only the certificate listed first is used so when > "domain1" is top of the list, the correct https version of that site is > returned and same if "domain2" is first. If I request the second in the > list I get a browser warning because of a certificate mismatch. Both of > these domains work fine with https unproxied. > > I have also tried creating two service blocks with HeadRequire "Host: > .*domainX" but this doesn't fix the issue. > > Apologies if I'm treading on very well worn ground. I did have a look > through the archives as well as doing a wider search and saw this > mentioned once or twice but didn't spot an obvious solution. > > -- > To unsubscribe send an email with subject unsubscribe to [email protected]. > Please contact [email protected] for questions.
