[GH-ISSUE #217] Allow specifying a custom ACME server for api.tls #102

New issue

Closed

opened 2026-03-13 15:46:47 +03:00 by kerem · 1 comment

kerem commented

2026-03-13 15:46:47 +03:00

Owner

Originally created by @emilazy on GitHub (Mar 19, 2020).
Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/217

This would make it possible to use acme-dns's integrated HTTPS API certificate machinery with non-Let's Encrypt ACME setups, which would also make end-to-end integration testing in NixOS easier; Pebble uses /dir as the ACME endpoint, so even shimming out the Let's Encrypt API domain name isn't enough to use it for this, unfortunately.

Example configuration syntax:

[api]
tls = "acme"
acme_server = "https://pebble.local/dir"

(Sorry for the flood of issues! I'm hoping to send PRs implementing this and other proposals soon if I can get around to it.)

Originally created by @emilazy on GitHub (Mar 19, 2020). Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/217 This would make it possible to use acme-dns's integrated HTTPS API certificate machinery with non-Let's Encrypt ACME setups, which would also make end-to-end integration testing in [NixOS](https://nixos.org/) easier; [Pebble](https://github.com/letsencrypt/pebble) uses `/dir` as the ACME endpoint, so even shimming out the Let's Encrypt API domain name isn't enough to use it for this, unfortunately. Example configuration syntax: ```toml [api] tls = "acme" acme_server = "https://pebble.local/dir" ``` (Sorry for the flood of issues! I'm hoping to send PRs implementing this and other proposals soon if I can get around to it.)