Thanks.
On 1/29/2019 11:19 PM, Dave Jones wrote:
> On 1/29/19 1:35 PM, Kevin A. McGrail wrote:
>> On 1/29/2019 2:25 PM, Dave Jones wrote:
>>> On 1/29/19 10:20 AM, Bill Cole wrote:
On 29 Jan 2019, at 10:25, Kevin A. McGrail wrote:
>>>
>>> So is this fixed on the sa-vm1.apache.org server or do
On 1/29/19 1:35 PM, Kevin A. McGrail wrote:
On 1/29/2019 2:25 PM, Dave Jones wrote:
On 1/29/19 10:20 AM, Bill Cole wrote:
On 29 Jan 2019, at 10:25, Kevin A. McGrail wrote:
So is this fixed on the sa-vm1.apache.org server or do I need to fix
it still?
FYI, I found a better method for LE verif
On 29 Jan 2019, at 14:25, Dave Jones wrote:
So is this fixed on the sa-vm1.apache.org server or do I need to fix
it still?
I was relating work I did for a PCCC customer machine (which is why
Kevin was aware of it) NOT sa-vm1. If you're familiar with how sa-vm1
was set up, it may be best that
On 1/29/19 10:20 AM, Bill Cole wrote:
On 29 Jan 2019, at 10:25, Kevin A. McGrail wrote:
FYI, I think this is your territory, Dave
Bill had some interesting experience with the issue so cc'ing him.
Only "interesting" because I didn't trust the simplicity of the fix.
All I had to do on a fair
ew directories got modified, but no remaining files
were, so the only clear evidence of this was in the certbot debug log.
In short: I expected a failure that I'd need to work around but that
didn't happen. It just worked.
---- Forwarded Message ----
Subject:A
FYI, I think this is your territory, Dave
Bill had some interesting experience with the issue so cc'ing him.
Forwarded Message
Subject: Action required: Let's Encrypt certificate renewals
Date: Tue, 29 Jan 2019 02:14:39 +
From: nore...@letsencrypt.or
Hello,
Action may be required to prevent your Let's Encrypt certificate renewals
from breaking.
If you already received a similar e-mail, this one contains updated
information.
Your Let's Encrypt client used ACME TLS-SNI-01 domain validation to issue
a certificate in the past 60 days. Below is a
