DEV Community

Discussion on: Let’s Encrypt SSL certificate in Namecheap AutoRenewal – Verified & working – Using ACME.sh

Collapse
 
arielyahav profile image
Ariel-Yahav

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.

Collapse
 
atomar profile image
Anuj Singh Tomar • Edited

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.