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

location /.well-known/acme-challenge/ {
    auth_basic off;
    allow all;
    root /usr/share/nginx/html;
    try_files $uri =404;
    break;
}
Revert "Set /.well-known/acme-challenge nginx location path as prefix string (#192)" Don't need to use a regexp because the vhost.d/default configuration must be include specificaly in each server configurations by the nginx.tmpl template file. Something like: {{ if (exists (printf "/etc/nginx/vhost.d/%s" $host)) }} include {{ printf "/etc/nginx/vhost.d/%s" $host }}; {{ else if (exists "/etc/nginx/vhost.d/default") }} include /etc/nginx/vhost.d/default; {{ end }} 2017-07-02 11:02:07 +02:00			`location /.well-known/acme-challenge/ {`
disable auth for the acme-challenge location 2017-07-08 16:59:20 +02:00			`auth_basic 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			`}`