Joe, Sorry for wasting your time... It seems I'm using 2.4.5
I always install pound from source... Now I've installed pound using apt-get in Ubuntu 10.4 TLS. I will install it from source and it will probably work. During installation I was too focused on my modified script that NATs the incoming ports automatically. I am already running Varnish on that system and at first I thought I could use that one for HTTPS, but it seems it doesn't even support incoming https. Thanks -----Original Message----- From: Joe Gooch <[email protected]> To: "'[email protected]'" <[email protected]> Date: Wed, 8 Feb 2012 14:39:49 +0000 Subject: RE: [Pound Mailing List] HTTPS backend See lines below. Joe > -----Original Message----- > From: Jean-Pierre [mailto:[email protected]] > Sent: Wednesday, February 08, 2012 8:52 AM > To: [email protected] > Subject: RE: [Pound Mailing List] HTTPS backend > > Hi Joe, > > I'm using 2.6f > > I did see the possibility to do a redirect, but this is AFAIK only > possible outside the backend-scope. > > ListenHTTPS > Address 0.0.0.0 > Port 4443 > > Cert "/root/.ssh/cert.pem" > CAList "/root/.ssh/godaddy-class2.pem" > xHTTP 3 > > Service "pfsense" > BackEnd > Address 82.172.139.149 > Port 61080 HTTPS > End > BackEnd > Address 89.250.170.164 > Port 61080 HTTPS > End > BackEnd > Address 89.250.169.117 > Port 61080 HTTPS > End > End > End > > This is my config... > How should it look if these backends were https backend? > > > -----Original message----- > From: Joe Gooch <[email protected]> > Sent: Tue 07-02-2012 22:45 > To: '[email protected]' <[email protected]>; > Subject: RE: [Pound Mailing List] HTTPS backend > > > HTTPS backends were added in v2.5c... Are you having an issue > configuring the feature, or are you using a pound that is older than > that, or is it something else? > > Joe > > -----Original Message----- > > From: Jean-Pierre [mailto:[email protected]] > > Sent: Tuesday, February 07, 2012 2:05 PM > > To: [email protected] > > Subject: [Pound Mailing List] HTTPS backend > > > > I've been using pound for a long while now. > > I'm also using pound to terminate my HTTPS connection with a cheapo > 1- > > subdomain SSL-certificate. > > Thanks to Pound I can have a few different machines using 1 IP and 1 > > subdomain. > > > > I now wanted to use pound to proxy my multi-WAN router. > > The multi-WAN router uses several modems and with pound I will always > > get a connection from a remote location because pound will only proxy > > for connections that are UP. This way I don't need to remember IP's > (I > > can still do this as fallback). > > > > During configuration I realized for the first time that I can't proxy > > to an SSL-connection. > > I now switched to http remote access, but this means someone can get > my > > passwords.... > > > > Is there a special reason why I can't use https-backend? > > SSL-support is already there as a client... > > > > BTW... I only need SSL-encryption, not 3-rd party authentication. > > > > JP > > > > > > > > -- > > To unsubscribe send an email with subject unsubscribe to > > [email protected]. > > Please contact [email protected] for questions. > > -- > To unsubscribe send an email with subject unsubscribe to > [email protected]. > Please contact [email protected] for questions. -- To unsubscribe send an email with subject unsubscribe to [email protected]. Please contact [email protected] for questions.
