NginxProxyManager / nginx-proxy-manager

Docker container for managing Nginx proxy hosts with a simple, powerful interface
https://nginxproxymanager.com
MIT License
22.84k stars 2.65k forks source link

Faulty proxy_host config file causes boot loop with "double read ssl 443" #3345

Open Haui1112 opened 11 months ago

Haui1112 commented 11 months ago

Checklist

Describe the bug An error in one proxy host file in the advanced section causes the whole app to boot loop:

listen 443 ssl http2; listen [::]:443 ssl http2;

even commenting them out gets reversed on reboot for some reason. I had to fully remove the lines to keep that from happening.

Nginx Proxy Manager Version 2.10.4

To Reproduce Steps to reproduce the behavior:

  1. Go to any proxy_host, edit
  2. force ssl
  3. add listen 443 ssl http2; to advanced section
  4. restart container
  5. boot loop

Expected behavior npm should just ignore the doubled line or at least kill the one host instead of downing the whole system behind it.

Screenshots image image

Operating System Ubuntu 22.04.3 -> Docker Compose

Additional context Fallback_error.log 2023/11/22 20:15:13 [error] 10849#10849: *92907 open() "/var/www/html/robots.txt" failed (2: No such file or directory), client: .222.253.12, server: localhost-nginx-proxy-manager, request: "GET /robots.txt HTTP/1.1", host: "" 2023/11/22 22:46:11 [warn] 11251#11251: 512 worker_connections are not enough, reusing connections 2023/11/22 22:46:11 [alert] 11251#11251: *122878 512 worker_connections are not enough while connecting to upstream, client: 127.0.0.1, server: localhost-nginx-proxy-manager, request: "GET /favicon.ico HTTP/1.1", upstream: "http://127.0.0.1:80/favicon.ico", host: "" 2023/11/22 22:53:25 [error] 11251#11251: 123929 open() "/var/www/html/.env" failed (2: No such file or directory), client: **.236.231.176, server: localhost-nginx-proxy-manager, request: "GET /.env HTTP/1.1", host: "" 2023/11/22 23:27:08 [error] 11392#11392: *128790 open() "/var/www/html/.env" failed (2: No such file or directory), client: .16.38.88, server: localhost-nginx-proxy-manager, request: "GET /.env HTTP/1.1", host: "" 2023/11/22 23:39:22 [warn] 11392#11392: 512 worker_connections are not enough, reusing connections 2023/11/22 23:39:22 [alert] 11392#11392: 512 worker_connections are not enough 2023/11/22 23:39:22 [error] 11393#11393: *131593 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 127.0.0.1, server: localhost-nginx-proxy-manager, request: "GET /favicon.ico HTTP/1.1", upstream: "http://127.0.0.1:80/favicon.ico", host: "*" 2023/11/23 01:06:19 [error] 11607#11607: 145973 open() "/var/www/html/robots.txt" failed (2: No such file or directory), client: 35.217.99.157, server: localhost-nginx-proxy-manager, request: "GET /robots.txt HTTP/1.1", host: "federation.matrix..com" 2023/11/23 01:41:35 [error] 11699#11699: *150478 "/var/www/html/HNAP1/index.html" is not found (2: No such file or directory), client: 94.228.162.87, server: localhost-nginx-proxy-manager, request: "POST /HNAP1/ HTTP/1.1", host: "**:80" 2023/11/23 02:00:01 [alert] 10157#10157: 1688 open socket #49 left in connection 22 2023/11/23 02:00:01 [alert] 10157#10157: *1686 open socket #44 left in connection 47 2023/11/23 02:00:01 [alert] 10157#10157: aborting 2023/11/23 02:00:04 [alert] 10111#10111: worker process 10157 exited on signal 9

Geczy commented 10 months ago

https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2388#issuecomment-1807353881 https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1912

redtripleAAA commented 8 months ago

Getting the same issue here

2024/02/29 05:27:44 [alert] 255#255: *3618 512 worker_connections are not enough while connecting to upstream, client: 127.0.0.1, server: localhost-nginx-proxy-manager, request: "GET /favicon.ico HTTP/1.1", upstream: "http://127.0.0.1:80/favicon.ico", host: "domain", referrer: "http://domain/"

github-actions[bot] commented 1 month ago

Issue is now considered stale. If you want to keep it open, please comment :+1: