Problems installing a Let’s Encrypt certificate? This might be the solution
A check that Let's Encrypt performs can drive you crazy — here we give you the solution.
Today something happened to me that I want to share with you: when installing a Let’s Encrypt certificate on my hosting for a new domain, it installed on the first try and without problems on the main domain, yet it would not install by any means on a subdomain.
What problem did we have?
The problem is convoluted, but the solution is very easy:
The Let´s Encrypt tool always checks the domain or subdomain you specify and its www version, so subdomain.domain.com and www.subdomain.domain.com must both exist for the certificate to install correctly.
What is the solution?
By going to your DNS and adding the subdomain with the www prefix, the matter will be resolved in a few minutes — although you can be racking your brains for quite a while and searching the internet like crazy to find this solution.
Keep the patch to avoid problems
Once the certificate is installed, my recommendation is to keep that subdomain in the DNS, or you will have problems with the renewal of the certificates, which with Let’s Encrypt must be done every 90 days.
We audit and fix WordPress and Laravel installations every week.