digitalocean/nginxconfig.io

Cannot get SSL certificate.

Open

#157 opened on Jul 1, 2020

View on GitHub
 (3 comments) (0 reactions) (0 assignees)JavaScript (1,978 forks)batch import
bughacktoberfesthelp wanted

Repository metrics

Stars
 (26,979 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

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

Contributor guide

Research direction
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.
Tech stack
None
Domain
backendsecurity
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
basic nginx knowledgefamiliarity with certbot
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30