Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

We launched an ecommerce site a while back and got an ssl certificate for https://www.mysite.com. The site was abandoned for a while, and then recently resurrected. We got a new ssl certificate, but this time it was for https://mysite.com. Now, when people find the site on Google, the url is for https://www.mysite.com, and gives an untrusted site warning.

After some digging I've learned that I can't just redirect https://www.mysite.com to https://mysite.com without having a different ssl certificate for the www version. Is there a way I can correct this problem without having to buy another certificate?

share|improve this question

1 Answer 1

One option is to use Google's tools to remove a site from their index. Even if you did get a second certificate, the cache mix-up will be confusing to customers and developers alike. I think the most thorough solution is to remove the "bad" URL from Google's cache.

share|improve this answer
    
Few people will have gone to the site at this point, so this may fully solve the problem. –  dvcolgan Apr 19 '12 at 5:16
    
@dvcolgan Even if it's not the total solution, I think it has to be at least a large part of it. Then, of course, you'll want to check Bing and Yahoo to see what they've cached and how to go about removing any traces. –  Wesley Apr 19 '12 at 5:18

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.