[GH-ISSUE #405] Unrecognized log level warning #229

New issue

Open

opened 2026-03-13 16:12:36 +03:00 by kerem · 0 comments

kerem commented

2026-03-13 16:12:36 +03:00

Owner

Originally created by @cwchristerw on GitHub (Feb 15, 2026).
Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/405

After upgrading to latest release I have multiple error entries due to Could not set up logging: unrecognized level: "warning". I suspect that this was caused due to changes in Refactoring (https://github.com/acme-dns/acme-dns/pull/325) PR changing Changed logging to use zap.Logger. I have tested instead of warning, you should use warn. There needs to be release that will update this value in config or separate code which keeps supporting this old value.

Also updating example config needs to reflect available options.

Originally created by @cwchristerw on GitHub (Feb 15, 2026). Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/405 After upgrading to latest release I have multiple error entries due to `Could not set up logging: unrecognized level: "warning"`. I suspect that this was caused due to changes in Refactoring (https://github.com/acme-dns/acme-dns/pull/325) PR changing `Changed logging to use zap.Logger`. I have tested instead of `warning`, you should use `warn`. There needs to be release that will update this value in config or separate code which keeps supporting this old value. Also updating example config needs to reflect available options.