[GH-ISSUE #184] Where is "api-certs" supposed to land? #76

New issue

Closed

opened 2026-03-13 15:41:34 +03:00 by kerem · 3 comments

kerem commented

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

Owner

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

The first time I tested on my personal server/domain, I ran acme-dns directly as root user at /root/go/bin/acme-dns and the api-certs directory appeared next to it shortly. I take it those will be stored at the executable's working directory?

On attempting to run acme-dns as a systemd service (with low-privilege acme-dns user) on our company's server/domain, we finally got the auto-certificate registration with Let's Encrypt. However I do not see any api-certs directory at the re-located /usr/local/bin/acme-dns executable directory, nor the home directory /var/lib/acme-dns (which hosts the database file).

Where is api-certs located in this context?

Originally created by @icelava on GitHub (Sep 18, 2019). Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/184 The first time I tested on my personal server/domain, I ran acme-dns directly as root user at /root/go/bin/acme-dns and the _api-certs_ directory appeared next to it shortly. I take it those will be stored at the executable's working directory? On attempting to run acme-dns as a systemd service (with low-privilege acme-dns user) on our company's server/domain, we finally got the auto-certificate registration with Let's Encrypt. However I do not see any api-certs directory at the re-located /usr/local/bin/acme-dns executable directory, nor the home directory /var/lib/acme-dns (which hosts the database file). Where is api-certs located in this context?

kerem closed this issue

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

kerem commented

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

Author

Owner

@lateagain commented on GitHub (Sep 18, 2019):

Have a look at issue 172 < https://github.com/joohoi/acme-dns/issues/172 > I had the same question/problem

@lateagain commented on GitHub (Sep 18, 2019): Have a look at issue 172 < https://github.com/joohoi/acme-dns/issues/172 > I had the same question/problem

kerem commented

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

Author

Owner

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

Have a look at issue 172 < #172 > I had the same question/problem

Hmmm, but the thing is, acme-dns runs fine with the low-privilege acme-dns user account. It definitely registered its own cert with LE, since we can interface with it on HTTPS. Where would "api-certs" be for this case?

@icelava commented on GitHub (Sep 19, 2019): > Have a look at issue 172 < #172 > I had the same question/problem Hmmm, but the thing is, acme-dns runs fine with the low-privilege acme-dns user account. It definitely registered its own cert with LE, since we can interface with it on HTTPS. Where would "api-certs" be for this case?

kerem commented

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

Author

Owner

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

For whatever reason, this time round I managed to find the api-certs directory at /usr/local/bin/acme-dns the directory of the executable. So it is indeed relative the the process' current working directory. Strange why it did not show up with ls so many times last week.

@icelava commented on GitHub (Sep 23, 2019): For whatever reason, this time round I managed to find the api-certs directory at /usr/local/bin/acme-dns the directory of the executable. So it is indeed relative the the process' _current working directory_. Strange why it did not show up with ls so many times last week.