Skip to content

Diagnosing issues

Jump to bottom
Nate McMaster edited this page May 26, 2020 · 2 revisions

Here are some tips for diagnosing issues with LettuceEncrypt.

Enable trace logging

Trace logging includes more details about what LettuceEncrypt is going. In a typical ASP.NET Core project using Microsoft's built-in logger, you can enable trace logging with 'appsettings.json' like this:

{
  "Logging": {
    "LogLevel": {
      "LettuceEncrypt": "Trace"
    }
  }
}

Then, look in your log output for statements coming from "LettuceEncrypt.*" loggers. Example:

info: LettuceEncrypt.Internal.AcmeCertificateLoader[0]
      Using existing account for mailto:it-admin@example.com

When sharing this in a GitHub issue, consider attaching the log as a .txt file or using https://gist.github.com as logs can be long and hard to view in an issue thread.

Clone this wiki locally