Hi,

I'm trying use pound for  HTTPS requests, decrypting them and sending
them to the backend servers, rather than having web servers running
https.

My problem is this: When a browser connects with HTTPS, the page does
not load (as if there was no https server running) and in
/var/log/messages, pound says:

pound: HTTPS accept: Bad file descriptor

My pound.cfg looks like:

LogLevel 1
ListenHTTP  1.2.3.4,80
ListenHTTPS 1.2.3.4,443 /usr/local/etc/server.pem
 
User nobody
Group nobody
Alive 1
Client 999


UrlGroup ".*"
BackEnd 192.168.1.2,80,1 
BackEnd 192.168.1.3,80,1     
EndGroup

Pretty simple, just balancing between two servers. Pound starts up fine,
but all HTTPS request produce that "bad file descriptor" error.
Server.pem is where I say it is above, owned by and readable to the
pound user. 


My .pem file is my private key file, intermediate key and public key.

Any ideas what I'm doing wrong?


Thanks,
- Jason

I fixed this, I was still running an https server on the same machine,
duh!

But now I get this in the log when trying to start pound:

May  9 21:10:23 proxy pound: starting...
May  9 21:10:23 proxy pound: SSL_CTX_use_PrivateKey_file failed -
aborted

The private key is not password protected and I'm using openssl-0.9.7d.

---------------------------------------------------
Jason Kronstat
DirectXAthletics
jason(at)directXathletics.com
 


-----Original Message-----
From: Jason Kronstat [mailto:jason(at)directXathletics.com] 
Sent: Sunday, May 09, 2004 9:07 PM
To: pound(at)apsis.ch
Subject: HTTPS error 


Hi,

I'm trying use pound for  HTTPS requests, decrypting them and sending
them to the backend servers, rather than having web servers running
https.

My problem is this: When a browser connects with HTTPS, the page does
not load (as if there was no https server running) and in
/var/log/messages, pound says:

pound: HTTPS accept: Bad file descriptor

My pound.cfg looks like:

LogLevel 1
ListenHTTP  1.2.3.4,80
ListenHTTPS 1.2.3.4,443 /usr/local/etc/server.pem
 
User nobody
Group nobody
Alive 1
Client 999


UrlGroup ".*"
BackEnd 192.168.1.2,80,1 
BackEnd 192.168.1.3,80,1     
EndGroup

Pretty simple, just balancing between two servers. Pound starts up fine,
but all HTTPS request produce that "bad file descriptor" error.
Server.pem is where I say it is above, owned by and readable to the
pound user. 


My .pem file is my private key file, intermediate key and public key.

Any ideas what I'm doing wrong?


Thanks,
- Jason

On Monday 10 May 2004 03.54, Jason Kronstat wrote:[...]

No way - you would get another message ("check socket create"). I suggest you 
check again.
[...]

There is a problem with your certificate file - the key is not there, or in 
the wrong format, or the wrong key...[...]