On 2005.10.12, Mark Aufflick <[EMAIL PROTECTED]> wrote: > In some code dealing with paypal callbacks, I have the following line: > > set result [ns_httpspost $webscr "" $qsset] > > on my dev server, with aolserver40r10 and ns_openssl (from cvs head) it > works fine. > > On my production server, with aolserver and nsopenssl compiled from > exactly the same file versions, I get the following error: > > failed to use either named or default client SSL context [...] > > I am using exactly the same config file and certs in both cases (and > based on the openacs default). For you reference the relevant section > is below. > > Can anyone shed some light onto this? As far as I can see, the defaults > are set up correctly. The fact that it works with the same config and > versions on a different server doesn't help my sanity!
Hi, Mark, My gut is telling me that in production, either the certs aren't installed in the right place OR the file permissions on them are such that the webserver isn't reading them. Can you watch your dev. startup carefully in the server.log (or whatever you've configured the name to be) esp. around the nsopenssl module load where it confirms it read the certificates and registered the client context, then check your prod. startup log to ensure it's doing the exact same thing? If the startup messages aren't the same, then something must be different between the two hosts ... Figuring out what that difference might be is tough. I'd just start by ruling out the "obvious" or easy to test possibilities. -- Dossy -- Dossy Shiobara [EMAIL PROTECTED] | http://dossy.org/ Panoptic Computer Network http://panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70) -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
