Enable Let's Encrypt Auto-renewal to work with .htaccess redirects in place
When a website is SSL secured (https) it is recommended to have redirect rules in place which enforce https (redirect http to https) and of course redirecting to one version (www vs non-www).
It appears that the Let's Encrypt Auto-Renewal does not work. It will fail saying there are htacces rules restricting it from working. I am not sure if this is an issue for Cloudways to fix, or Let's Encrypt.
In either case, the solution provided by Cloudways support is to:
1. Temporarily rename your .htaccess (so it is not in effect)
2. REVOKE your Let's Encrypt Certificate
3. Install a new Let's Encrypt Certificate
4. Revert the name of your .htaccess (so it is back in effect)
(note, even if you remove your .htaccess in step 1, the manual "Renew Now" will say it worked, but it will not work, the old certificate will remain)
I would like to think there is a long term solution whereby the auto-renew will work. Especially since these redirect rules should in fact be in place (if you are not redirection all variants of your website to a single variant, you do not have your site setup correctly).
Is there some way for this to be resolved?
We have resolved this issue, an update was deployed on all customer’s servers.
LE SSL installation is now independent of rules added in htaccess, now users just have to make sure that the domain is added in the domain section of the application and the domain is pointing to Cloudways server, any rules in htaccess will not conflict with SSL installations.