$uddenly cooperative webhost
-
The SSL certificate we bought through our webhost expired without a warning or renewal notice. This explains some weird things that started happening with some of our client file manager (updates) processes. It seems that a resource requested through https where the certificate is out of date does not throw an exception...it only creates 0 byte files! Yes, the https protocol was baked into the processes. The processes have been modified and posted, but if they are automatically downloaded through the version of the application that all current clients are using, the updates fail. :doh: We have a secondary fallback server that still works, but only if the primary server is unreachable. It should be a simple solution...either renew the existing cert or get one from another vendor and install it myself. The first option seemed easy enough, except for some reason, my credentials to the webhost account no longer work. I can login to cPanel, but not to the account! :confused: No problem, use their forgot password utility to recover it...nada...after a few tries I'm locked out. Fine, then I'll get an SSL elsewhere and undoubtably cheaper than $109/yr! I got a deal for 3 years at a decent price and bought it. Now, I just need to get a CSR from my webhost to create the certificate. No problem, I open a support ticket with my webhost and ask for one. Although they can identify me as the technical contact for the company, the primary account contact and CC holder (who just left for vacation) is the only one who can ask for a CSR and they refuse to help me since they charge $15 to generate the CSR and I'm not authorized for charges. :mad: I'm pretty close to moving the whole domain to Azure at this point! First though, I'll try another tech/support ticket to see if there's a way around this silly $15 charge. Edit: They now insist that they will need to install the cert (for an additional $30...am I wrong in thinking that it's only a freaking text file placed in the root folder?..and that I should be able to do this myself? Update: I managed to get the last 4 of the cc on file, and got the process complete through their helpdesk. Once they had their money, it only took about 48 hours to get it done...but at least it's done and I don't have to think about it again for 3 years. :)
"Go forth into the source" - Neal Morse
-
The SSL certificate we bought through our webhost expired without a warning or renewal notice. This explains some weird things that started happening with some of our client file manager (updates) processes. It seems that a resource requested through https where the certificate is out of date does not throw an exception...it only creates 0 byte files! Yes, the https protocol was baked into the processes. The processes have been modified and posted, but if they are automatically downloaded through the version of the application that all current clients are using, the updates fail. :doh: We have a secondary fallback server that still works, but only if the primary server is unreachable. It should be a simple solution...either renew the existing cert or get one from another vendor and install it myself. The first option seemed easy enough, except for some reason, my credentials to the webhost account no longer work. I can login to cPanel, but not to the account! :confused: No problem, use their forgot password utility to recover it...nada...after a few tries I'm locked out. Fine, then I'll get an SSL elsewhere and undoubtably cheaper than $109/yr! I got a deal for 3 years at a decent price and bought it. Now, I just need to get a CSR from my webhost to create the certificate. No problem, I open a support ticket with my webhost and ask for one. Although they can identify me as the technical contact for the company, the primary account contact and CC holder (who just left for vacation) is the only one who can ask for a CSR and they refuse to help me since they charge $15 to generate the CSR and I'm not authorized for charges. :mad: I'm pretty close to moving the whole domain to Azure at this point! First though, I'll try another tech/support ticket to see if there's a way around this silly $15 charge. Edit: They now insist that they will need to install the cert (for an additional $30...am I wrong in thinking that it's only a freaking text file placed in the root folder?..and that I should be able to do this myself? Update: I managed to get the last 4 of the cc on file, and got the process complete through their helpdesk. Once they had their money, it only took about 48 hours to get it done...but at least it's done and I don't have to think about it again for 3 years. :)
"Go forth into the source" - Neal Morse
-
I don't envy you...horsing around with SSL certificates is a pain. The whole security certificate thing is a giant racket. I'm hoping this takes off: https://letsencrypt.org/[^]
This is the one from the Insider isn't it? I like the idea too, but I don't see how they can continue to operate for free. Are they going to depend on donations for funding?
-
This is the one from the Insider isn't it? I like the idea too, but I don't see how they can continue to operate for free. Are they going to depend on donations for funding?
-
I don't envy you...horsing around with SSL certificates is a pain. The whole security certificate thing is a giant racket. I'm hoping this takes off: https://letsencrypt.org/[^]