I follow this procedure: How to create a "Let's Encrypt" certificate on Windows
at step 2, creating certificate got time out with following:
I follow this procedure: How to create a "Let's Encrypt" certificate on Windows
at step 2, creating certificate got time out with following:
Hello @Cannafar, welcome to the Let's Encrypt community.
When you opened this thread in the Help section, you should have been provided with a questionnaire. Maybe you didn't get it somehow (which is weird), or you've decided to delete it. In any case, all the answers to this questionnaire are required:
Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is:
I ran this command:
It produced this output:
My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don't know):
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
The version of my client is (e.g. output of certbot --version
or certbot-auto --version
if you're using Certbot):
Thank you for assisting us in helping YOU!
Maybe related to Stuck at connection/GET-request to Letsencrypt ACME API · Issue #1903 · win-acme/win-acme · GitHub
The developer of win-acme has mostly moved to their new fork of that app, GitHub - simple-acme/simple-acme: A simple cross platform ACME client (for use with Let's Encrypt et al.)
Alternatively you could try https://certifytheweb.com (which I develop) to see if you have a general connectivity problem that's affecting communication with Let's Encrypt.
You should at least open a web browser on the server and try to access https://acme-v02.api.letsencrypt.org/ and if that doesn't work then you know it's a firewall or configuration problem.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.