You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 11, 2020. It is now read-only.
Naturally acmeproxy has to encrypt its own communication. Therefore we have to obtain a certificate for the public instance of acmeproxy using the acme-client operation mode.
Implementation note:
Upon startup acmeproxy checks if it already has a certificate for itself. If not it uses the self-test endpoint (#7) to check if the DNS server already has been configured correctly. Then it tries to obtain a certificate for itself. If the self-test fails acmeproxy waits for an configurable amount of time and retries to obtain a certificate.
The text was updated successfully, but these errors were encountered:
Naturally
acmeproxy
has to encrypt its own communication. Therefore we have to obtain a certificate for the public instance of acmeproxy using theacme-client
operation mode.Implementation note:
Upon startup
acmeproxy
checks if it already has a certificate for itself. If not it uses the self-test endpoint (#7) to check if the DNS server already has been configured correctly. Then it tries to obtain a certificate for itself. If the self-test failsacmeproxy
waits for an configurable amount of time and retries to obtain a certificate.The text was updated successfully, but these errors were encountered: