Cerbot Renewal - Fails with Invalid Response

Help
1

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:
inside.thefamilycrypt.com

I ran this command:
certbot renew

It produced this output:

Processing /etc/letsencrypt/renewal/inside.thefamilycrypt.com.conf

Cert is due for renewal, auto-renewing…
Plugins selected: Authenticator standalone, Installer None
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for inside.thefamilycrypt.com
Waiting for verification…
Cleaning up challenges
Attempting to renew cert (inside.thefamilycrypt.com) from /etc/letsencrypt/renewal/inside.thefamilycrypt.com.conf produced anunexpected error: Failed authorization procedure. inside.thefamilycrypt.com (http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://inside.thefamilycrypt.com/.well-known/acme-challenge/bcYkXIC6GmE6ZyNNV3ANl0cb4olpQK-myQtSfeTCEuI [160.2.27.72]: “\r\n400 The plain HTTP request was sent to HTTPS port\r\n<body bgcolor=“white”>\r\n

400 B”. Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/inside.thefamilycrypt.com/fullchain.pem (failure)

All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/inside.thefamilycrypt.com/fullchain.pem (failure)

1 renew failure(s), 0 parse failure(s)

IMPORTANT NOTES:

  • The following errors were reported by the server:

    Domain: inside.thefamilycrypt.com
    Type: unauthorized
    Detail: Invalid response from
    http://inside.thefamilycrypt.com/.well-known/acme-challenge/bcYkXIC6GmE6ZyNNV3ANl0cb4olpQK-myQtSfeTCEuI
    [160.2.27.72]: “\r\n400 The plain HTTP request
    was sent to HTTPS port\r\n<body
    bgcolor=“white”>\r\n

    400 B”

    To fix these errors, please make sure that your domain name was
    entered correctly and the DNS A/AAAA record(s) for that domain
    contain(s) the right IP address.
    My web server is (include version):
    nextcloud 15.0.5
    The operating system my web server runs on is (include version):
    unraid 6.6.7

My hosting provider, if applicable, is:

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

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot): 31

2

Hi @ribbitmckenzie

checking your configuration there is an error ( https://check-your-website.server-daten.de/?q=inside.thefamilycrypt.com ):

Domainname Http-Status redirect Sec. G
• http://inside.thefamilycrypt.com/
160.2.27.72 400 0.333 M
Bad Request
• https://inside.thefamilycrypt.com/
160.2.27.72 302 https://inside.thefamilycrypt.com/index.php/login 3.043 A
• https://inside.thefamilycrypt.com/index.php/login 200 3.113 A
• https://inside.thefamilycrypt.com:80/
160.2.27.72 302 https://inside.thefamilycrypt.com/index.php/login 2.550 Q
Visible Content:
• http://inside.thefamilycrypt.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
160.2.27.72 400 0.333 M
Bad Request
Visible Content: 400 Bad Request The plain HTTP request was sent to HTTPS port nginx/1.14.2

If you use http-01 validation, Certbot creates a file in /.well-known/acme-challenge, Letsencrypt checks that file.

Your port 80 is open, this is required. But it looks that you have a port forward

external port 80 ->> internal port 443

400 Bad Request The plain HTTP request was sent to HTTPS port nginx/1.14.2

That's wrong.

Your external port 80 must be forwarded to the internal port 80, there should be a running webserver with http. This webserver may send a redirect to https.

3

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