3 ms·
I agree with GoDaddy being horrible, but this really isn't just their fault. Certificate revocation does exactly what it says. It's a technical term that everyo
by pieter 15y ago
I agree with GoDaddy being horrible, but this really isn't just their fault. Certificate revocation does exactly what it says. It's a technical term that everyone using SSL should know and understand the implications of. Their offer of creating a new certificate for you for $15 actually sounds pretty decent.
And, you don't have backups of all your data and domains? While running your sites on a shared host? This really sounds like something that was bound to happen to you. Be glad you got it fixed and I hope you learned your lesson.
- wvenable 15y agoBackups don't matter in this case. What is he going to do with backups?
- dholowiski 15y agoHis sites were down for "days". If he had backups he could have restored the sites to a different server.
- wvenable 15y agoYes, but isn't the problem related to the domains not the hosting?
- kijin 15y agoIt seems that GoDaddy created a certificate for the wrong domain in the first place. Still, the author should have pointed out the problem and ask GoDaddy to fix it instead of revoking the certificate himself.
- caryme 15y agoI ran into the same situation the author did when getting SSL for a freelance client of mine. The problem is that nowhere in GoDaddy's certificate purchasing or setup process do they ask you what domain name you want the certificate to apply to. They just apply it to the "primary" domain on a hosting account, which is basically the first domain you set up and associated with that hosting. I kept expecting that the next step in the setup process would ask me what domain I wanted to use the certificate for until there was no next step and the cert was pending setup on the wrong domain. At no point did they indicate that their single-domain certificate only works on the primary domain until I was on the phone with customer service before revoking it. We ended up going with a multi-domain cert (which they did give us a discount on) rather than change the primary domain on the hosting account because their service representative said that would require downtime for all the sites on that hosting account.