letsencrypt-win-simple does not work on Server 2008 – FIXED

Credit to developer of LetsEncrypt-Win-SimpleĀ  – https://github.com/Lone-Coder/letsencrypt-win-simple

Some users working with version 1.9.1 will find the following error on server 2008 as TLS1.1 and TLS 1.2 are not available on this operating system.

==================================
Let’s Encrypt (Simple Windows ACME Client)
Renewal Period: 60
Certificate Store: WebHosting

ACME Server: https://acme-v01.api.letsencrypt.org/
Config Folder: C:\Users\administrator\AppData\Roaming\letsencrypt-win-simple\httpsacme-v01.api.letsencrypt.org
Certificate Folder: C:\Users\administrator\AppData\Roaming\letsencrypt-win-simple\httpsacme-v01.api.letsencrypt.org
System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. —> System.ComponentModel.Win32Exception: The client and server cannot communicate, because they do not possess a common algorithm at System.Net.SSPIWrapper.AcquireCredentialsHandle(SSPIInterface SecModule, String package, CredentialUse intent, SecureCredential scc)
at System.Net.Security.SecureChannel.AcquireCredentialsHandle(CredentialUse credUsage, SecureCredential& secureCredential)
at System.Net.Security.SecureChannel.AcquireClientCredentials(Byte[]& thumbPrint)
at System.Net.Security.SecureChannel.GenerateToken(Byte[] input, Int32 offset, Int32 count, Byte[]& output)
at System.Net.Security.SecureChannel.NextMessage(Byte[] incoming, Int32 offset, Int32 count)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
at System.Net.TlsStream.CallProcessAuthentication(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.ConnectStream.WriteHeaders(Boolean async)
— End of inner exception stack trace —
at System.Net.HttpWebRequest.GetResponse()
at ACMESharp.AcmeClient.RequestHttpGet(Uri uri)
at ACMESharp.AcmeClient.Init()
at LetsEncrypt.ACME.Simple.Program.Main(String[] args)
Press enter to continue.
==================================

The author has produced a fix for this – https://github.com/Lone-Coder/letsencrypt-win-simple/pull/268

However its not yet been complied into a release.

Therefore I have complied the EXE and I’m hosting it at https://www.ashleyunwin.com/wp-content/uploads/2017/01/letsencrypt.exe for download.
Simply install the latest build from – https://github.com/Lone-Coder/letsencrypt-win-simple/releases and then replace the EXE with the one I’m hosting.

WARNING: Please use only at your own risk, I have not inspected the code etc and make no warranties/assurances of the product! I take no liability of any problems/damage caused by using this product.