I ran this command: sudo certbot --nginx -d afrotechtrends.com -d www.afrotechtrends.com
It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator nginx, Installer nginx
Starting new HTTPS connection (1): acme-v02.api.letsencrypt.org
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for www.afrotechtrends.com
http-01 challenge for afrotechtrends.com
nginx: [warn] conflicting server name “afrotechtrends.com” on 0.0.0.0:80, ignored
nginx: [warn] conflicting server name “www.afrotechtrends.com” on 0.0.0.0:80, ignored
Waiting for verification…
Cleaning up challenges
nginx: [warn] conflicting server name “afrotechtrends.com” on 0.0.0.0:80, ignored
nginx: [warn] conflicting server name “www.afrotechtrends.com” on 0.0.0.0:80, ignored
Failed authorization procedure. afrotechtrends.com (http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://afrotechtrends.com/.well-known/acme-challenge/_tNgClX9MEptwIZgeV8gGddwyS9XpS8lLZxbNAhKFV8: "\n<html lang=“en”>\n\n <meta http-equiv=“content-type” content=“text/html; charset=utf-8”>\n Page not "
IMPORTANT NOTES:
- The following errors were reported by the server:Domain: afrotechtrends.com
Type: unauthorized
Detail: Invalid response from
http://afrotechtrends.com/.well-known/acme-challenge/_tNgClX9MEptwIZgeV8gGddwyS9XpS8lLZxbNAhKFV8:
"\n<html lang=“en”>\n\n <meta
http-equiv=“content-type” content=“text/html; charset=utf-8”>\nPage not "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): Digitalocean
The operating system my web server runs on is (include version): Ubuntu 16.04
My hosting provider, if applicable, is: Digital Ocean
I can login to a root shell on my machine (yes or no, or I don’t know): Yes
I got this error when trying to secure my domain www.afrotechtrends.com.
I recently changed the domains IP address to a new one and when I’m trying to secure the domain with the new IP address, I’m getting that error. Is there anyone who knows how I can fix that.?