There's a fairly good solution available with the current protocol,
which is to serve a (long lived) redirect from
/.well-known/acme-challenge/ on all of the servers to a different URL
that is always answered by the machine you run an ACME client on.
Are there any cases where that is sufficiently
This seems to be a common problem, so I opened a PR that someone on
that project can merge.
On 4 December 2015 at 08:08, Salz, Rich wrote:
>> Should I open an issue on the protocol draft repository? (Which I assume is
>> at [1])
>> [1]:
On Fri, Dec 4, 2015 at 12:46 AM, Peter Eckersley wrote:
> There's a fairly good solution available with the current protocol,
> which is to serve a (long lived) redirect from
> /.well-known/acme-challenge/ on all of the servers to a different URL
> that is always answered by the