Kestrel could not be started.

[W-Maxo]

Dear @ffMathy

Kestrel could not be started when used "https://" + DomainToUse.

[OlegJakushkin]

Encountered the same exact problem when publishing into Portable build on Windows server.

Solution:

1. Add cert. persistence code alike

            services.AddFluffySpoonLetsEncryptCertificatePersistence(
                async (key, bytes) => await File.WriteAllBytesAsync("certificate_" + key + ".pfx", bytes),
                async (key) =>
                {
                    byte[] result = null;
                    try
                    {
                        result = await File.ReadAllBytesAsync("certificate_" + key + ".pfx");
                    }
                    catch (Exception e)
                    {
                        //Log stuff
                    }

                    return result;
                });

2. Add localhost certificate via cmd

dotnet dev-certs https --trust

3. Compile, publish, Run once - it will generate certificates
4. Revoke localhost certificate via cmd-> mmc-> file -> Add/Remove -> Certificates -> My User -> Finish -> Ok; In Personal certificates you'll find an item to remove.
5. In appsettings.json add something like:

{
  "Logging": {
    "LogLevel": {
      "Default": "Information",
      "Microsoft": "Warning",
      "Microsoft.Hosting.Lifetime": "Information"
    }
  },
  "AllowedHosts": "*",
   "Kestrel": {
    "Certificates": {
      "Default": {
        "Path": "./certificate_Site.pfx",
        "Password": "FluffySpoon"
      }
    }
  }
}

Service\App will run. And display stuff like this:

Yet this bug probably kills all stuff related to certificate autoupdate and certificate password dynamical changes...

[ffMathy]

Don't have a lot of time lately. PRs are welcome and appreciated! ❤️🙏

[MarkCiliaVincenti]

Have the same issue running Kestrel on Linux, .NET 5

FluffySpoon.AspNet.LetsEncrypt 1.163 works fine
FluffySpoon.AspNet.EncryptWeMust 1.169 and 1.171 throw that exception

[MarkCiliaVincenti]

Gave up and revered back to FluffySpoon.AspNet.LetsEncrypt. Too many bugs with FluffySpoon.AspNet.EncryptWeMust and the project looks dead.

[she2]

I am having this same issue running Kestrel on Linux with .Net 6

[MarkCiliaVincenti]

I am having this same issue running Kestrel on Linux with .Net 6

I ended up creating https://www.nuget.org/packages/TlsCertificateLoader/ which I'm using with the industry-standard Certbot handling the actual renewals. This package allows loading of TLS (HTTPS) certificates for .NET 6.0 Kestrel web applications, allowing for refreshing of certificates as well as compatibility with HTTP/3, and tested well on Linux.