[cobalt-users] The Certificate That Would Not Die

[Sterling Udell <sterling@xxxxxxxxxxxxxxxx>]

Greetings,

I'm in the process of moving a website with SSL from a BSD-Unix box to a Raq 4. As part of that process, I'm attempting to install my existing Thawte cert on the Raq. I think I've done everything correctly (based on instructions at http://list.cobalt.com/pipermail/cobalt-users/2000-November/026387.html ), but here's what happens:

Yesterday, I generated a self-signed cert as a test, and sure enough, that worked fine. Today, I copied in the key and Thawte cert from my old BSD server, then selected "Use manually entered certificate" on the Raq's "SSL Settings" siteadmin page. It seemed to take it, but when I try to access the secured site from a browser, it's still getting the old (self-signed) cert.

I've tried installing this cert on other virtual sites on this server (only 1 at a time of course), and it works fine there (though of course the domain name doesn't match). On my main site I've deleted and re-installed my Thawte cert several times, but the only cert it will serve is the test one I created yesterday.

Any thoughts on where this thrice-damned test cert might be lurking, and how I can get rid
of it?

--
Sterling Udell

http://www.AddresSender.com . . . the address book with a difference!