NameCheap doesn't support Let's Encrypt natively, But provides option so you can setup LetEncrypt SSL certificates using different utilities like getSSL or ACME.sh, having used both found acme.sh to be quite better and simple to use + it supports auto renewal too.
1 - Enable SSH to get into your shared hosting server with your cpanel username.(You can get keys & login from your terminal or use inbuilt capnel terminal for quick access)
2 - Get the certs
#Get acme.sh utility
curl https://get.acme.sh | sh
#Source the Environment variables
source ~/.bashrc
#Register your email with Lets's Encrypt to be notified any renewals issue
acme.sh --register-account --accountemail email@example.com
# At this moment a cron entry already has been setup for autorenewal which will auto renew after 60 days., You can update /dev/null to something like this if you need the log
crontab -l | grep acme.sh
10 0 * * * "/home/_CPANEL_USERNAME_/.acme.sh"/acme.sh --cron --home "/home/_CPANEL_USERNAME_/.acme.sh" >> /home/_CPANEL_USERNAME_/.acme_cron_log
4 – Issue a test cert to check if all working
#webroot will be any directory in which your domain exist, give path accordingly.
acme.sh --issue --webroot ~/public_html -d yourdomain.com --staging
5 – issue an actual Certificate
acme.sh --issue --webroot ~/public_html -d yourdomain.com --force
#In ourput you will see success if all goes fine & key/Certs/chaincerts/csr will be stored under below location, you can refer those if you intend to apply those using cpanel GUI manually
~/.acme.sh/yourdomain.com/
6 - Apply Cert to website using cPnel hook
acme.sh --deploy --deploy-hook cpanel_uapi --domain yourdomain.com
7 – You should be able to see your domain with SSL in cpanel under SSL/TLS -> Manage all certs
8 - Force HTTP-HTTPS redirection
If you see option to enable you can enforce HTTP from cpanel itself:
cPanel->Domains
In case it is greyed out, which could be in case you have multiple domains like www.yourdomain.com for which you don’t have the cert , Enable the redirection from “redirects” or simply add below lines in .htaccess file
#always backup as a thumb of rule
vi ~/public_html/.htaccess
Or
vi ./yourdomain.com/.htaccess
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
</IfModule>
9 – test your website in new window with URL: https://yourdomain.com or http://yourdomain.com( in http it should redirect automatically to https)
So you are all done now, If you need a more detailed Article you can checkout the original article on below link:
devops.egyan.space
Glad if this helped you, You can now buy me a coffee if this was helpful:
Top comments (26)
This is a bit of an old article, but still relevant. If anyone is following these steps, please be aware that in August of 2021, acme.sh began supporting multiple Certificate Authorities, defaulting to ZeroSSL. In order to use LetsEncrypt, you will need to provide the
--server letsencryptargument to the issue command. It would look something like this:acme.sh --issue --webroot ~/public_html --server letsencrypt -d yourdomain.com --forceGood to know , thanks for sharing
This is indeed an awsome tutorial as following it step by step works.
However the code below seemed not to work so i just skipped it
Thanks for the wonderful tutorial
Glad that it helped, that code worked fine for me, it is critical too, as i don't want to bother me with running this manually, cronjob takes care of autorenewal, have worked fine for me for more than a year :)
Just check the CPANEL_USername , it would be same id when you log in to your cpanel, it will show with below command on terminal run :
echo $USER
Or in Console note it under: General Information->Current User
The redirect method for www. has a snag. Most browsers seem to look for a
www.mydomain.comcert before following the redirect. This results in users seeing a warning and not redirecting.The solution is to add a second domain arg to each of the commands. EG:
You'll still want to add the redirect, but this will now avoid the error for users.
thanks so much! This really helped me!
Big Thanks!
Saving me lots of money :)
I was about to switch hosting provider to one that supports let's encrypt!
Had read this post before but it looked too complicated.
After some efforts and patience everything is working now and all my sites are secure, for free, with auto renew on! How cool!! :D
Much gratitude <3
Now what would make it perfect would be a script like :
/ssl domain.com
That would automatically do all the steps, including the www :D
This way it would save some time and avoid typos ^^
Thanks again!
This is a bit of an old article, but still relevant. If anyone is following these steps, please be aware that in August of 2021, acme.sh began supporting multiple Certificate Authorities, defaulting to ZeroSSL. In order to use LetsEncrypt, you will need to provide the
--server letsencryptargument to the issue command. It would look something like this:acme.sh --issue --webroot ~/public_html --server letsencrypt -d yourdomain.com --forceAfter command:
At this moment a cron entry already has been setup for autorenewal which will auto renew after 60 days., You can update /dev/null to something like this if you need the log
crontab -l | grep acme.sh
10 0 * * * "/home/CPANEL_USERNAME/.acme.sh"/acme.sh --cron --home "/home/CPANEL_USERNAME/.acme.sh" >> /home/CPANEL_USERNAME/.acme_cron_log
I have error: -bash: 10: command not found
This is great!
I keep getting stuck at the --staging issue stage, though. Any idea why I might be getting the following error code (35):
acme.sh --issue --webroot ~/public_html -d breastfeeding.london --staging
[Thu Feb 4 20:51:07 EST 2021] Using ACME_DIRECTORY: acme-staging-v02.api.letsencrypt.o...
[Thu Feb 4 20:51:10 EST 2021] Please refer to curl.haxx.se/libcurl/c/libcurl-err... for error code: 35
[Thu Feb 4 20:51:10 EST 2021] Can not init api.
[Thu Feb 4 20:51:10 EST 2021] Using CA: acme-staging-v02.api.letsencrypt.o...
[Thu Feb 4 20:51:19 EST 2021] Please refer to curl.haxx.se/libcurl/c/libcurl-err... for error code: 35
[Thu Feb 4 20:51:19 EST 2021] Can not init api.
[Thu Feb 4 20:51:19 EST 2021] Registering account: acme-staging-v02.api.letsencrypt.o...
[Thu Feb 4 20:51:22 EST 2021] Please refer to curl.haxx.se/libcurl/c/libcurl-err... for error code: 35
[Thu Feb 4 20:51:22 EST 2021] Could not get nonce, let's try again.
Check if ~/public_html exists Or if your website exits in a different folder , then replace the webroot like below:
acme.sh --issue --webroot ~/breastfeeding.london -d breastfeeding.london --staging
If still same issue check with namecheap support for below error:
CURLE_SSL_CONNECT_ERROR (35)
A problem occurred somewhere in the SSL/TLS handshake. You really want the error buffer and read the message there as it pinpoints the problem slightly more. Could be certificates (file formats, paths, permissions), passwords, and others.
Awesome! Great tutorial. Working very fine.
Pls tell me if I need to disable SSH access again, as the certificate installed successfully.
Check if any line break in the cron entry, it can happen when you copy pasted from here, ensure it is a single line without any new line.
Also regarding SSH Access best practice is to keep it disabled, you can enable it again whenever you need.
Thanks for the reply. It worked now.
This is a great step by step guide, you saved me hours of figuring this out on my own, thanks a lot!
Thanks for commenting, Glad that it helped.
Thanks for the post! It worked great the first time. However, I have a problem when doing this process for other domains in my shared hosting.
I'm getting an error 503 when I try to issue a test certificate. As far as I can see .well-know is blocking the request. Any idea of why it may happen?
Thanks for posting this. Breezy to follow, and now I shouldn't have to worry about this stuff for a while. I'd been doing it manually for a year now on four of my sites and it was a pain but worth not paying them.
thank you :) this was really helpful. 🪙
hi, thanks for tutorial. I'm getting a error when issue a cert for cpanel.domain.com and webmail.domain.com... the others like domain and mail.domain and domain.com was successful.
When trying issue a cert for webmail i'm getting multiple "processing" and timeout lines. I have a stelar plan from namecheap.
Peace.
This was very useful for me. Thank you!