编辑：
Nginxconfiguration：
server { server_name selftestcheck.com www.selftestcheck.com; access_log /var/log/nginx/selftestcheck.com.access.log rt_cache_redis; error_log /var/log/nginx/selftestcheck.com.error.log; root /var/www/selftestcheck.com/htdocs; index index.php index.html index.htm; include common/redis-php7.conf; include common/wpcommon-php7.conf; include common/locations-php7.conf; include /var/www/selftestcheck.com/conf/nginx/*.conf; location '/.well-known/acme-challenge' { root /var/www/domain/htdocs; } } 这个问题也许之前已经被问过了，但似乎没有答案，所以我想试着回答一下，因为很多人似乎都忍受了这个问题。
这就是问题：
我运行“sudo ee站点创build域 – wpfc –letsencrypt”或“sudo ee站点更新域–letsencrypt”
我得到这个错误：
“要解决这些错误，请确保您的域名input正确，并且该域名的DNS Alogging包含正确的IP地址。”
几个月前，我可以做sudo ee网站创build域 – wpfc –letsencrypt，一切都将工作得很好。 现在突然间，我用ee创build的每个站点都有这个https问题。 为什么？！
无论如何，基本上我认为每个人都需要弄清楚发生了什么事情：
2017-06-27 16:01:33,531 (DEBUG) ee : logging initialized for 'ee' using LoggingLogHandler 2017-06-27 16:01:33,826 (DEBUG) ee : ['/usr/local/bin/ee', 'site', 'update', 'domain', '--letsencrypt'] 2017-06-27 16:01:33,827 (DEBUG) ee : collecting arguments/commands for <ee.cli.controllers.base.EEBaseController object at 0x7ff98cd5d908> 2017-06-27 16:01:33,829 (DEBUG) ee : collecting arguments/commands for <ee.cli.plugins.site.EESiteController object at 0x7ff98cd5dac8> 2017-06-27 16:01:33,830 (DEBUG) ee : collecting arguments/commands for <ee.cli.plugins.site.EESiteUpdateController object at 0x7ff98cd6f3c8> 2017-06-27 16:01:33,833 (INFO) ee : Initializing EasyEngine Database 2017-06-27 16:01:33,843 (INFO) ee : Letsencrypt is currently in beta phase. Do you wish to enable SSl now for domain? 2017-06-27 16:01:36,195 (DEBUG) ee : Changing directory to /opt/letsencrypt 2017-06-27 16:01:36,195 (DEBUG) ee : Running command: git pull 2017-06-27 16:01:36,548 (DEBUG) ee : Command Output: Already up-to-date. , Command Error: 2017-06-27 16:01:36,549 (WARNING) ee : Please Wait while we fetch SSL Certificate for your site. It may take time depending upon network. 2017-06-27 16:01:36,549 (DEBUG) ee : Running command: ./letsencrypt-auto certonly --webroot -w /var/www/domain/htdocs/ -d domain -d domain --email email --text --agree-tos 2017-06-27 16:01:44,332 (DEBUG) ee : Command Output: IMPORTANT NOTES: - The following errors were reported by the server: Domain: domain Type: unauthorized Detail: Invalid response from //domain/.well-known/acme-challenge/uLxoAUahNQ-eqXBUfYuYP2xVEQwohM1o4zm53RgqtHI: "<html> <head><title>404 Not Found</title></head> <body bgcolor="white"> <center><h1>404 Not Found</h1></center> <center>" Domain: non-www-domain Type: unauthorized Detail: Invalid response from //non-www-domain/.well-known/acme-challenge/vFzrgVwx62VPdsAeN4M1DGXJDwLkPaIC3nuCMfXvw0Q: "<html> <head><title>404 Not Found</title></head> <body bgcolor="white"> <center><h1>404 Not Found</h1></center> <center>" To fix these errors, please make sure that your domain name was entered correctly and the DNS A record(s) for that domain contain(s) the right IP address. , Command Error: Saving debug log to /var/log/letsencrypt/letsencrypt.log Obtaining a new certificate Performing the following challenges: http-01 challenge for domain http-01 challenge for non-www-domain Using the webroot path /var/www/domain/htdocs for all unmatched domains. Waiting for verification... Cleaning up challenges Failed authorization procedure. domain (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from //domain/.well-known/acme-challenge/uLxoAUahNQ-eqXBUfYuYP2xVEQwohM1o4zm53RgqtHI: "<html> <head><title>404 Not Found</title></head> <body bgcolor="white"> <center><h1>404 Not Found</h1></center> <center>", domain (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from //domain/.well-known/acme-challenge/vFzrgVwx62VPdsAeN4M1DGXJDwLkPaIC3nuCMfXvw0Q: "<html> <head><title>404 Not Found</title></head> <body bgcolor="white"> <center><h1>404 Not Found</h1></center> <center>" 2017-06-27 16:01:44,333 (ERROR) ee : Unable to setup, Let's Encrypt 2017-06-27 16:01:44,333 (ERROR) ee : Please make sure that your site is pointed to same server on which you are running Let's Encrypt Client to allow it to verify the site automatically.
我用pingdom来检查我的DNS，它指向Linode上的所有正确的域名服务器，我可以看到它，反向DNS工作。
Status: active Logging: on (low) Default: deny (incoming), allow (outgoing), disabled (routed) New profiles: skip To Action From -- ------ ---- 22 DENY IN Anywhere 80 ALLOW IN Anywhere 443 ALLOW IN Anywhere xxxxxxx ALLOW IN Anywhere xxx ALLOW IN Anywhere 22 (v6) DENY IN Anywhere (v6) 80 (v6) ALLOW IN Anywhere (v6) 443 (v6) ALLOW IN Anywhere (v6) xxxxxxx (v6) ALLOW IN Anywhere (v6) xxx (v6) ALLOW IN Anywhere (v6)
这里是我放在DIR中的testing文件，以确保它是可访问的：
http://selftestcheck.com/.well-known/acme-challenge/test.txt
应该看到“嗨你好”有人请帮忙！
你的configuration很可能是configuration错误。
location ~ /.well-known/ { allow all; }
确保你在你的configuration中有这个。 也尝试，如果你通过sudo nginx -t正确configuration它