Originally created by @tjharman on GitHub (Apr 26, 2018).
I am using this command to update my certificates:
`/usr/local/dehydrated/dehydrated -c -x -k ./beaker-ecc.sh -d muppetz.com -d beaker.muppetz.com -d www.muppetz.com -d tjharman.com -d www.tjharman.com -d old.tjharman.com -d lice.muppetz.com -d gallery.tjharman.com -d matchboxdigital.co.nz -d www.matchboxdigital.co.nz -o /etc/letsencrypt/ecc -a secp384r1`
This is the log:
```
+ 10 pending challenge(s)
+ Deploying challenge tokens...
+ Responding to challenge for beaker.muppetz.com authorization...
+ Challenge is valid!
+ Responding to challenge for gallery.tjharman.com authorization...
+ Challenge is valid!
+ Responding to challenge for lice.muppetz.com authorization...
+ Challenge is valid!
+ Responding to challenge for matchboxdigital.co.nz authorization...
+ Challenge is valid!
+ Responding to challenge for muppetz.com authorization...
+ Challenge is valid!
+ Responding to challenge for old.tjharman.com authorization...
+ Challenge is valid!
+ Responding to challenge for www.matchboxdigital.co.nz authorization...
+ Challenge is valid!
+ Responding to challenge for www.muppetz.com authorization...
+ Challenge is valid!
+ Responding to challenge for www.tjharman.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://tjharman.com.well-known/acme-challenge/FnaK7v52ZkQn43VitAr9Vav9SriOxC4bFrg_RdvvHWg: Error getting validation data",
"status": 400
},
"url": "https://acme-v02.api.letsencrypt.org/acme/challenge/Gzt4EWQlA-3N1gF5m5RnL--1l-C431PLk2sJmgY-bRE/4389580035",
"token": "FnaK7v52ZkQn43VitAr9Vav9SriOxC4bFrg_RdvvHWg",
"validationRecord": [
{
"url": "https://tjharman.com.well-known/acme-challenge/FnaK7v52ZkQn43VitAr9Vav9SriOxC4bFrg_RdvvHWg",
"hostname": "tjharman.com.well-known",
"port": "443"
},
{
"url": "http://www.tjharman.com/.well-known/acme-challenge/FnaK7v52ZkQn43VitAr9Vav9SriOxC4bFrg_RdvvHWg",
"hostname": "www.tjharman.com",
"port": "80",
"addressesResolved": [
"103.247.152.88"
],
"addressUsed": "103.247.152.88"
}
]
})
```
For some reason my URL is http://tjharman.com.well-known ?
Is there a parsing error here?
I am using commit 89de83c99428481d880aac6f9702f4ecea38fa53
This is an issue with your webserver (probably Apache) configuration, not an issue with dehydrated. Fix your SSL redirect by adding a / to the end.
@lukas2511 commented on GitHub (Apr 27, 2018):
This is an issue with your webserver (probably Apache) configuration, not an issue with dehydrated. Fix your SSL redirect by adding a `/` to the end.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @tjharman on GitHub (Apr 26, 2018).
I am using this command to update my certificates:
/usr/local/dehydrated/dehydrated -c -x -k ./beaker-ecc.sh -d muppetz.com -d beaker.muppetz.com -d www.muppetz.com -d tjharman.com -d www.tjharman.com -d old.tjharman.com -d lice.muppetz.com -d gallery.tjharman.com -d matchboxdigital.co.nz -d www.matchboxdigital.co.nz -o /etc/letsencrypt/ecc -a secp384r1This is the log:
For some reason my URL is http://tjharman.com.well-known ?
Is there a parsing error here?
I am using commit
89de83c994@lukas2511 commented on GitHub (Apr 27, 2018):
This is an issue with your webserver (probably Apache) configuration, not an issue with dehydrated. Fix your SSL redirect by adding a
/to the end.@tjharman commented on GitHub (Apr 27, 2018):
OMG I was missing a /
I am so, so sorry for wasting your time.
@lukas2511 commented on GitHub (Apr 27, 2018):
@tjharman don't worry, I got used to this by now ;)
@tjharman commented on GitHub (Apr 27, 2018):
I'm sure, but I still made another small donation by way of apology.
@lukas2511 commented on GitHub (Apr 27, 2018):
@tjharman hehe, apology accepted ;)