digitalocean/nginxconfig.io

Cannot get SSL certificate.

Open

#157 建立於 2020年7月1日

在 GitHub 查看
 (3 留言) (0 反應) (0 負責人)JavaScript (26,979 star) (1,978 fork)batch import
bughacktoberfesthelp wanted

描述

I've followed the setup instructions step by step. However, when I execute:

sudo certbot certonly --webroot -d domain.com --email my@mail.com -w /var/www/_letsencrypt -n --agree-tos --force-renewal

The following error message appears:

Failed authorization procedure. domain.com (http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://domain.com/.well-known/acme-challenge/V8Gz5gpzI0B6C7iyQ5N6W4MhmYD6Cn6Mh5Pb755s03Y [MY IP]: "<html>\r\n<head><title>404 Not Found</title></head>\r\n<body bgcolor=\"white\">\r\n<center><h1>404 Not Found</h1></center>\r\n<hr><center>"

IMPORTANT NOTES:
 - The following errors were reported by the server:

   Domain: domain.com
   Type:   unauthorized
   Detail: Invalid response from
   http://domain.com/.well-known/acme-challenge/V8Gz5gpzI0B6C7iyQ5N6W4MhmYD6Cn6Mh5Pb755s03Y
   [MY IP]: "<html>\r\n<head><title>404 Not
   Found</title></head>\r\n<body bgcolor=\"white\">\r\n<center><h1>404
   Not Found</h1></center>\r\n<hr><center>"

   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.

I'm sure the web server is reachable from the internet. I'm trying to configure the webserver on a Raspberry Pi 4B with Nginx 1.14.2 and Certbot 0.31.0-1

貢獻者指南

技術棧
無
領域
backendsecurity
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
needs investigation
前置要求
basic nginx knowledgefamiliarity with certbot
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
30
研究方向
Investigate the nginx configuration generated by nginxconfig.io to ensure it includes a location block for /.well known/acme challenge that serves files from the correct webroot path. Check if the user's webroot path matches the one used in the certbot command. Review the repository's documentation for any known issues or updates regarding SSL certificate setup. Also consider that the error might be due to DNS propagation or firewall rules; suggest verifying domain resolution and server accessibility.