Right then. I moved my certificates into their respective directories and re-reeditted my httpd.conf file to reflect those changes and set the SSLVerifyClient to 'none'. I was not sure where to go to change the logging to 'trace' though. But, I can get into the secure server now so it technically works. (thank you again Camun, and DuFresne and Stromas too)
However, I am finding that all of the pages I've visited while in https are pulling up 404 errors. The same pages pull up fine in http. Do I need to have a mirrored web directory just for https to get the files to show up or something? This is the only real conclusion I can think of. On Thursday 13 March 2003 11:55, cam wrote: > --- On Fri 03/14, A. Putnam < [EMAIL PROTECTED] > wrote: > >I get this error moeesage: > > > >"www.pelathe.org has received an incorrect or unexpected message. Error > > Code: -12227" I've never seen an error code like that before. Does anyone > > know what it means? > > Again, a guess, but you haven't set SSLVerifyClient Require have you? You > (presumably, otherwise, get reading on client certificates) want 'none' > here. If not, in fact, in any case, have a look in your SSL log files (not > the 'normal' log files) which will have been specified in httpd.conf... The > logs are your friend. > > cam > > _______________________________________________ > No banners. No pop-ups. No kidding. > Introducing My Way - http://www.myway.com > ______________________________________________________________________ > Apache Interface to OpenSSL (mod_ssl) www.modssl.org > User Support Mailing List [EMAIL PROTECTED] > Automated List Manager [EMAIL PROTECTED] -- A. Putnam Assistant IT Administrator Pelathe Community Resource Center ______________________________________________________________________ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
