-
-
Save stopspazzing/c871f935771f14933c63 to your computer and use it in GitHub Desktop.
********* <[email protected]> | |
Dec 13, 2015, 10:53 AM | |
to: | |
“emailremoved” <emailremoved> | |
Dear Jeremy, | |
We are deeply sorry to know that you have decided to end our relationships, both because we value your business and because we truly believe purchased SSL is a better choice in most cases. | |
We'll happily provide a 30% discount on your SSL renewal if you'll stay with us. | |
Regarding the cPanel plugin for Let's Encrypt, unfortunately at this point we are unable to tell exactly if we will be implementing it or not since it involves a big amount of changes to our servers structure. | |
We will treat any decision of yours with proper respect and understanding. | |
If there is anything else you would like to discuss about this matter or have any additional questions or comments, please feel free to reply to this email. | |
----------------------------- | |
Regards, | |
********* | |
Customer Support Specialist | |
SSL Department |
a way to use certbot in their shared server … I was able to do it on my Ubuntu box and then upload/paste/install
@kabeza Yes, in the message I posted on this thread in May of 2021 I included a shell script to do exactly that.
The medium essay that you posted involves many manual steps to be repeated quarterly: you have to, of your own volition, (1) execute certbot, then (2) upload a file to the hosting, then (3) finish executing certbot, then (4) paste the certificate into CPanel. This is a nuisance.
Contrast that with my shell script which, once installed into Cron on the shared hosting, will automatically do the first 3 of those with no user intervention—you'll get an e-mail every 70 days containing the new cert and you only have to paste it up into CPanel—just one manual action (that you'll be reminded to do via e-mail, so you don't even have to keep track of it yourself).
Obviously the better solution would be to change providers, but if you're stuck on namecheap I think using a cron script on the shared hosting with manual uploading only of the cert is about as easy as it gets.
Namecheap interface silently truncates these records, leading to serious problems, particularly with DKIM signatures that require strong encryption keys. This oversight can result in email deliverability issues, which is unacceptable for anyone who relies on secure communication. I discovered this issue while working on a project with https://bizistech.com/, where precise DNS settings were crucial for maintaining the integrity of our email campaigns.
It seems that Namecheap has grown complacent in their position within the industry. Instead of innovating and improving their services, they’ve allowed critical flaws to persist. Additionally, their newly designed user interface is a step backward, complicating rather than enhancing the user experience. Unfortunately, if they continue down this path, they risk losing more customers like me who demand reliability and functionality.
I wasn't looking for an api but a way to use certbot in their shared server.
I was able to do it on my Ubuntu box and then upload/paste/install in Namecheap
https://medium.com/@tsui.gordon.9/generate-let-encrypt-ssl-certificate-manually-using-the-http-challenge-64b14750e3f8