Changed server and IP - continued errors

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: hoodoutdoors.com

I ran this command: sudo certbot renew --dry-run

It produced this output:

Saving debug log to /var/log/letsencrypt/letsencrypt.log


Processing /etc/letsencrypt/renewal/hoodoutdoors.com.conf


Cert is due for renewal, auto-renewing…
Plugins selected: Authenticator apache, Installer apache
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for hoodoutdoors.com
http-01 challenge for www.hoodoutdoors.com
Waiting for verification…
Cleaning up challenges
Attempting to renew cert (hoodoutdoors.com) from /etc/letsencrypt/renewal/hoodoutdoors.com.conf produced an unexpected error: Failed authorization procedure. hoodoutdoors.com (http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from https://hoodoutdoors.com/.well-known/acme-challenge/gS96pfWZvMZSKm81zyMkOzb5J43TD1SLHQEGIV2YXSk [134.209.79.158]: "<!doctype html>\n<html lang=“en-US”>\n\n<meta charset=“UTF-8”>\n<meta name=“viewport” content=“width=device-width, initial-sca”, www.hoodoutdoors.com (http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from https://hoodoutdoors.com/.well-known/acme-challenge/QN403ts6xPu_VaFQ_UJUoTx1MjEaKoWurn2Ig-mwJr8 [134.209.79.158]: "<!doctype html>\n<html lang=“en-US”>\n\n<meta charset=“UTF-8”>\n<meta name=“viewport” content=“width=device-width, initial-sca”. Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/hoodoutdoors.com/fullchain.pem (failure)


** DRY RUN: simulating ‘certbot renew’ close to cert expiry
** (The test certificates below have not been saved.)

All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/hoodoutdoors.com/fullchain.pem (failure)
** DRY RUN: simulating ‘certbot renew’ close to cert expiry
** (The test certificates above have not been saved.)


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

IMPORTANT NOTES:

  • The following errors were reported by the server:

    Domain: hoodoutdoors.com
    Type: unauthorized
    Detail: Invalid response from
    https://hoodoutdoors.com/.well-known/acme-challenge/gS96pfWZvMZSKm81zyMkOzb5J43TD1SLHQEGIV2YXSk
    [134.209.79.158]: "<!doctype html>\n<html
    lang=“en-US”>\n\n<meta charset=“UTF-8”>\n<meta
    name=“viewport” content=“width=device-width, initial-sca”

    Domain: www.hoodoutdoors.com
    Type: unauthorized
    Detail: Invalid response from
    https://hoodoutdoors.com/.well-known/acme-challenge/QN403ts6xPu_VaFQ_UJUoTx1MjEaKoWurn2Ig-mwJr8
    [134.209.79.158]: "<!doctype html>\n<html
    lang=“en-US”>\n\n<meta charset=“UTF-8”>\n<meta
    name=“viewport” content=“width=device-width, initial-sca”

    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.

  • Your account credentials have been saved in your Certbot
    configuration directory at /etc/letsencrypt. You should make a
    secure backup of this folder now. This configuration directory will
    also contain certificates and private keys obtained by Certbot so
    making regular backups of this folder is ideal.

My web server is (include version):

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

My hosting provider, if applicable, is: DigitalOcean

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): 0.28.0

I actually had to move two sites to a new account and thus server with Digitalocean. Both are giving me fits. I have researched and tried some of the things that I found recommended without luck. I then restored back to the original snapshot and pulled this information.

Thanks.

Hi @hood

if apache as authenticator doesn’t work, your configuration is buggy. Find your DocumentRoot of your https - vHost, then use it.

certbot run -a webroot -i apache -w yourDocumentRoot -d hoodoutdoors.com -d www.hoodoutdoors.com

I uninstalled and reinstall apache2 then certbot (because files were missing). It fixed the certificate and I am no longer receiving any errors through apache but the site is now saying it can’t be reached.

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