.NET 5 support

While setting up LettuceEncrypt (DigitalOcean droplet, .NET 5 RC, ASP.NET Core app via docker) I noticed the following warning:

warn: LettuceEncrypt.Internal.AcmeCertificateLoader[0]
      LettuceEncrypt can only be used with Kestrel and is not supported on Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServerImpl servers. Skipping certificate provisioning.

There’s a sanity check in https://github.com/natemcmaster/LettuceEncrypt/blob/main/src/LettuceEncrypt/Internal/AcmeCertificateLoader.cs that specifically checks the IServer instance is in fact a KestrelServer.

After checking Kestrel’s repo it appears there is now a KestrelServer and a KestrelServerImpl, both implementing IServer (KestrelServer wraps/decorates KestrelServerImpl).

Is this an easy fix or an indication of further differences in dotnet 3.1 vs 5 when it comes to Kestrel? How does .NET 5 support fit into the roadmap? Am I just dumb and misinterpreting something?

Thanks for your hard work!

[Fydar]

I’m using LettuceEncrypt 1.1.0-beta.73 on .NET 5 but I still get the same error:

LettuceEncrypt can only be used with Kestrel and is not supported on Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServerImpl servers. Skipping certificate provisioning.

Is there any kind of workaround?

The beta “preview” package does not have support for .NET 5. The full release 1.0.1 does have support for .NET 5.

You can use the version of the package from origin/main which contains the features and API of version 1.1.0-beta.73 and .NET 5 support.

We need a new preview package to be built and deployed on NuGet.

[codingyourlife]

This issue is open since October and I tried the last 3 pre-releases and they all fail for me in .NET5. Also there is this open issue: https://github.com/natemcmaster/LettuceEncrypt/issues/165 saying use pre-release because main version isn’t working.

Sorry but I give up on this package…