1
0
mirror of https://github.com/nginx-proxy/nginx-proxy synced 2024-11-08 07:49:22 +01:00
nginx-proxy/nginx.tmpl

439 lines
19 KiB
Go HTML Template
Raw Normal View History

2016-02-23 13:59:30 +01:00
{{ $CurrentContainer := where $ "ID" .Docker.CurrentContainerID | first }}
2022-01-11 22:38:30 +01:00
{{ $nginx_proxy_version := coalesce $.Env.NGINX_PROXY_VERSION "" }}
{{ $external_http_port := coalesce $.Env.HTTP_PORT "80" }}
{{ $external_https_port := coalesce $.Env.HTTPS_PORT "443" }}
{{ $debug_all := $.Env.DEBUG }}
2021-08-17 21:51:09 +02:00
{{ $sha1_upstream_name := parseBool (coalesce $.Env.SHA1_UPSTREAM_NAME "false") }}
{{ $default_root_response := coalesce $.Env.DEFAULT_ROOT "404" }}
{{ $trust_downstream_proxy := parseBool (coalesce $.Env.TRUST_DOWNSTREAM_PROXY "true") }}
2019-08-29 22:14:14 +02:00
{{ define "ssl_policy" }}
{{ if eq .ssl_policy "Mozilla-Modern" }}
ssl_protocols TLSv1.3;
2022-05-17 06:47:40 +02:00
{{/* nginx currently lacks ability to choose ciphers in TLS 1.3 in configuration, see https://trac.nginx.org/nginx/ticket/1529 */}}
{{/* a possible workaround can be modify /etc/ssl/openssl.cnf to change it globally (see https://trac.nginx.org/nginx/ticket/1529#comment:12 ) */}}
2019-08-29 22:14:14 +02:00
{{/* explicitly set ngnix default value in order to allow single servers to override the global http value */}}
ssl_ciphers HIGH:!aNULL:!MD5;
ssl_prefer_server_ciphers off;
{{ else if eq .ssl_policy "Mozilla-Intermediate" }}
ssl_protocols TLSv1.2 TLSv1.3;
ssl_ciphers 'ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384';
ssl_prefer_server_ciphers off;
{{ else if eq .ssl_policy "Mozilla-Old" }}
ssl_protocols TLSv1 TLSv1.1 TLSv1.2 TLSv1.3;
ssl_ciphers 'ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA:ECDHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES256-SHA256:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:DES-CBC3-SHA';
ssl_prefer_server_ciphers on;
{{ else if eq .ssl_policy "AWS-TLS-1-2-2017-01" }}
ssl_protocols TLSv1.2 TLSv1.3;
ssl_ciphers 'ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:AES128-GCM-SHA256:AES128-SHA256:AES256-GCM-SHA384:AES256-SHA256';
ssl_prefer_server_ciphers on;
{{ else if eq .ssl_policy "AWS-TLS-1-1-2017-01" }}
ssl_protocols TLSv1.1 TLSv1.2 TLSv1.3;
ssl_ciphers 'ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:AES128-GCM-SHA256:AES128-SHA256:AES128-SHA:AES256-GCM-SHA384:AES256-SHA256:AES256-SHA';
ssl_prefer_server_ciphers on;
{{ else if eq .ssl_policy "AWS-2016-08" }}
ssl_protocols TLSv1 TLSv1.1 TLSv1.2 TLSv1.3;
ssl_ciphers 'ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:AES128-GCM-SHA256:AES128-SHA256:AES128-SHA:AES256-GCM-SHA384:AES256-SHA256:AES256-SHA';
ssl_prefer_server_ciphers on;
{{ else if eq .ssl_policy "AWS-2015-05" }}
ssl_protocols TLSv1 TLSv1.1 TLSv1.2 TLSv1.3;
ssl_ciphers 'ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:AES128-GCM-SHA256:AES128-SHA256:AES128-SHA:AES256-GCM-SHA384:AES256-SHA256:AES256-SHA:DES-CBC3-SHA';
ssl_prefer_server_ciphers on;
{{ else if eq .ssl_policy "AWS-2015-03" }}
ssl_protocols TLSv1 TLSv1.1 TLSv1.2 TLSv1.3;
ssl_ciphers 'ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES128-SHA:DHE-RSA-AES128-SHA:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:AES128-GCM-SHA256:AES128-SHA256:AES128-SHA:AES256-GCM-SHA384:AES256-SHA256:AES256-SHA:DHE-DSS-AES128-SHA:DES-CBC3-SHA';
ssl_prefer_server_ciphers on;
{{ else if eq .ssl_policy "AWS-2015-02" }}
ssl_protocols TLSv1 TLSv1.1 TLSv1.2 TLSv1.3;
ssl_ciphers 'ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES128-SHA:DHE-RSA-AES128-SHA:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:AES128-GCM-SHA256:AES128-SHA256:AES128-SHA:AES256-GCM-SHA384:AES256-SHA256:AES256-SHA:DHE-DSS-AES128-SHA';
ssl_prefer_server_ciphers on;
{{ end }}
{{ end }}
{{ define "location" }}
location {{ .Path }} {
{{ if eq .NetworkTag "internal" }}
# Only allow traffic from internal clients
include /etc/nginx/network_internal.conf;
{{ end }}
{{ if eq .Proto "uwsgi" }}
include uwsgi_params;
uwsgi_pass {{ trim .Proto }}://{{ trim .Upstream }};
{{ else if eq .Proto "fastcgi" }}
2022-02-24 15:17:47 +01:00
root {{ trim .VhostRoot }};
include fastcgi_params;
fastcgi_pass {{ trim .Upstream }};
{{ else if eq .Proto "grpc" }}
grpc_pass {{ trim .Proto }}://{{ trim .Upstream }};
{{ else }}
proxy_pass {{ trim .Proto }}://{{ trim .Upstream }}{{ trim .Dest }};
{{ end }}
{{ if (exists (printf "/etc/nginx/htpasswd/%s" .Host)) }}
auth_basic "Restricted {{ .Host }}";
auth_basic_user_file {{ (printf "/etc/nginx/htpasswd/%s" .Host) }};
{{ end }}
{{ if (exists (printf "/etc/nginx/vhost.d/%s_%s_location" .Host (sha1 .Path) )) }}
include {{ printf "/etc/nginx/vhost.d/%s_%s_location" .Host (sha1 .Path) }};
{{ else if (exists (printf "/etc/nginx/vhost.d/%s_location" .Host)) }}
include {{ printf "/etc/nginx/vhost.d/%s_location" .Host}};
{{ else if (exists "/etc/nginx/vhost.d/default_location") }}
include /etc/nginx/vhost.d/default_location;
{{ end }}
}
{{ end }}
2022-02-24 15:17:47 +01:00
{{ define "upstream" }}
{{ $networks := .Networks }}
{{ $debug_all := .Debug }}
upstream {{ .Upstream }} {
{{ $server_found := false }}
2022-02-24 15:17:47 +01:00
{{ range $container := .Containers }}
{{ $debug := parseBool (coalesce $container.Env.DEBUG $debug_all "false") }}
{{/* If only 1 port exposed, use that as a default, else 80 */}}
{{ $defaultPort := (when (eq (len $container.Addresses) 1) (first $container.Addresses) (dict "Port" "80")).Port }}
{{ $port := (coalesce $container.Env.VIRTUAL_PORT $defaultPort) }}
{{ $address := where $container.Addresses "Port" $port | first }}
{{ if $debug }}
# Exposed ports: {{ $container.Addresses }}
# Default virtual port: {{ $defaultPort }}
# VIRTUAL_PORT: {{ $container.Env.VIRTUAL_PORT }}
2022-02-24 15:17:47 +01:00
{{ if not $address }}
# /!\ Virtual port not exposed
2022-02-24 15:17:47 +01:00
{{ end }}
{{ end }}
2022-02-24 15:17:47 +01:00
{{ range $knownNetwork := $networks }}
2022-05-11 14:54:51 +02:00
{{ range $containerNetwork := sortObjectsByKeysAsc $container.Networks "Name" }}
2022-02-24 15:17:47 +01:00
{{ if (and (ne $containerNetwork.Name "ingress") (or (eq $knownNetwork.Name $containerNetwork.Name) (eq $knownNetwork.Name "host"))) }}
## Can be connected with "{{ $containerNetwork.Name }}" network
2022-02-24 15:17:47 +01:00
{{ if $address }}
{{/* If we got the containers from swarm and this container's port is published to host, use host IP:PORT */}}
{{ if and $container.Node.ID $address.HostPort }}
{{ $server_found = true }}
# {{ $container.Node.Name }}/{{ $container.Name }}
server {{ $container.Node.Address.IP }}:{{ $address.HostPort }};
2022-02-24 15:17:47 +01:00
{{/* If there is no swarm node or the port is not published on host, use container's IP:PORT */}}
{{ else if $containerNetwork }}
{{ $server_found = true }}
# {{ $container.Name }}
server {{ $containerNetwork.IP }}:{{ $address.Port }};
2022-02-24 15:17:47 +01:00
{{ end }}
{{ else if $containerNetwork }}
# {{ $container.Name }}
2022-02-24 15:17:47 +01:00
{{ if $containerNetwork.IP }}
{{ $server_found = true }}
server {{ $containerNetwork.IP }}:{{ $port }};
2022-02-24 15:17:47 +01:00
{{ else }}
# /!\ No IP for this network!
2022-02-24 15:17:47 +01:00
{{ end }}
{{ end }}
2022-02-24 15:17:47 +01:00
{{ else }}
# Cannot connect to network '{{ $containerNetwork.Name }}' of this container
{{ end }}
{{ end }}
{{ end }}
2022-02-24 15:17:47 +01:00
{{ end }}
{{/* nginx-proxy/nginx-proxy#1105 */}}
{{ if not $server_found }}
# Fallback entry
server 127.0.0.1 down;
2022-02-24 15:17:47 +01:00
{{ end }}
}
{{ end }}
2022-01-11 22:38:30 +01:00
{{ if ne $nginx_proxy_version "" }}
# nginx-proxy version : {{ $nginx_proxy_version }}
{{ end }}
# If we receive X-Forwarded-Proto, pass it through; otherwise, pass along the
# scheme used to connect to this server
map $http_x_forwarded_proto $proxy_x_forwarded_proto {
default {{ if $trust_downstream_proxy }}$http_x_forwarded_proto{{ else }}$scheme{{ end }};
'' $scheme;
}
map $http_x_forwarded_host $proxy_x_forwarded_host {
default {{ if $trust_downstream_proxy }}$http_x_forwarded_host{{ else }}$http_host{{ end }};
'' $http_host;
}
# If we receive X-Forwarded-Port, pass it through; otherwise, pass along the
2016-09-29 22:06:53 +02:00
# server port the client connected to
map $http_x_forwarded_port $proxy_x_forwarded_port {
default {{ if $trust_downstream_proxy }}$http_x_forwarded_port{{ else }}$server_port{{ end }};
'' $server_port;
}
# If we receive Upgrade, set Connection to "upgrade"; otherwise, preserve
# NGINX's default behavior ("Connection: close").
map $http_upgrade $proxy_connection {
default upgrade;
2015-05-09 23:15:26 +02:00
'' close;
}
# Apply fix for very long server names
server_names_hash_bucket_size 128;
# Default dhparam
{{ if (exists "/etc/nginx/dhparam/dhparam.pem") }}
ssl_dhparam /etc/nginx/dhparam/dhparam.pem;
{{ end }}
# Set appropriate X-Forwarded-Ssl header based on $proxy_x_forwarded_proto
map $proxy_x_forwarded_proto $proxy_x_forwarded_ssl {
default off;
https on;
}
gzip_types text/plain text/css application/javascript application/json application/x-javascript text/xml application/xml application/xml+rss text/javascript;
2014-12-07 02:46:25 +01:00
log_format vhost '$host $remote_addr - $remote_user [$time_local] '
'"$request" $status $body_bytes_sent '
'"$http_referer" "$http_user_agent" '
2021-06-09 21:51:51 +02:00
'"$upstream_addr"';
2014-12-07 02:46:25 +01:00
access_log off;
2019-08-29 22:14:14 +02:00
{{/* Get the SSL_POLICY defined by this container, falling back to "Mozilla-Intermediate" */}}
{{ $ssl_policy := or ($.Env.SSL_POLICY) "Mozilla-Intermediate" }}
{{ template "ssl_policy" (dict "ssl_policy" $ssl_policy) }}
error_log /dev/stderr;
2019-08-29 22:14:14 +02:00
2017-02-06 11:20:54 +01:00
{{ if $.Env.RESOLVERS }}
resolver {{ $.Env.RESOLVERS }};
{{ end }}
{{ if (exists "/etc/nginx/proxy.conf") }}
include /etc/nginx/proxy.conf;
{{ else }}
# HTTP 1.1 support
proxy_http_version 1.1;
proxy_buffering off;
proxy_set_header Host $http_host;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $proxy_connection;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Host $proxy_x_forwarded_host;
proxy_set_header X-Forwarded-Proto $proxy_x_forwarded_proto;
proxy_set_header X-Forwarded-Ssl $proxy_x_forwarded_ssl;
proxy_set_header X-Forwarded-Port $proxy_x_forwarded_port;
proxy_set_header X-Original-URI $request_uri;
2016-07-19 17:03:41 +02:00
# Mitigate httpoxy attack (see README for details)
proxy_set_header Proxy "";
{{ end }}
{{ $access_log := (or (and (not $.Env.DISABLE_ACCESS_LOGS) "access_log /var/log/nginx/access.log vhost;") "") }}
{{ $enable_ipv6 := parseBool (coalesce $.Env.ENABLE_IPV6 "false") }}
server {
server_name _; # This is just an invalid value which will never trigger on a real hostname.
server_tokens off;
listen {{ $external_http_port }};
{{ if $enable_ipv6 }}
listen [::]:{{ $external_http_port }};
{{ end }}
{{ $access_log }}
return 503;
{{ if (and (exists "/etc/nginx/certs/default.crt") (exists "/etc/nginx/certs/default.key")) }}
listen {{ $external_https_port }} ssl http2;
{{ if $enable_ipv6 }}
listen [::]:{{ $external_https_port }} ssl http2;
{{ end }}
2019-08-29 22:14:14 +02:00
ssl_session_cache shared:SSL:50m;
ssl_session_tickets off;
ssl_certificate /etc/nginx/certs/default.crt;
ssl_certificate_key /etc/nginx/certs/default.key;
{{ end }}
}
{{ range $host, $containers := groupByMulti $ "Env.VIRTUAL_HOST" "," }}
{{ $host := trim $host }}
2021-08-17 21:51:09 +02:00
{{ $is_regexp := hasPrefix "~" $host }}
{{ $upstream_name := when (or $is_regexp $sha1_upstream_name) (sha1 $host) $host }}
{{ $paths := groupBy $containers "Env.VIRTUAL_PATH" }}
{{ $nPaths := len $paths }}
{{ if eq $nPaths 0 }}
{{ $paths = dict "/" $containers }}
{{ end }}
{{ range $path, $containers := $paths }}
{{ $upstream := $upstream_name }}
{{ if gt $nPaths 0 }}
{{ $sum := sha1 $path }}
{{ $upstream = printf "%s-%s" $upstream $sum }}
{{ end }}
# {{ $host }}{{ $path }}
2022-02-24 15:17:47 +01:00
{{ template "upstream" (dict "Upstream" $upstream "Containers" $containers "Networks" $CurrentContainer.Networks "Debug" $debug_all) }}
{{ end }}
2014-05-05 18:59:23 +02:00
2015-07-26 11:38:45 +02:00
{{ $default_host := or ($.Env.DEFAULT_HOST) "" }}
{{ $default_server := index (dict $host "" $default_host "default_server") $host }}
2015-07-24 10:39:56 +02:00
{{/* Get the SERVER_TOKENS defined by containers w/ the same vhost, falling back to "" */}}
{{ $server_tokens := trim (or (first (groupByKeys $containers "Env.SERVER_TOKENS")) "") }}
2015-11-20 23:36:12 +01:00
{{/* Get the HTTPS_METHOD defined by containers w/ the same vhost, falling back to "redirect" */}}
{{ $https_method := or (first (groupByKeys $containers "Env.HTTPS_METHOD")) (or $.Env.HTTPS_METHOD "redirect") }}
2015-11-20 23:36:12 +01:00
2019-08-29 22:14:14 +02:00
{{/* Get the SSL_POLICY defined by containers w/ the same vhost, falling back to empty string (use default) */}}
{{ $ssl_policy := or (first (groupByKeys $containers "Env.SSL_POLICY")) "" }}
2017-10-27 10:09:32 +02:00
2017-11-09 04:30:24 +01:00
{{/* Get the HSTS defined by containers w/ the same vhost, falling back to "max-age=31536000" */}}
{{ $hsts := or (first (groupByKeys $containers "Env.HSTS")) (or $.Env.HSTS "max-age=31536000") }}
2017-11-09 04:30:24 +01:00
2017-06-24 08:48:05 +02:00
{{/* Get the VIRTUAL_ROOT By containers w/ use fastcgi root */}}
{{ $vhost_root := or (first (groupByKeys $containers "Env.VIRTUAL_ROOT")) "/var/www/public" }}
Add SSL support This adds SSL support for containers. It supports single host certificates, wildcards and SNI using naming conventions for certificates or optionally specify a cert name (for SNI). The SSL cipher configuration is based on mozilla intermediate profile which should provide compatibility with clients back to Firefox 1, Chrome 1, IE 7, Opera 5, Safari 1, Windows XP IE8, Android 2.3, Java 7. The configuration also enables OCSP stapling, HSTS, and ssl session caches. To enable SSL, nginx-proxy should be started w/ -p 443:443 and -v /path/to/certs:/etc/nginx/certs. Certificates must be named: <virtualhost>.crt and <virtualhost>.key where <virtualhost> matches the a value of VIRTUAL_HOST on a container. For wildcard certificates, the certificate and private key should be named after the wildcard domain with .crt and .key suffixes. For example, *.example.com should be name example.com.crt and example.com.key. For SNI where a certificate may be used for multiple domain names, the container can specify a CERT_NAME env var that corresponds to the base file name of the certificate and key. For example, if you have a cert allowing *.example.com and *.bar.com, it can be name shared.crt and shared.key. A container can use that cert by having CERT_NAME=shared and VIRTUAL_HOST=foo.example.com. The name "shared" is arbitrary and can be whatever makes sense. The behavior for the proxy when port 80 and 443 is defined is as follows: * If a container has a usable cert, port 80 will redirect to 443 for that container to always prefer HTTPS when available. * If the container does not have a usable cert 503 will be returned. In the last case, a self-signed or generic cert can be defined as "default.crt" and "default.key" which will allow a client browser to at least make a SSL connection.
2014-11-26 18:38:51 +01:00
{{/* Get the first cert name defined by containers w/ the same vhost */}}
{{ $certName := (first (groupByKeys $containers "Env.CERT_NAME")) }}
{{/* Get the best matching cert by name for the vhost. */}}
{{ $vhostCert := (closest (dir "/etc/nginx/certs") (printf "%s.crt" $host))}}
2016-06-13 08:10:49 +02:00
{{/* vhostCert is actually a filename so remove any suffixes since they are added later */}}
{{ $vhostCert := trimSuffix ".crt" $vhostCert }}
{{ $vhostCert := trimSuffix ".key" $vhostCert }}
Add SSL support This adds SSL support for containers. It supports single host certificates, wildcards and SNI using naming conventions for certificates or optionally specify a cert name (for SNI). The SSL cipher configuration is based on mozilla intermediate profile which should provide compatibility with clients back to Firefox 1, Chrome 1, IE 7, Opera 5, Safari 1, Windows XP IE8, Android 2.3, Java 7. The configuration also enables OCSP stapling, HSTS, and ssl session caches. To enable SSL, nginx-proxy should be started w/ -p 443:443 and -v /path/to/certs:/etc/nginx/certs. Certificates must be named: <virtualhost>.crt and <virtualhost>.key where <virtualhost> matches the a value of VIRTUAL_HOST on a container. For wildcard certificates, the certificate and private key should be named after the wildcard domain with .crt and .key suffixes. For example, *.example.com should be name example.com.crt and example.com.key. For SNI where a certificate may be used for multiple domain names, the container can specify a CERT_NAME env var that corresponds to the base file name of the certificate and key. For example, if you have a cert allowing *.example.com and *.bar.com, it can be name shared.crt and shared.key. A container can use that cert by having CERT_NAME=shared and VIRTUAL_HOST=foo.example.com. The name "shared" is arbitrary and can be whatever makes sense. The behavior for the proxy when port 80 and 443 is defined is as follows: * If a container has a usable cert, port 80 will redirect to 443 for that container to always prefer HTTPS when available. * If the container does not have a usable cert 503 will be returned. In the last case, a self-signed or generic cert can be defined as "default.crt" and "default.key" which will allow a client browser to at least make a SSL connection.
2014-11-26 18:38:51 +01:00
2016-05-17 01:46:46 +02:00
{{/* Use the cert specified on the container or fallback to the best vhost match */}}
Add SSL support This adds SSL support for containers. It supports single host certificates, wildcards and SNI using naming conventions for certificates or optionally specify a cert name (for SNI). The SSL cipher configuration is based on mozilla intermediate profile which should provide compatibility with clients back to Firefox 1, Chrome 1, IE 7, Opera 5, Safari 1, Windows XP IE8, Android 2.3, Java 7. The configuration also enables OCSP stapling, HSTS, and ssl session caches. To enable SSL, nginx-proxy should be started w/ -p 443:443 and -v /path/to/certs:/etc/nginx/certs. Certificates must be named: <virtualhost>.crt and <virtualhost>.key where <virtualhost> matches the a value of VIRTUAL_HOST on a container. For wildcard certificates, the certificate and private key should be named after the wildcard domain with .crt and .key suffixes. For example, *.example.com should be name example.com.crt and example.com.key. For SNI where a certificate may be used for multiple domain names, the container can specify a CERT_NAME env var that corresponds to the base file name of the certificate and key. For example, if you have a cert allowing *.example.com and *.bar.com, it can be name shared.crt and shared.key. A container can use that cert by having CERT_NAME=shared and VIRTUAL_HOST=foo.example.com. The name "shared" is arbitrary and can be whatever makes sense. The behavior for the proxy when port 80 and 443 is defined is as follows: * If a container has a usable cert, port 80 will redirect to 443 for that container to always prefer HTTPS when available. * If the container does not have a usable cert 503 will be returned. In the last case, a self-signed or generic cert can be defined as "default.crt" and "default.key" which will allow a client browser to at least make a SSL connection.
2014-11-26 18:38:51 +01:00
{{ $cert := (coalesce $certName $vhostCert) }}
{{ $is_https := (and (ne $https_method "nohttps") (ne $cert "") (exists (printf "/etc/nginx/certs/%s.crt" $cert)) (exists (printf "/etc/nginx/certs/%s.key" $cert))) }}
2015-11-20 22:53:50 +01:00
{{ if and $is_https (eq $https_method "redirect") }}
Add SSL support This adds SSL support for containers. It supports single host certificates, wildcards and SNI using naming conventions for certificates or optionally specify a cert name (for SNI). The SSL cipher configuration is based on mozilla intermediate profile which should provide compatibility with clients back to Firefox 1, Chrome 1, IE 7, Opera 5, Safari 1, Windows XP IE8, Android 2.3, Java 7. The configuration also enables OCSP stapling, HSTS, and ssl session caches. To enable SSL, nginx-proxy should be started w/ -p 443:443 and -v /path/to/certs:/etc/nginx/certs. Certificates must be named: <virtualhost>.crt and <virtualhost>.key where <virtualhost> matches the a value of VIRTUAL_HOST on a container. For wildcard certificates, the certificate and private key should be named after the wildcard domain with .crt and .key suffixes. For example, *.example.com should be name example.com.crt and example.com.key. For SNI where a certificate may be used for multiple domain names, the container can specify a CERT_NAME env var that corresponds to the base file name of the certificate and key. For example, if you have a cert allowing *.example.com and *.bar.com, it can be name shared.crt and shared.key. A container can use that cert by having CERT_NAME=shared and VIRTUAL_HOST=foo.example.com. The name "shared" is arbitrary and can be whatever makes sense. The behavior for the proxy when port 80 and 443 is defined is as follows: * If a container has a usable cert, port 80 will redirect to 443 for that container to always prefer HTTPS when available. * If the container does not have a usable cert 503 will be returned. In the last case, a self-signed or generic cert can be defined as "default.crt" and "default.key" which will allow a client browser to at least make a SSL connection.
2014-11-26 18:38:51 +01:00
server {
server_name {{ $host }};
{{ if $server_tokens }}
server_tokens {{ $server_tokens }};
{{ end }}
listen {{ $external_http_port }} {{ $default_server }};
{{ if $enable_ipv6 }}
listen [::]:{{ $external_http_port }} {{ $default_server }};
{{ end }}
{{ $access_log }}
2021-10-22 17:08:32 +02:00
# Do not HTTPS redirect Let'sEncrypt ACME challenge
location ^~ /.well-known/acme-challenge/ {
auth_basic off;
auth_request off;
allow all;
root /usr/share/nginx/html;
try_files $uri =404;
break;
}
2021-10-22 17:08:32 +02:00
location / {
{{ if eq $external_https_port "443" }}
return 301 https://$host$request_uri;
{{ else }}
return 301 https://$host:{{ $external_https_port }}$request_uri;
{{ end }}
}
Add SSL support This adds SSL support for containers. It supports single host certificates, wildcards and SNI using naming conventions for certificates or optionally specify a cert name (for SNI). The SSL cipher configuration is based on mozilla intermediate profile which should provide compatibility with clients back to Firefox 1, Chrome 1, IE 7, Opera 5, Safari 1, Windows XP IE8, Android 2.3, Java 7. The configuration also enables OCSP stapling, HSTS, and ssl session caches. To enable SSL, nginx-proxy should be started w/ -p 443:443 and -v /path/to/certs:/etc/nginx/certs. Certificates must be named: <virtualhost>.crt and <virtualhost>.key where <virtualhost> matches the a value of VIRTUAL_HOST on a container. For wildcard certificates, the certificate and private key should be named after the wildcard domain with .crt and .key suffixes. For example, *.example.com should be name example.com.crt and example.com.key. For SNI where a certificate may be used for multiple domain names, the container can specify a CERT_NAME env var that corresponds to the base file name of the certificate and key. For example, if you have a cert allowing *.example.com and *.bar.com, it can be name shared.crt and shared.key. A container can use that cert by having CERT_NAME=shared and VIRTUAL_HOST=foo.example.com. The name "shared" is arbitrary and can be whatever makes sense. The behavior for the proxy when port 80 and 443 is defined is as follows: * If a container has a usable cert, port 80 will redirect to 443 for that container to always prefer HTTPS when available. * If the container does not have a usable cert 503 will be returned. In the last case, a self-signed or generic cert can be defined as "default.crt" and "default.key" which will allow a client browser to at least make a SSL connection.
2014-11-26 18:38:51 +01:00
}
2015-11-20 22:53:50 +01:00
{{ end }}
Add SSL support This adds SSL support for containers. It supports single host certificates, wildcards and SNI using naming conventions for certificates or optionally specify a cert name (for SNI). The SSL cipher configuration is based on mozilla intermediate profile which should provide compatibility with clients back to Firefox 1, Chrome 1, IE 7, Opera 5, Safari 1, Windows XP IE8, Android 2.3, Java 7. The configuration also enables OCSP stapling, HSTS, and ssl session caches. To enable SSL, nginx-proxy should be started w/ -p 443:443 and -v /path/to/certs:/etc/nginx/certs. Certificates must be named: <virtualhost>.crt and <virtualhost>.key where <virtualhost> matches the a value of VIRTUAL_HOST on a container. For wildcard certificates, the certificate and private key should be named after the wildcard domain with .crt and .key suffixes. For example, *.example.com should be name example.com.crt and example.com.key. For SNI where a certificate may be used for multiple domain names, the container can specify a CERT_NAME env var that corresponds to the base file name of the certificate and key. For example, if you have a cert allowing *.example.com and *.bar.com, it can be name shared.crt and shared.key. A container can use that cert by having CERT_NAME=shared and VIRTUAL_HOST=foo.example.com. The name "shared" is arbitrary and can be whatever makes sense. The behavior for the proxy when port 80 and 443 is defined is as follows: * If a container has a usable cert, port 80 will redirect to 443 for that container to always prefer HTTPS when available. * If the container does not have a usable cert 503 will be returned. In the last case, a self-signed or generic cert can be defined as "default.crt" and "default.key" which will allow a client browser to at least make a SSL connection.
2014-11-26 18:38:51 +01:00
2014-05-05 18:59:23 +02:00
server {
server_name {{ $host }};
{{ if $server_tokens }}
server_tokens {{ $server_tokens }};
{{ end }}
{{ $access_log }}
{{- if or (not $is_https) (eq $https_method "noredirect") }}
listen {{ $external_http_port }} {{ $default_server }};
{{ if $enable_ipv6 }}
listen [::]:{{ $external_http_port }} {{ $default_server }};
{{ end }}
{{- end }}
{{- if $is_https }}
listen {{ $external_https_port }} ssl http2 {{ $default_server }};
{{ if $enable_ipv6 }}
listen [::]:{{ $external_https_port }} ssl http2 {{ $default_server }};
{{ end }}
Add SSL support This adds SSL support for containers. It supports single host certificates, wildcards and SNI using naming conventions for certificates or optionally specify a cert name (for SNI). The SSL cipher configuration is based on mozilla intermediate profile which should provide compatibility with clients back to Firefox 1, Chrome 1, IE 7, Opera 5, Safari 1, Windows XP IE8, Android 2.3, Java 7. The configuration also enables OCSP stapling, HSTS, and ssl session caches. To enable SSL, nginx-proxy should be started w/ -p 443:443 and -v /path/to/certs:/etc/nginx/certs. Certificates must be named: <virtualhost>.crt and <virtualhost>.key where <virtualhost> matches the a value of VIRTUAL_HOST on a container. For wildcard certificates, the certificate and private key should be named after the wildcard domain with .crt and .key suffixes. For example, *.example.com should be name example.com.crt and example.com.key. For SNI where a certificate may be used for multiple domain names, the container can specify a CERT_NAME env var that corresponds to the base file name of the certificate and key. For example, if you have a cert allowing *.example.com and *.bar.com, it can be name shared.crt and shared.key. A container can use that cert by having CERT_NAME=shared and VIRTUAL_HOST=foo.example.com. The name "shared" is arbitrary and can be whatever makes sense. The behavior for the proxy when port 80 and 443 is defined is as follows: * If a container has a usable cert, port 80 will redirect to 443 for that container to always prefer HTTPS when available. * If the container does not have a usable cert 503 will be returned. In the last case, a self-signed or generic cert can be defined as "default.crt" and "default.key" which will allow a client browser to at least make a SSL connection.
2014-11-26 18:38:51 +01:00
2019-08-29 22:14:14 +02:00
{{ template "ssl_policy" (dict "ssl_policy" $ssl_policy) }}
Add SSL support This adds SSL support for containers. It supports single host certificates, wildcards and SNI using naming conventions for certificates or optionally specify a cert name (for SNI). The SSL cipher configuration is based on mozilla intermediate profile which should provide compatibility with clients back to Firefox 1, Chrome 1, IE 7, Opera 5, Safari 1, Windows XP IE8, Android 2.3, Java 7. The configuration also enables OCSP stapling, HSTS, and ssl session caches. To enable SSL, nginx-proxy should be started w/ -p 443:443 and -v /path/to/certs:/etc/nginx/certs. Certificates must be named: <virtualhost>.crt and <virtualhost>.key where <virtualhost> matches the a value of VIRTUAL_HOST on a container. For wildcard certificates, the certificate and private key should be named after the wildcard domain with .crt and .key suffixes. For example, *.example.com should be name example.com.crt and example.com.key. For SNI where a certificate may be used for multiple domain names, the container can specify a CERT_NAME env var that corresponds to the base file name of the certificate and key. For example, if you have a cert allowing *.example.com and *.bar.com, it can be name shared.crt and shared.key. A container can use that cert by having CERT_NAME=shared and VIRTUAL_HOST=foo.example.com. The name "shared" is arbitrary and can be whatever makes sense. The behavior for the proxy when port 80 and 443 is defined is as follows: * If a container has a usable cert, port 80 will redirect to 443 for that container to always prefer HTTPS when available. * If the container does not have a usable cert 503 will be returned. In the last case, a self-signed or generic cert can be defined as "default.crt" and "default.key" which will allow a client browser to at least make a SSL connection.
2014-11-26 18:38:51 +01:00
ssl_session_timeout 5m;
ssl_session_cache shared:SSL:50m;
ssl_session_tickets off;
Add SSL support This adds SSL support for containers. It supports single host certificates, wildcards and SNI using naming conventions for certificates or optionally specify a cert name (for SNI). The SSL cipher configuration is based on mozilla intermediate profile which should provide compatibility with clients back to Firefox 1, Chrome 1, IE 7, Opera 5, Safari 1, Windows XP IE8, Android 2.3, Java 7. The configuration also enables OCSP stapling, HSTS, and ssl session caches. To enable SSL, nginx-proxy should be started w/ -p 443:443 and -v /path/to/certs:/etc/nginx/certs. Certificates must be named: <virtualhost>.crt and <virtualhost>.key where <virtualhost> matches the a value of VIRTUAL_HOST on a container. For wildcard certificates, the certificate and private key should be named after the wildcard domain with .crt and .key suffixes. For example, *.example.com should be name example.com.crt and example.com.key. For SNI where a certificate may be used for multiple domain names, the container can specify a CERT_NAME env var that corresponds to the base file name of the certificate and key. For example, if you have a cert allowing *.example.com and *.bar.com, it can be name shared.crt and shared.key. A container can use that cert by having CERT_NAME=shared and VIRTUAL_HOST=foo.example.com. The name "shared" is arbitrary and can be whatever makes sense. The behavior for the proxy when port 80 and 443 is defined is as follows: * If a container has a usable cert, port 80 will redirect to 443 for that container to always prefer HTTPS when available. * If the container does not have a usable cert 503 will be returned. In the last case, a self-signed or generic cert can be defined as "default.crt" and "default.key" which will allow a client browser to at least make a SSL connection.
2014-11-26 18:38:51 +01:00
ssl_certificate /etc/nginx/certs/{{ (printf "%s.crt" $cert) }};
ssl_certificate_key /etc/nginx/certs/{{ (printf "%s.key" $cert) }};
{{ if (exists (printf "/etc/nginx/certs/%s.dhparam.pem" $cert)) }}
2015-05-21 17:43:09 +02:00
ssl_dhparam {{ printf "/etc/nginx/certs/%s.dhparam.pem" $cert }};
{{ end }}
{{ if (exists (printf "/etc/nginx/certs/%s.chain.pem" $cert)) }}
ssl_stapling on;
ssl_stapling_verify on;
ssl_trusted_certificate {{ printf "/etc/nginx/certs/%s.chain.pem" $cert }};
{{ end }}
{{ if (not (or (eq $https_method "noredirect") (eq $hsts "off"))) }}
set $sts_header "";
if ($https) {
set $sts_header "{{ trim $hsts }}";
}
add_header Strict-Transport-Security $sts_header always;
{{ end }}
{{- end }}
Add SSL support This adds SSL support for containers. It supports single host certificates, wildcards and SNI using naming conventions for certificates or optionally specify a cert name (for SNI). The SSL cipher configuration is based on mozilla intermediate profile which should provide compatibility with clients back to Firefox 1, Chrome 1, IE 7, Opera 5, Safari 1, Windows XP IE8, Android 2.3, Java 7. The configuration also enables OCSP stapling, HSTS, and ssl session caches. To enable SSL, nginx-proxy should be started w/ -p 443:443 and -v /path/to/certs:/etc/nginx/certs. Certificates must be named: <virtualhost>.crt and <virtualhost>.key where <virtualhost> matches the a value of VIRTUAL_HOST on a container. For wildcard certificates, the certificate and private key should be named after the wildcard domain with .crt and .key suffixes. For example, *.example.com should be name example.com.crt and example.com.key. For SNI where a certificate may be used for multiple domain names, the container can specify a CERT_NAME env var that corresponds to the base file name of the certificate and key. For example, if you have a cert allowing *.example.com and *.bar.com, it can be name shared.crt and shared.key. A container can use that cert by having CERT_NAME=shared and VIRTUAL_HOST=foo.example.com. The name "shared" is arbitrary and can be whatever makes sense. The behavior for the proxy when port 80 and 443 is defined is as follows: * If a container has a usable cert, port 80 will redirect to 443 for that container to always prefer HTTPS when available. * If the container does not have a usable cert 503 will be returned. In the last case, a self-signed or generic cert can be defined as "default.crt" and "default.key" which will allow a client browser to at least make a SSL connection.
2014-11-26 18:38:51 +01:00
{{ 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") }}
2015-08-30 02:38:43 +02:00
include /etc/nginx/vhost.d/default;
{{ end }}
{{ range $path, $containers := $paths }}
{{/* Get the VIRTUAL_PROTO defined by containers w/ the same vhost-vpath, falling back to "http" */}}
{{ $proto := trim (or (first (groupByKeys $containers "Env.VIRTUAL_PROTO")) "http") }}
{{/* Get the NETWORK_ACCESS defined by containers w/ the same vhost, falling back to "external" */}}
{{ $network_tag := or (first (groupByKeys $containers "Env.NETWORK_ACCESS")) "external" }}
{{ $upstream := $upstream_name }}
{{ $dest := "" }}
{{ if gt $nPaths 0 }}
{{ $sum := sha1 $path }}
{{ $upstream = printf "%s-%s" $upstream $sum }}
{{ $dest = (or (first (groupByKeys $containers "Env.VIRTUAL_DEST")) "") }}
{{ end }}
2022-02-24 15:17:47 +01:00
{{ template "location" (dict "Path" $path "Proto" $proto "Upstream" $upstream "Host" $host "VhostRoot" $vhost_root "Dest" $dest "NetworkTag" $network_tag) }}
{{ end }}
{{ if (not (contains $paths "/")) }}
location / {
return {{ $default_root_response }};
}
{{ end }}
Add SSL support This adds SSL support for containers. It supports single host certificates, wildcards and SNI using naming conventions for certificates or optionally specify a cert name (for SNI). The SSL cipher configuration is based on mozilla intermediate profile which should provide compatibility with clients back to Firefox 1, Chrome 1, IE 7, Opera 5, Safari 1, Windows XP IE8, Android 2.3, Java 7. The configuration also enables OCSP stapling, HSTS, and ssl session caches. To enable SSL, nginx-proxy should be started w/ -p 443:443 and -v /path/to/certs:/etc/nginx/certs. Certificates must be named: <virtualhost>.crt and <virtualhost>.key where <virtualhost> matches the a value of VIRTUAL_HOST on a container. For wildcard certificates, the certificate and private key should be named after the wildcard domain with .crt and .key suffixes. For example, *.example.com should be name example.com.crt and example.com.key. For SNI where a certificate may be used for multiple domain names, the container can specify a CERT_NAME env var that corresponds to the base file name of the certificate and key. For example, if you have a cert allowing *.example.com and *.bar.com, it can be name shared.crt and shared.key. A container can use that cert by having CERT_NAME=shared and VIRTUAL_HOST=foo.example.com. The name "shared" is arbitrary and can be whatever makes sense. The behavior for the proxy when port 80 and 443 is defined is as follows: * If a container has a usable cert, port 80 will redirect to 443 for that container to always prefer HTTPS when available. * If the container does not have a usable cert 503 will be returned. In the last case, a self-signed or generic cert can be defined as "default.crt" and "default.key" which will allow a client browser to at least make a SSL connection.
2014-11-26 18:38:51 +01:00
}
2015-11-20 23:36:12 +01:00
{{ if (and (not $is_https) (exists "/etc/nginx/certs/default.crt") (exists "/etc/nginx/certs/default.key")) }}
Add SSL support This adds SSL support for containers. It supports single host certificates, wildcards and SNI using naming conventions for certificates or optionally specify a cert name (for SNI). The SSL cipher configuration is based on mozilla intermediate profile which should provide compatibility with clients back to Firefox 1, Chrome 1, IE 7, Opera 5, Safari 1, Windows XP IE8, Android 2.3, Java 7. The configuration also enables OCSP stapling, HSTS, and ssl session caches. To enable SSL, nginx-proxy should be started w/ -p 443:443 and -v /path/to/certs:/etc/nginx/certs. Certificates must be named: <virtualhost>.crt and <virtualhost>.key where <virtualhost> matches the a value of VIRTUAL_HOST on a container. For wildcard certificates, the certificate and private key should be named after the wildcard domain with .crt and .key suffixes. For example, *.example.com should be name example.com.crt and example.com.key. For SNI where a certificate may be used for multiple domain names, the container can specify a CERT_NAME env var that corresponds to the base file name of the certificate and key. For example, if you have a cert allowing *.example.com and *.bar.com, it can be name shared.crt and shared.key. A container can use that cert by having CERT_NAME=shared and VIRTUAL_HOST=foo.example.com. The name "shared" is arbitrary and can be whatever makes sense. The behavior for the proxy when port 80 and 443 is defined is as follows: * If a container has a usable cert, port 80 will redirect to 443 for that container to always prefer HTTPS when available. * If the container does not have a usable cert 503 will be returned. In the last case, a self-signed or generic cert can be defined as "default.crt" and "default.key" which will allow a client browser to at least make a SSL connection.
2014-11-26 18:38:51 +01:00
server {
server_name {{ $host }};
{{ if $server_tokens }}
server_tokens {{ $server_tokens }};
{{ end }}
listen {{ $external_https_port }} ssl http2 {{ $default_server }};
{{ if $enable_ipv6 }}
listen [::]:{{ $external_https_port }} ssl http2 {{ $default_server }};
{{ end }}
{{ $access_log }}
return 500;
Add SSL support This adds SSL support for containers. It supports single host certificates, wildcards and SNI using naming conventions for certificates or optionally specify a cert name (for SNI). The SSL cipher configuration is based on mozilla intermediate profile which should provide compatibility with clients back to Firefox 1, Chrome 1, IE 7, Opera 5, Safari 1, Windows XP IE8, Android 2.3, Java 7. The configuration also enables OCSP stapling, HSTS, and ssl session caches. To enable SSL, nginx-proxy should be started w/ -p 443:443 and -v /path/to/certs:/etc/nginx/certs. Certificates must be named: <virtualhost>.crt and <virtualhost>.key where <virtualhost> matches the a value of VIRTUAL_HOST on a container. For wildcard certificates, the certificate and private key should be named after the wildcard domain with .crt and .key suffixes. For example, *.example.com should be name example.com.crt and example.com.key. For SNI where a certificate may be used for multiple domain names, the container can specify a CERT_NAME env var that corresponds to the base file name of the certificate and key. For example, if you have a cert allowing *.example.com and *.bar.com, it can be name shared.crt and shared.key. A container can use that cert by having CERT_NAME=shared and VIRTUAL_HOST=foo.example.com. The name "shared" is arbitrary and can be whatever makes sense. The behavior for the proxy when port 80 and 443 is defined is as follows: * If a container has a usable cert, port 80 will redirect to 443 for that container to always prefer HTTPS when available. * If the container does not have a usable cert 503 will be returned. In the last case, a self-signed or generic cert can be defined as "default.crt" and "default.key" which will allow a client browser to at least make a SSL connection.
2014-11-26 18:38:51 +01:00
ssl_certificate /etc/nginx/certs/default.crt;
ssl_certificate_key /etc/nginx/certs/default.key;
}
{{ end }}
Add SSL support This adds SSL support for containers. It supports single host certificates, wildcards and SNI using naming conventions for certificates or optionally specify a cert name (for SNI). The SSL cipher configuration is based on mozilla intermediate profile which should provide compatibility with clients back to Firefox 1, Chrome 1, IE 7, Opera 5, Safari 1, Windows XP IE8, Android 2.3, Java 7. The configuration also enables OCSP stapling, HSTS, and ssl session caches. To enable SSL, nginx-proxy should be started w/ -p 443:443 and -v /path/to/certs:/etc/nginx/certs. Certificates must be named: <virtualhost>.crt and <virtualhost>.key where <virtualhost> matches the a value of VIRTUAL_HOST on a container. For wildcard certificates, the certificate and private key should be named after the wildcard domain with .crt and .key suffixes. For example, *.example.com should be name example.com.crt and example.com.key. For SNI where a certificate may be used for multiple domain names, the container can specify a CERT_NAME env var that corresponds to the base file name of the certificate and key. For example, if you have a cert allowing *.example.com and *.bar.com, it can be name shared.crt and shared.key. A container can use that cert by having CERT_NAME=shared and VIRTUAL_HOST=foo.example.com. The name "shared" is arbitrary and can be whatever makes sense. The behavior for the proxy when port 80 and 443 is defined is as follows: * If a container has a usable cert, port 80 will redirect to 443 for that container to always prefer HTTPS when available. * If the container does not have a usable cert 503 will be returned. In the last case, a self-signed or generic cert can be defined as "default.crt" and "default.key" which will allow a client browser to at least make a SSL connection.
2014-11-26 18:38:51 +01:00
{{ end }}