docker-letsencrypt-nginx-pr.../app/nginx_location.conf

location ^~ /.well-known/acme-challenge/ {
    auth_basic off;
    auth_request off;
    allow all;
    root /usr/share/nginx/html;
    try_files $uri =404;
    break;
}
Added ^~ to location directive 2018-02-20 20:55:48 +01:00			`location ^~ /.well-known/acme-challenge/ {`
disable auth for the acme-challenge location 2017-07-08 16:59:20 +02:00			`auth_basic off;`
Set auth_request off for acme challenge location 2019-08-19 03:19:36 +02:00			`auth_request off;`
enable public access to validation endpoints despite existing IP whitelisting or basic auth settings 2016-05-23 21:04:38 +02:00			`allow all;`
Create location configurations automatically 2016-01-01 14:32:40 +01:00			`root /usr/share/nginx/html;`
			`try_files $uri =404;`
break in location in case the upstream is protected Add a break into the letsencrypt block so that no more rules are executed otherwise if you have a block like... ## Start of configuration add by letsencrypt container location /.well-known/acme-challenge/ { auth_basic off; root /usr/share/nginx/html; try_files $uri =404; } ## End of configuration add by letsencrypt container if (!-f /code/home/cookies/$cookie_AUTH_COOKIE) { rewrite ^ https://auth.example.org break; } Then lets encrypt never manages to verify the domain as the request gets re-written to the authentication URL. 2016-05-06 19:47:50 +02:00			`break;`
Create location configurations automatically 2016-01-01 14:32:40 +01:00			`}`