Failed authorization procedure


#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: techeleza.com

I ran this command: sudo certbot --nginx -d techeleza.com -d www.techeleza.com

It produced this output:

Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator nginx, Installer nginx
Enter email address (used for urgent renewal and security notices) (Enter ‘c’ to
cancel): johnpaulgitata@gmail.com
Starting new HTTPS connection (1): acme-v02.api.letsencrypt.org


Please read the Terms of Service at
https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf. You must
agree in order to register with the ACME server at
https://acme-v02.api.letsencrypt.org/directory


(A)gree/©ancel: A


Would you be willing to share your email address with the Electronic Frontier
Foundation, a founding partner of the Let’s Encrypt project and the non-profit
organization that develops Certbot? We’d like to send you email about our work
encrypting the web, EFF news, campaigns, and ways to support digital freedom.


(Y)es/(N)o: Y
Starting new HTTPS connection (1): supporters.eff.org
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for techeleza.com
http-01 challenge for www.techeleza.com
nginx: [warn] conflicting server name “techeleza.com” on 0.0.0.0:80, ignored
nginx: [warn] conflicting server name “www.techeleza.com” on 0.0.0.0:80, ignored
Waiting for verification…
Cleaning up challenges
nginx: [warn] conflicting server name “techeleza.com” on 0.0.0.0:80, ignored
nginx: [warn] conflicting server name “www.techeleza.com” on 0.0.0.0:80, ignored
Failed authorization procedure. www.techeleza.com (http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://www.techeleza.com/.well-known/acme-challenge/_qb7AAhN3PEeI5OzlGAh5eR6hzFoShoOC1GlLgmVNug: "\n<html lang=“en”>\n\n <meta http-equiv=“content-type” content=“text/html; charset=utf-8”>\n Page not ", techeleza.com (http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://techeleza.com/.well-known/acme-challenge/0_aLAfVYbRFbuFUV2YfaRh67ZBWx0vNZcPsCsMZ58yo: "\n<html lang=“en”>\n\n <meta http-equiv=“content-type” content=“text/html; charset=utf-8”>\n <meta name=“robo”

IMPORTANT NOTES:

  • The following errors were reported by the server:

    Domain: www.techeleza.com
    Type: unauthorized
    Detail: Invalid response from
    http://www.techeleza.com/.well-known/acme-challenge/_qb7AAhN3PEeI5OzlGAh5eR6hzFoShoOC1GlLgmVNug:
    "\n<html lang=“en”>\n\n <meta
    http-equiv=“content-type” content=“text/html; charset=utf-8”>\n

    Page not "

    Domain: techeleza.com
    Type: unauthorized
    Detail: Invalid response from
    http://techeleza.com/.well-known/acme-challenge/0_aLAfVYbRFbuFUV2YfaRh67ZBWx0vNZcPsCsMZ58yo:
    "\n<html lang=“en”>\n\n <meta
    http-equiv=“content-type” content=“text/html; charset=utf-8”>\n

    <meta name=\"robo"

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

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

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

Why I’m I getting this error while like 3 months ago, I had secured a previous domain with the same procedure and it worked well. ?


#2

You might have a duplicate dns configuration entry.
Please try to use nginx -T to check your Nginx configuration. (You could share it to us if you have no clue…)

Thank you


#3

It looks very likely to be the same problem as what you’re experiencing with your other domain…