mirror of
				https://github.com/NginxProxyManager/nginx-proxy-manager.git
				synced 2025-11-04 09:25:15 +00:00 
			
		
		
		
	* Fix wrapping when too many hosts are shown (#207) * Update npm packages, fixes CVE-2019-10757 * Revert some breaking packages * Major overhaul - Docker buildx support in CI - Cypress API Testing in CI - Restructured folder layout (insert clean face meme) - Added Swagger documentation and validate API against that (to be completed) - Use common base image for all supported archs, which includes updated nginx with ipv6 support - Updated certbot and changes required for it - Large amount of Hosts names will wrap in UI - Updated packages for frontend - Version bump 2.1.0 * Updated documentation * Fix JWT expire time going crazy. Now set to 1day * Backend JS formatting rules * Remove v1 importer, I doubt anyone is using v1 anymore * Added backend formatting rules and enforce them in Jenkins builds * Fix CI, doesn't need a tty * Thanks bcrypt. Why can't you just be normal. * Cleanup after syntax check Co-authored-by: Marcelo Castagna <margaale@users.noreply.github.com>
		
			
				
	
	
		
			30 lines
		
	
	
		
			1.4 KiB
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
			
		
		
	
	
			30 lines
		
	
	
		
			1.4 KiB
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
# Rule for legitimate ACME Challenge requests (like /.well-known/acme-challenge/xxxxxxxxx)
 | 
						|
# We use ^~ here, so that we don't check other regexes (for speed-up). We actually MUST cancel
 | 
						|
# other regex checks, because in our other config files have regex rule that denies access to files with dotted names.
 | 
						|
location ^~ /.well-known/acme-challenge/ {
 | 
						|
	# Since this is for letsencrypt authentication of a domain and they do not give IP ranges of their infrastructure
 | 
						|
	# we need to open up access by turning off auth and IP ACL for this location.
 | 
						|
	auth_basic off;
 | 
						|
	allow all;
 | 
						|
 | 
						|
	# Set correct content type. According to this:
 | 
						|
	# https://community.letsencrypt.org/t/using-the-webroot-domain-verification-method/1445/29
 | 
						|
	# Current specification requires "text/plain" or no content header at all.
 | 
						|
	# It seems that "text/plain" is a safe option.
 | 
						|
	default_type "text/plain";
 | 
						|
 | 
						|
	# This directory must be the same as in /etc/letsencrypt/cli.ini
 | 
						|
	# as "webroot-path" parameter. Also don't forget to set "authenticator" parameter
 | 
						|
	# there to "webroot".
 | 
						|
	# Do NOT use alias, use root! Target directory is located here:
 | 
						|
	# /var/www/common/letsencrypt/.well-known/acme-challenge/
 | 
						|
	root /data/letsencrypt-acme-challenge;
 | 
						|
}
 | 
						|
 | 
						|
# Hide /acme-challenge subdirectory and return 404 on all requests.
 | 
						|
# It is somewhat more secure than letting Nginx return 403.
 | 
						|
# Ending slash is important!
 | 
						|
location = /.well-known/acme-challenge/ {
 | 
						|
	return 404;
 | 
						|
}
 |