In early 2018, SiteGround made a change to how their Let’s Encrypt SSL certificates are issued and renewed.
If you are using Cloudflare, it may not renew successfully the next time the auto renewal runs, which is every 90 days.
See how to easily issue a new SSL certificate.
You can even do this prior to the next renewal.
NOTE: If your certificate has already renewed in 2018, you may not need to do this process. But, it doesn’t hurt to do it, so you might as well, to ensure your renewal is on the new system at SiteGround.
NOTE: You only need to do this once. Your renewals should remain on the new system hereafter.
Log into your Cloudflare account and click on the domain you want to use.
Go to the Overview screen.
In the first module, click the Advanced link.
Click the Pause button, then click Ok in the pop up.
This will allow all links direct access to the host, instead of going through Cloudflare.
Stay logged into Cloudflare, as we will return to it shortly.
Check Your Current Certificate
From your SiteGround cPanel, go to SSL/TLS Manager.
Click on the CRT section link.
Scan the list and find the most recent certificate date.
It should be the one that did not renew properly.
Or, you may not see an SSL certificate listed for your domain if it has already expired.
Use the Let’s Encrypt Tool
Return to the cPanel home and go to Let’s Encrypt.
Go to the lower section for Install new Let’s Encrypt Certificate.
Ensure the correct domain is selected.
Click the Install button.
You will see several messages appear in a pop up lightbox.
The final message should be that it successfully installed.
Click the Okay button.
Recheck Your Certificate List
Return to cPanel and the SSL/TLS Manager.
Then click the CRT link again.
In the list, you should see a certificate with an expiration date 3 months in the future.
Return to Cloudflare.
Click the Resume button.
That Should Do It!!
Your SSL certificate should continue to auto renew from now on.
And you should not need to take this manual action again.
Need More HTTPS Help?
I do full HTTPS conversions, meaning no plugin or host side trickery. And you get all the security headers that browsers like Chrome require now too.