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 Dec 1, 2018. It is now read-only.
So we are moving all our systems from Linux to BSD and we want to use acme-client. We configure all our systems with ansible right now and we're not sure the best way to handle this situation.
If we are standing up a new www server that hosts a number of different domains, we can't just start nginx with our normal configuration because the certs don't yet exist on the system. We can't get the certs with acme-client because it depends on a nginx or apache config, there's no internal www server it can use like with the python version of letsencrypt.
So what is the best way for us to handle this? Do we have to generate a dummy config for nginx every time we add a new domain and load that up temporarily till we have the initial cert? Is there a better way?
Sorry if this is way out of scope for the issue tracker.
The text was updated successfully, but these errors were encountered:
So we are moving all our systems from Linux to BSD and we want to use acme-client. We configure all our systems with ansible right now and we're not sure the best way to handle this situation.
If we are standing up a new www server that hosts a number of different domains, we can't just start nginx with our normal configuration because the certs don't yet exist on the system. We can't get the certs with acme-client because it depends on a nginx or apache config, there's no internal www server it can use like with the python version of letsencrypt.
So what is the best way for us to handle this? Do we have to generate a dummy config for nginx every time we add a new domain and load that up temporarily till we have the initial cert? Is there a better way?
Sorry if this is way out of scope for the issue tracker.
The text was updated successfully, but these errors were encountered: