Issue Description When multiple ACME providers are configured using the same Let’s Encrypt directory URL, they cannot be distinguished in the Domain TLS settings. For example, separate ACME providers may be configured for different tenants, but each provider is displayed only as: https://acme-v02.…

For anyone else following this thread, in v0.16.18 this is now the interface. You will still need to cross reference the URI back to the ACME Providers, but at least you can narrow it down. [image]

This confirms the AcmeProvider object schema has no name/label field, just id, directory URL, contact, etc, so the WebUI has nothing but the id (an opaque string) or directory URL to display, confirming the reported behavior is expected given current data model. Confirmed: the current AcmeProvider …

The new label fields are also all identical and do not provide any means of distinguishing the entries. [image]

Fixed. v0.16.18 will show the provider URL plus the unique accountUri instead of the email address. If that does not help, a new user defined description field has to be added to the schema as there are no other properties to uniquely identify a provider.

ACME Providers Are Indistinguishable in Domain TLS Settings

Issues

stalwart August 10, 2026, 2:41pm 3

Fixed in v0.16.17 (yet to be released).

ACME Provider Custom Name

ACME Provider Lists & Tenancy

Topic		Replies	Views
ACME Provider Custom Name Feature Ideas	1	32	August 10, 2026
ACME Provider Lists & Tenancy Feature Ideas	1	33	August 10, 2026
Not able to retrieve certificates through Let's encrypt ACME (behind caddy) - worked around Issues no-ai	7	232	June 15, 2026
ACME DNS-01 not issuing certificates Issues	3	74	July 18, 2026
Item references with multiple tenants Issues	2	24	May 28, 2026

ACME Providers Are Indistinguishable in Domain TLS Settings

Related topics