Renewal not working


#1

My domain is: www.heliosp2p.com

This is the output of my letsencrypt.log file :
HTTP 200
Server: nginx
Content-Type: application/json
Content-Length: 1787
X-Frame-Options: DENY
Strict-Transport-Security: max-age=604800
Expires: Wed, 02 Jan 2019 15:19:28 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Wed, 02 Jan 2019 15:19:28 GMT
Connection: keep-alive

{
“identifier”: {
“type”: “dns”,
“value”: “www.heliosp2p.com
},
“status”: “invalid”,
“expires”: “2019-01-09T15:19:23Z”,
“challenges”: [
{
“type”: “dns-01”,
“status”: “invalid”,
“url”: “https://acme-v02.api.letsencrypt.org/acme/challenge/aRo9sKsjnrPPHdqKYnD9ntZsFQrb9JnwJt3W5_kX7VU/10991433265”,
“token”: “e2hMD1uZtCJJpBZNYmzlIJl86ej0xywdne03ohFB1xg”
},
{
“type”: “tls-alpn-01”,
“status”: “invalid”,
“url”: “https://acme-v02.api.letsencrypt.org/acme/challenge/aRo9sKsjnrPPHdqKYnD9ntZsFQrb9JnwJt3W5_kX7VU/10991433266”,
“token”: “_e0wxRz6wrFh8K_3Pl0sUWRQ4f4aBHNeW1-YJBH3lTw”
},
{
“type”: “tls-sni-01”,
“status”: “invalid”,
“url”: “https://acme-v02.api.letsencrypt.org/acme/challenge/aRo9sKsjnrPPHdqKYnD9ntZsFQrb9JnwJt3W5_kX7VU/10991433267”,
“token”: “RlrE36dkOV9yIN7z-RV4Enu7ZQFxifzUJBjR9vNua5U”
},
{
“type”: “http-01”,
“status”: “invalid”,
“error”: {
“type”: “urn:ietf:params:acme:error:unauthorized”,
“detail”: “Invalid response from http://www.heliosp2p.com/.well-known/acme-challenge/z708BJ2tDhVH89nbndWpiUygz_tSZjyTSzx46yryCIk [13.126.145.58]: 500”,
“status”: 403
},
“url”: “https://acme-v02.api.letsencrypt.org/acme/challenge/aRo9sKsjnrPPHdqKYnD9ntZsFQrb9JnwJt3W5_kX7VU/10991433268”,
“token”: “z708BJ2tDhVH89nbndWpiUygz_tSZjyTSzx46yryCIk”,
“validationRecord”: [
{
“url”: “http://www.heliosp2p.com/.well-known/acme-challenge/z708BJ2tDhVH89nbndWpiUygz_tSZjyTSzx46yryCIk”,
“hostname”: “www.heliosp2p.com”,
“port”: “80”,
“addressesResolved”: [
“13.126.145.58”
],
“addressUsed”: “13.126.145.58”
}
]
}
]
}

My web server is (include version): Apache

The operating system my web server runs on is (include version): Ubuntu

My hosting provider, if applicable, is:AWS

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


#2

Hi @NMeyen

checking your domain (via https://check-your-website.server-daten.de/?q=heliosp2p.com ), most works. But your /.well-known/acme-challenge subdirectory has a http status 500. That means, Letsencrypt can’t validate your file / domain:



The redirect http -> https isn’t a problem. But why is there a http status 500?


#3

Hi, I changed the config now. The 500 error should not be there any more.


#4

This is the latest error . Now it is showing a 404 error.


#5

A 404 is good. Now create a test file (file name 1234) in

/.well-known/acme-challenge

create the two directories in your webroot, if they don’t exist.

Then try to load this testfile with your browser:

http://heliosp2p.com/.well-known/acme-challenge/1234

If this works, you have your correct webroot. So you can use

certbot run -a webroot -i apache -w yourWebRoot -d example.com

#6

What version of Ubuntu?


Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:

I ran this command:

It produced this output:


#7

Ubunutu 14.04.5 LTS - trusty


#8

closed #9

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.