Renewal Error as "Initial Connection Failed"

Help
1

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: oshwaleducationtrust.org

I ran this command: wacs.exe as Run as administrator

It produced this output: Initial Connection failed

My web server is (include version): windows server 2016 standard

The operating system my web server runs on is (include version):

My hosting provider, if applicable, is: localhost IIS10

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):

2

Let's Encrypts API recently changed from an RSA certificate to an ECDSA certificate, this results in your server having to communicate with a slightly different set of TLS Cipher Suites. Older versions of Windows or those upgraded in-place from older versions need additional configuration to enable the TLS Cipher Suites required.

Here is a related article for a different ACME tool:

4 Likes
3

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.