Last updated on June 17th, 2018 at 10:57 am
If you are using Vesta Control panel to run your web project and you experience an error for letsencrypt such as the one below:
Error: Fetching https://www.bizanosa.com/.well-known/acme-challenge/ remote error: tls: handshake failure
Here is a quick fix for you.
Note that this fix only works for you iff (if and Only if ) you are using Cloudflare, if you are not using cloud flare then you will not get the answers in this post.
First of all this error comes about when VestaCp tries to automatically renew your Letsenrypt certificates.,
If you are using Cloudflare here is what you need to do:
STEP 1 : Log into Cloudflare
Log into your Cloudflare Account. Just go to https://dash.cloudflare.com
STEP 2 : Choose your website
Choose your website url on Cloud flare.
STEP 3 : Choose Advanced Settings
Under Your Website Home page Overview Choose Advanced, to reveal more options.
STEP 4 : Pause Cloud flare
Click on the Pause button, to pause cloudflare. DNS will continue working , however other services will be paused.
Remember that after you finish up with the next steps you will need to follow the above steps and reactivate / resume on Cloudflare for your Website.
Next steps involve manually recreating the LetsEncrypt Certificates.
STEP 5 : Log into Vesta CP and go to Web
On the Vesta CP dashboard, click on Web. Then choose to edit the Website for which you want to renew letsencrypt.
STEP 6 : Uncheck SSL / LetsEncrypt
Scroll down to SSL Support and uncheck Lets Encrypt Support .
Before you even do this, scroll down to see the NOT_BEFORE and the NOT_AFTER dates . They are located right under your lets Encrypt certificates.
Once you Uncheck LetsEncrypt SSL, Scroll down and click on Save.
STEP 7 : Generate a new Lets Encrypt Cert
After you save the changes, scroll down to SSL support. Ensure you check it.
Then check on Lets Encrypt Support .
Then scroll down and save.
STEP 8 : Final Steps
Refresh the page to see if the the NOT_BEFORE and the NOT_AFTER dates have changed. If yes, well and good. If not, try again.
Finally, go back to Cloudflare and resume the Cloud flare services for your website(s).