I was too quick to call it a success. Squid now starts, and appears to run
until a user tries to connect through it. I don't see any logs being
written. How can I troubleshoot without a log file to read over? I'm using
two squid servers to accelerate ssl through my firewall, the outer squid box
is up and running fine with a valid verisign key, and the inner box should
be able to run with a self signed cert, but I'm running out of ideas.
client<--->internet<--->squid1<--->firewall<--->squid2<--->application
server
SSL SSL SSL SSL SSL http
Charles
______________________________________________________________
-----Original Message-----
From: Henrik Nordstrom [mailto:hno@squid-cache.org]
Sent: Tuesday, January 06, 2004 10:39 AM
To: Schaefer, Charles
Cc: 'Henrik Nordstrom'; squid-users@squid-cache.org
Subject: RE: [squid-users] SSL error preventing Squid from running
On Tue, 6 Jan 2004, Schaefer, Charles wrote:
> How can I check the server name? I have the same name in the hosts file,
and
> the correct dns name in resolv.conf.
openssl x509 -in certificate.pem -text
the CN value in the Subject field needs to match the host name the user
requests in his browser.
But as I said this error does not stop Squid from starting, and only gives
a warning in the browser.
Regards
Henrik
Received on Tue Jan 06 2004 - 14:32:50 MST
This archive was generated by hypermail pre-2.1.9 : Sun Feb 01 2004 - 12:00:03 MST