nginx-proxy-manager icon indicating copy to clipboard operation
nginx-proxy-manager copied to clipboard
Published 1 month ago • verified publisher icon NginxProxyManager

Not a single npm version after 2.9.19 works for me.

Open SuperGaleb opened this issue 1 year ago • 1 comments

Checklist

  • Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
    • Yes
  • Are you sure you're not using someone else's docker image?
    • Yes
  • Have you searched for similar issues (both open and closed)?
    • Yes

Describe the bug

I am running npm behind pfsense / haproxy. I can access admin, issue/renew all certs, no problem. I tried clean install (blank db) no luck, different db, no luck.

Nginx Proxy Manager Version

All / any version after 2.9.19 does not work anymore (all earlier versions work fine).

To Reproduce Steps to reproduce the behavior:

  1. image: 'jc21/nginx-proxy-manager:latest
  2. can't access any webservers behind npm, admin panel works fine, I can request or renew certificates, add sites, etc.
  3. image: 'jc21/nginx-proxy-manager:2.9.19'
  4. all working fine, all web servers behind npm are accessable

Expected behavior

Access to all web-servers behind npm

Screenshots

image: 'jc21/nginx-proxy-manager:latest' npm-down_2024-01-29 133748

image: 'jc21/nginx-proxy-manager:2.9.19' npm-up_2024-01-29 133748

Operating System

ubuntu and/or arch

docker info Client: Version: 24.0.7 Context: default Debug Mode: false Plugins: compose: Docker Compose (Docker Inc.) Version: 2.24.3 Path: /usr/lib/docker/cli-plugins/docker-compose Additional context

docker logs eba49551bbd7 ❯ Configuring npm user ... ❯ Configuring npm group ... ❯ Checking paths ... ❯ Setting ownership ... ❯ Dynamic resolvers ... ❯ IPv6 ... Enabling IPV6 in hosts in: /etc/nginx/conf.d

  • /etc/nginx/conf.d/default.conf
  • /etc/nginx/conf.d/include/assets.conf
  • /etc/nginx/conf.d/include/block-exploits.conf
  • /etc/nginx/conf.d/include/force-ssl.conf
  • /etc/nginx/conf.d/include/ip_ranges.conf
  • /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
  • /etc/nginx/conf.d/include/proxy.conf
  • /etc/nginx/conf.d/include/ssl-ciphers.conf
  • /etc/nginx/conf.d/include/resolvers.conf
  • /etc/nginx/conf.d/production.conf Enabling IPV6 in hosts in: /data/nginx
  • /data/nginx/proxy_host/1.conf ❯ Docker secrets ...

| \ | | _ | / | | | | |) | |/| | | |\ | __/| | | | || _|| || |_|

User: npm PUID:1001 ID:1001 GROUP:999 Group: npm PGID:999 ID:999

❯ Starting backend ... ❯ Starting nginx ... nginx: [warn] the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /etc/nginx/nginx.conf:4 [1/29/2024] [1:51:44 PM] [Global ] › ℹ info Using MySQL configuration [1/29/2024] [1:51:45 PM] [Migrate ] › ℹ info Current database version: 20211108145214 [1/29/2024] [1:51:45 PM] [Global ] › ⬤ debug CMD: [ -f '/etc/letsencrypt/credentials/credentials-2' ] || { mkdir -p /etc/letsencrypt/credentials 2> /dev/null; echo '# Cloudflare API token dns_cloudflare_api_token = wfqk1lBsIgV3skVGYR49qll6Ws9ntwMDVRpRyVn7' > '/etc/letsencrypt/credentials/credentials-2' && chmod 600 '/etc/letsencrypt/credentials/credentials-2'; } [1/29/2024] [1:51:45 PM] [Certbot ] › ▶ start Installing cloudflare... [1/29/2024] [1:51:45 PM] [Global ] › ⬤ debug CMD: . /opt/certbot/bin/activate && pip install --no-cache-dir cloudflare acme==$(certbot --version | grep -Eo '0-9+') certbot-dns-cloudflare==$(certbot --version | grep -Eo '0-9+') && deactivate [1/29/2024] [1:51:47 PM] [Certbot ] › ☒ complete Installed cloudflare [1/29/2024] [1:51:47 PM] [Setup ] › ℹ info Added Certbot plugins cloudflare [1/29/2024] [1:51:47 PM] [Setup ] › ℹ info Logrotate Timer initialized [1/29/2024] [1:51:47 PM] [Global ] › ⬤ debug CMD: logrotate /etc/logrotate.d/nginx-proxy-manager [1/29/2024] [1:51:47 PM] [Setup ] › ℹ info Logrotate completed. [1/29/2024] [1:51:47 PM] [IP Ranges] › ℹ info Fetching IP Ranges from online services... [1/29/2024] [1:51:47 PM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json [1/29/2024] [1:51:47 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v4 [1/29/2024] [1:51:47 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v6 [1/29/2024] [1:51:47 PM] [SSL ] › ℹ info Let's Encrypt Renewal Timer initialized [1/29/2024] [1:51:47 PM] [SSL ] › ℹ info Renewing SSL certs expiring within 30 days ... [1/29/2024] [1:51:47 PM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized [1/29/2024] [1:51:47 PM] [Global ] › ℹ info Backend PID 163 listening on port 3000 ... [1/29/2024] [1:51:47 PM] [SSL ] › ℹ info Completed SSL cert renew process

SuperGaleb avatar Jan 29 '24 02:01 SuperGaleb

I can confirm that 2.11.1 produced many unreachable host errors while everything looked in order. I have rolled back to 2.11.0 and for now it seems to work, but I'm not 100% sure because the outages were not constant, sometimes my cloudflare domains were up, sometimes not, so I'll have to wait and see. I'm on Orange Pi 3 LTS running Docker inside OMV6/Armbian. EDIT After 3 hours my domains were down again (reachable via local IP). Tried 2.9.19, but got error

❯ Starting backend ...
node: --openssl-legacy-provider is not allowed in NODE_OPTIONS

I'm not sure how to fix that, so I went back to :latest which does not give that error.

janaxhell avatar Jan 29 '24 16:01 janaxhell