Hi all. My site is hosted by Go Daddy, on one of their shared hosting plans. What is the current status of Go Daddy support for Let’s Encrypt? This previous post indicates that my only recourse is to use a web-based service like ZeroSSL212 to manually generate certificates, then paste into the GoDaddy control panel. This would need to be repeated approximately every three months. Is this still the case?
Thanks in advance.
Although some of the people around here may have an answer for that, I would recommend to forward your question to the support team of your provider first.
AFAIK, status is the same as in the previous post. If you are using Apache, here’s a guide that could be helpful: https://www.godaddy.com/help/install-a-lets-encrypt-ssl-apache-20245
@jple thanks for that. The link you provided for Apache could be applicable to me. I’ll take a look. edit: One prerequisite of those instructions is, “Your domain is pointed to your server.” How exactly do I check this?
@bytecamp I will also ask Go Daddy. But in my experience, since they offer paid SSL service, I am fairly confident this will be the only solution they describe, even if others exist.
Using a third-party service can streamline things, but isn’t required.
You can run the certbot client on your computer (or webserver) and perform a “manual” authentication, where you will be prompted to place a file on the webserver OR create a DNS entry. That will generate the certificates needed, which you then manually install onto your host’s account dashboard.
@jvanasco thanks for that info. Just so I’m clear though, when you use the term ‘third-party service,’ you are referring to Certbot or ZeroSSL–correct? And am I correct that using those methods would be an alternative to the Install a Let’s Encrypt SSL (Apache) instructions? It is these instructions that I will probably pursue, as they seem relatively straightforward.
Thanks.
The “letsencrypt” software that the GoDaddy tutorial refers to is Certbot; it’s just the old name for Certbot. Despite the use of the old name, the GoDaddy tutorial will result in obtaining the most recent version of the software.
https://certbot.eff.org/ has our own documentation for Certbot, which is hopefully a little more complete and a little more up-to-date.
I think @jvanasco was only referring to ZeroSSL as a third-party service in this case.
@cagross Certbot will not work on shared hosting. I am writing a script that will do complete automation (including SSL installation) of Let’s Encrypt on shared hosting like Godaddy. There are two system requirements for my script:
Do you have these?
@anindya Thanks for the reply. You say that Certbot will not work on shared hosting. Is this to say that these instructions do not apply to shared hosting? @schoen has said those instructions consists of installing and using Certbot. But those instructions do not mention anything about shared hosting.
@anindya, to answer your questions about requirements: I have cPanel, and I have SSL enabled in cPanel. But I’m not sure if I have SSL enabled in cPanel API–how do I check that?
@cagross My pleasure.
Certbot is written in python. Certbot needs root access. Any shared hosting don’t provide root access.
Please click ‘SSL/TLS’ option in your cPanel. In next page, if you see ‘Install and Manage SSL for your site (HTTPS)’ and a link called ‘Manage SSL sites’. Click on the link. If you see a form like the screenshot below, then most probably SSL installation feature is enabled for the cPanel API as well.
certbot does not require root access. https://certbot.eff.org/faq/#does-certbot-require-root-administrator-privileges
The most popular authenticators and features require root access, however one can use certbot with manual or webroot challenges to complete HTTP or DNS verification and obtain certificates that are manually installed.
It much easier (and recommended) to use certbot if you have root access, as everything is fully automated and there is amazing integration with web-servers.
Is complete automation possible with certbot and without root access?
Obtaining the certificates can be automated via the webroot plugin, but they need to be manually installed.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
