Unable to connect to ACME server

[Jawed34]

A simple Windows ACMEv2 client (WACS)
Software version 2.1.18.1119 (release, pluggable, standalone, 64-bit)
Connecting to https://acme-v02.api.letsencrypt.org/...
Initial connection failed, retrying with TLS 1.2 forced
Unable to connect to ACME server
Scheduled task looks healthy
Please report issues at https://github.com/win-acme/win-acme

It was working fine but now I am getting this error.

[WouterTinus]

There must have been some change on your end then, as new bugs don't suddenly pop up in 3 year old software 😄. I'll convert this issue into a discussion.

[Jawed34]

I did not make any changes; it was working fine just able to connect server.
Even on browser https://acme-v02.api.letsencrypt.org is not opening.

[WouterTinus]

Even on browser https://acme-v02.api.letsencrypt.org is not opening

I think if you solve that problem first, win-acme will be fine afterwards. Talk to your network admin if needed

[mmunchandersen]

I'm also now getting this: Unable to connect to ACME server.

A simple Windows ACMEv2 client (WACS)
Software version 2.1.8.838 (RELEASE, PLUGGABLE)
ACME server https://acme-v02.api.letsencrypt.org/
No luck yet, attempting to force TLS 1.2...
Unable to connect to ACME server
IIS version 8.5
Running with administrator credentials
Scheduled task looks healthy
Please report issues at https://github.com/win-acme/win-acme

Invoke-WebRequest https://acme-v02.api.letsencrypt.org/ -UseBasicParsing
Invoke-WebRequest : The request was aborted: Could not create SSL/TLS secure channel.
At line:1 char:1

• Invoke-WebRequest https://acme-v02.api.letsencrypt.org/ -UseBasicParsing

•   + CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebException
    + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand
  
  

Did this change recently?
Any ideas?

[webprofusion-chrisc]

See this related guidance for a different ACME tool (same problem and same fix): https://community.certifytheweb.com/t/fix-could-not-create-ssl-tls-secure-channel-when-attempting-a-certificate-order-with-lets-encrypt-or-ca-acme-directory-is-not-accessible/2558

The issue is most likely caused by Let's Encrypts recent API changes requiring your server to talk to them using ECDSA TLS Cipher Suites which you probably don't have enabled.

[mmunchandersen]

See this related guidance for a different ACME tool (same problem and same fix): https://community.certifytheweb.com/t/fix-could-not-create-ssl-tls-secure-channel-when-attempting-a-certificate-order-with-lets-encrypt-or-ca-acme-directory-is-not-accessible/2558

The issue is most likely caused by Let's Encrypts recent API changes requiring your server to talk to them using ECDSA TLS Cipher Suites which you probably don't have enabled.

Thanks. IISCrypto by Nartac, Best practices worked for me