> Am 13.03.2018 um 21:43 schrieb William A Rowe Jr :
>
>> On Mon, Mar 12, 2018 at 6:23 AM, Eric Covener wrote:
>> On Mon, Mar 12, 2018 at 6:33 AM, Stefan Eissing
>> wrote:
>>>
Am 12.03.2018 um 11:23 schrieb Daniel Gruno :
Would it be possible to just have a link that always po
On Mon, Mar 12, 2018 at 6:23 AM, Eric Covener wrote:
> On Mon, Mar 12, 2018 at 6:33 AM, Stefan Eissing
> wrote:
>>
>>> Am 12.03.2018 um 11:23 schrieb Daniel Gruno :
>>>
>>> Would it be possible to just have a link that always points to the
>>> _current_ agreement, much like our docs have a /curre
After consultation with Let's Encrypt developers I opened a new ticket
at their server: https://github.com/letsencrypt/boulder/issues/3547
They seem to be willing to be more forgiving when checking the URL
and accept alternate links to the same document (as used by their site
and which let to our
On Mon, Mar 12, 2018 at 6:33 AM, Stefan Eissing
wrote:
>
>> Am 12.03.2018 um 11:23 schrieb Daniel Gruno :
>>
>> Would it be possible to just have a link that always points to the
>> _current_ agreement, much like our docs have a /current/ directory that
>> always fetches you the current 2.4 docs?
> Am 12.03.2018 um 11:23 schrieb Daniel Gruno :
>
> Would it be possible to just have a link that always points to the
> _current_ agreement, much like our docs have a /current/ directory that
> always fetches you the current 2.4 docs?
More a question for Let's Encrypt than us. Legally, that wou
Would it be possible to just have a link that always points to the
_current_ agreement, much like our docs have a /current/ directory that
always fetches you the current 2.4 docs?
On 03/12/2018 11:03 AM, Stefan Eissing wrote:
>
>
>> Am 12.03.2018 um 10:39 schrieb Luca Toscano :
>>
>> Hi Stefan!
> Am 12.03.2018 um 10:39 schrieb Luca Toscano :
>
> Hi Stefan!
>
> 2018-03-12 10:29 GMT+01:00 Stefan Eissing :
> The recommended URL in our docs is wrong. The wrong one was introduced in
> r1820464.
> Supposedly as a fix to PR 35622. The proposed patch in the PR 35622 however
> carries the cor
Hi Stefan!
2018-03-12 10:29 GMT+01:00 Stefan Eissing :
> The recommended URL in our docs is wrong. The wrong one was introduced in
> r1820464.
> Supposedly as a fix to PR 35622. The proposed patch in the PR 35622 however
> carries the correct URL. Not sure how that happened. It should be changed
The recommended URL in our docs is wrong. The wrong one was introduced in
r1820464.
Supposedly as a fix to PR 35622. The proposed patch in the PR 35622 however
carries the correct URL. Not sure how that happened. It should be changed in
the docs.
However:
The *really* correct URL, however, is
More complete log.
It is an hard error, as discussed here before, no need to do retries.
[md:warn] [pid 7232:tid 2416] (22)Invalid argument: acme problem
urn:acme:error:malformed: Provided agreement URL
[https://letsencrypt.org/documents/2017.11.15-LE-SA-v1.2.pdf] does not
match current agr
Have reports from users that have issues with mod_md :
[md:warn] [pid 7232:tid 2416] (22)Invalid argument: acme problem
urn:acme:error:malformed: Provided agreement URL
[https://letsencrypt.org/documents/2017.11.15-LE-SA-v1.2.pdf] does not
match current agreement URL
[https://letsencrypt.or
11 matches
Mail list logo
