TLS 1.0 required? about acmesharp HOT 6 CLOSED

https://blogs.perficient.com/2016/04/28/tsl-1-2-and-net-support/

In PWSH, you can also do:

[System.Net.ServicePointManager]::SecurityProtocol = "Tls12";

from acmesharp.

Thank you. I tried this but I still get errors when using the MSPC.
I get:
Could not validate the choosen hostname for the certificate. No certificate issued.
Here is the settings on the server.

I run all updates and all .NET versions updated.

from acmesharp.

Also, global system-wide changes:

# Set strong cryptography on 32 bit .Net Framework (version 4 and above) so TLS 1.2 or above it used
Set-ItemProperty -Path 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\.NetFramework\v4.0.30319' -Name 'SchUseStrongCrypto' -Value '1' -Type DWord
Set-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\.NetFramework\v4.0.30319' -Name 'SchUseStrongCrypto' -Value '1' -Type DWord

from acmesharp.

Hmm, not sure why you would get that particular error. What is MSPC?

Do you have any proxy services in the middle between your servers and the outside world?

from acmesharp.

Thank you.
I've applied your settings and restarted the server but I keep getting the same error.
If I enable TLS 1.0 all is OK.
And I use no proxy.

from acmesharp.

Hi again.
I found the problem for the last domains that had the problem.
They all run Umbraco.
I renamed the web.config installed Let's Encrypt and all OK.
I renamed the web.config back and all is OK.

from acmesharp.