Installed a new SSL Certificate from Comodo and now I'm unable to access OWA on SBS2003
I renewed my SSL Cert with Comodo and immediately after installing it I was unable to access OWA.
I'm running SBS2003 Premium with SQL and MS CRM 3.0 - CRM does not appear to be affected at this time.
I am unable to access the Webmail site internally or externally by typing in https://bgrsbs01.bgrdc.com/exchange
I do get prompted for username and password but after I enter them I get HTTP Error 404 - page cannot be found.
I can browse the site through IIS and log in succesfully
I stopped and restarted IIS and all its sub services
I ran the CEICW and kept the existing certificate and still no go. Ran it again and tried to use the new cert but it said it was not in the right format.
Please advise.
dph
I'm running SBS2003 Premium with SQL and MS CRM 3.0 - CRM does not appear to be affected at this time.
I am unable to access the Webmail site internally or externally by typing in https://bgrsbs01.bgrdc.com/exchange
I do get prompted for username and password but after I enter them I get HTTP Error 404 - page cannot be found.
I can browse the site through IIS and log in succesfully
I stopped and restarted IIS and all its sub services
I ran the CEICW and kept the existing certificate and still no go. Ran it again and tried to use the new cert but it said it was not in the right format.
Please advise.
dph
ASKER
Thank you svkojester - My OWA has been available externally (until today) and the yes www.bgrdc.com is hosted by liquidweb, however https://bgrsbs01.bgrdc.com/exchange is not and has worked up until I change the cert today.
The cert installed is for bgrsbs01.bgrdc.com. I created a temp site to create the new request and imported the new cert to that site, then the default site. I just had a chance to reboot the server and no change... I'm retracing my steps to see if I missed anything.
dph
The cert installed is for bgrsbs01.bgrdc.com. I created a temp site to create the new request and imported the new cert to that site, then the default site. I just had a chance to reboot the server and no change... I'm retracing my steps to see if I missed anything.
dph
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Secure Connection Failed
bgrdc.com uses an invalid security certificate.
The certificate is only valid for *.liquidweb.com
(Error code: ssl_error_bad_cert_domain)
You will probably end up having the re-key the correct SSL certificate for your domain & install it on your server. Most places will let you re-key the cert for free as long as it's not expired.