[GH-ISSUE #180] Where is api-certs? #78

New issue

Closed

opened 2026-03-13 15:41:34 +03:00 by kerem · 1 comment

kerem commented

2026-03-13 15:41:34 +03:00

Owner

Originally created by @icelava on GitHub (Sep 3, 2019).
Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/180

I am testing setting up ACME-DNS as its own HTTP server to auto-register its own certificate from LE.

tls = "letsencrypt"
acme_cache_dir = "api-certs"

Where is this api-certs located? I don't see anything at /etc/acme-dns/ nor ~/go/bin/

Originally created by @icelava on GitHub (Sep 3, 2019). Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/180 I am testing setting up ACME-DNS as its own HTTP server to auto-register its own certificate from LE. tls = "letsencrypt" acme_cache_dir = "api-certs" Where is this api-certs located? I don't see anything at /etc/acme-dns/ nor ~/go/bin/

kerem closed this issue

2026-03-13 15:41:40 +03:00

kerem commented

2026-03-13 15:41:45 +03:00

Author

Owner

@icelava commented on GitHub (Sep 3, 2019):

Ok I see it appear at ~/go/bin/api-certs/

That only appeared once I reset configuration for ACME-DNS to use back port 80/443 and it succeeded in obtaining a certificate from LE. I previously tested it with 81/444 to avoid clashing with Nginx which is operating in the same server, so it wasn't able to verify properly with LE in that state.

@icelava commented on GitHub (Sep 3, 2019): Ok I see it appear at ~/go/bin/api-certs/ That only appeared once I reset configuration for ACME-DNS to use back port 80/443 and it succeeded in obtaining a certificate from LE. I previously tested it with 81/444 to avoid clashing with Nginx which is operating in the same server, so it wasn't able to verify properly with LE in that state.

kerem referenced this issue

2026-03-13 16:15:13 +03:00

[PR #78] [MERGED] Added Posh-ACME to client list #279