You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I followed the documentation to deploy my nginx proxy in a Rasberry Pi 4 (4GB) but I think the documentation is outdated. For example, here https://github.com/nginx-proxy/acme-companion/blob/main/docs/Docker-Compose.md the label is make reference to the old repository "com.github.jrcs.letsencrypt_nginx_proxy_companion.docker_gen" I thouth. In the documentation without docker-compose there is the same issue https://github.com/nginx-proxy/acme-companion/blob/main/docs/Advanced-usage.md but in this I saw I can use the env NGINX_DOCKER_GEN_CONTAINER for the same propose, so I try it and my docker-gen works but now the nginx-proxy container falls with exit code 1 when try to notify.
# 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 $http_x_forwarded_proto;''$scheme;
}
# If we receive X-Forwarded-Port, pass it through; otherwise, pass along the# server port the client connected to
map $http_x_forwarded_port$proxy_x_forwarded_port {
default $http_x_forwarded_port;''$server_port;
}
# If we receive Upgrade, set Connection to "upgrade"; otherwise, delete any# Connection header that may have been passed to this server
map $http_upgrade$proxy_connection {
default upgrade;'' close;
}
# Apply fix for very long server names
server_names_hash_bucket_size 128;# Default dhparam# 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;
log_format vhost '$host $remote_addr - $remote_user [$time_local] ''"$request" $status $body_bytes_sent ''"$http_referer" "$http_user_agent" ''"$upstream_addr"';
access_log off;
ssl_protocols TLSv1.2 TLSv1.3;
ssl_ciphers 'xxxx';
ssl_prefer_server_ciphers off;
error_log /dev/stderr;# 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-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;# Mitigate httpoxy attack (see README for details)
proxy_set_header Proxy "";
server {
server_name _;# This is just an invalid value which will never trigger on a real hostname.
server_tokens off;
listen 80;
access_log /var/log/nginx/access.log vhost;return 503;
}
server {
server_name _;# This is just an invalid value which will never trigger on a real hostname.
server_tokens off;
listen 443 ssl http2;
access_log /var/log/nginx/access.log vhost;return 503;
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;
}
# xxx.duckdns.org
upstream xxx.duckdns.org {
# Cannot connect to network 'webserver_default' of this container# Fallback entry
server 127.0.0.1 down;
}
server {
server_name xxx.duckdns.org;
listen 80 ;
access_log /var/log/nginx/access.log vhost;# 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;
}
location / {
return 301 https://$host$request_uri;
}
}
server {
server_name xxx.duckdns.org;
listen 443 ssl http2 ;
access_log /var/log/nginx/access.log vhost;
ssl_session_timeout 5m;
ssl_session_cache shared:SSL:50m;
ssl_session_tickets off;
ssl_certificate /etc/nginx/certs/xxx.duckdns.org.crt;
ssl_certificate_key /etc/nginx/certs/xxx.duckdns.org.key;
ssl_dhparam /etc/nginx/certs/xxx.duckdns.org.dhparam.pem;
ssl_stapling on;
ssl_stapling_verify on;
ssl_trusted_certificate /etc/nginx/certs/xxx.duckdns.org.chain.pem;
add_header Strict-Transport-Security "max-age=31536000" always;
location / {
proxy_pass http://xxx.duckdns.org;
}
}
Bug description
I followed the documentation to deploy my nginx proxy in a Rasberry Pi 4 (4GB) but I think the documentation is outdated. For example, here https://github.com/nginx-proxy/acme-companion/blob/main/docs/Docker-Compose.md the label is make reference to the old repository "com.github.jrcs.letsencrypt_nginx_proxy_companion.docker_gen" I thouth. In the documentation without docker-compose there is the same issue https://github.com/nginx-proxy/acme-companion/blob/main/docs/Advanced-usage.md but in this I saw I can use the env NGINX_DOCKER_GEN_CONTAINER for the same propose, so I try it and my docker-gen works but now the nginx-proxy container falls with exit code 1 when try to notify.
acme-companion image version
nginx-proxy's Docker configuration
rendered nginx configuration
Containers logs
_nginx-proxy-acme_logs.txt
_nginx-proxy-gen_logs.txt
_nginx-proxy_logs.txt
Docker host
OS
Raspberry Pi OS Lite 64bits
Docker version:
The text was updated successfully, but these errors were encountered: