Well, they finally fixed it, this is what they said the problem was. The problem was relating to the suExec configuration with ApacheSSL.
Thanks -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Nicolas Ross Sent: Wednesday, November 05, 2003 6:05 PM To: [EMAIL PROTECTED] Subject: Re: New certificate problem > For starters, your SSL certificate appears to be for > http://domainnamecenters.com, without the www sub-domain. Certificates can > be purchased for a domain either with or without, but they are not > interchangeable. Whenever I test > https://domainnamecenters.com/cgi-bin/register2/verify_install.cgi I am > still getting the error message, however. > > Since we can not provide support for third party scripts, and since this did > work before you renewed your SSL, our best recommendation would be to > contact TuCows (the makers of this particular script) and see if they have > any documentations as far as this type of problem is concerned. If they can > give you any recommendations as far as this is concerned, we can look into > implementing, but if the script has stopped running securely only after you > updated your SSL, and the SSL is not generating any errors, this is very > likely a problem with the script itself, unfortunately. > > > > Well, that doesn't make sense to me, if the script works fine unsecure, why > wouldn't it work secure???? I still get a 500 internal server error, with every address I tried. What is the log of your server web tells you ? As for the response you get, when you buy a certificate, it's for a particular name. You bought your cert for domainnamecenters.com, not www.domainnamecenters.com, wich would require another certs. Hope this helps ! Nicolas
