Processing home.skywayskase.com
+ Checking domain name(s) of existing cert... unchanged.
+ Checking expire date of existing cert...
+ Valid till Aug 31 07:26:56 2018 GMT (Less than 30 days). Renewing!
+ Signing domains...
+ Generating private key...
+ Generating signing request...
+ Requesting new certificate order from CA...
+ Received 1 authorizations URLs from the CA
+ Handling authorization for home.skywayskase.com
+ 1 pending challenge(s)
+ Deploying challenge tokens...
+ Responding to challenge for home.skywayskase.com authorization...
+ Cleaning challenge tokens...
+ Challenge validation has failed :(
ERROR: Challenge is invalid! (returned: invalid) (result: {
"type": "http-01",
"status": "invalid",
"error": {
"type": "urn:ietf:params:acme:error:connection",
"detail": "Fetching https://home.skywayskase.com/.well-known/acme-challenge/kZX_tYz3pn1CiQNEllKJLfFcaR7AxDchOR24NcBw848: Error getting validation data",
"status": 400
},
"url": "https://acme-v02.api.letsencrypt.org/acme/challenge/3eHuPgwLAfH2f8DZDyyOp58mxcTjW5dvTvF02E3I9us/7038525351",
"token": "kZX_tYz3pn1CiQNEllKJLfFcaR7AxDchOR24NcBw848",
"validationRecord": [
{
"url": "http://home.skywayskase.com/.well-known/acme-challenge/kZX_tYz3pn1CiQNEllKJLfFcaR7AxDchOR24NcBw848",
"hostname": "home.skywayskase.com",
"port": "80",
"addressesResolved": [
"73.254.229.249"
],
"addressUsed": "73.254.229.249"
},
{
"url": "https://home.skywayskase.com/.well-known/acme-challenge/kZX_tYz3pn1CiQNEllKJLfFcaR7AxDchOR24NcBw848",
"hostname": "home.skywayskase.com",
"port": "443",
"addressesResolved": [
"73.254.229.249"
],
"addressUsed": "73.254.229.249"
}
]
})
My web server is (include version):
nginx/1.12.2
The operating system my web server runs on is (include version):
Asuswrt-merlin 384.5
I can login to a root shell on my machine (yes or no, or I don't know):
Yes
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
No
Additional Info:
I've been using let's encrypt for a few years now. I'm pretty sure I'm following the same steps that have worked for me in the past. I can't think of anything that's changed in my environment in the last 3 months.
Oh, there is a problem. Using my own tool download.exe:
D:>download Welcome to our server -h
Only SslPolicyErrors.RemoteCertificateChainErrors found
SSL error: RemoteCertificateChainErrors
Error (1): Der Server hat eine Protokollverletzung ausgeführt.. Section=ResponseHeader Detail=Auf CR muss LF folgen
ServerProtocolViolation
The certificate error isn't the problem, Letsencrypt ignores that. But http headers must have two line-ends: Character 13 and Character 10 (CR + LF).
Perhaps this is the reason the Letsencrypt validator can't load your file.
So, I think I understand a little more about issue, but I’m still not sure what (file?) I need to change to get this working again… Or, why it has worked in the past and it’s just now not working correctly this renewal.