December 11, 20241 yr On 12/10/2024 at 11:49 AM, Espressomatic said: You have a bad DNS configuration. https://community.letsencrypt.org/t/failed-to-establish-a-new-connection-errno-3-temporary-failure-in-name-resolution/170617 I'm having this same error as well, but didn't change anything regarding DNS. Nginx just randomly also nuked itself and looks like a completely fresh install after probably last time I just restarted docker, so very odd so I tried creating new files and just copying my proxy_host folder but now I get this error and don't know how to move forward. When I even try to fresh start and create a new proxy it can't connect to my domain, so bad DNS makes sense, but I don't know where or what to change. Do I have to just change Nginx DNS server? Thank you for any help! Nginx DNS below: [1;32mdocker-bfcb45c5a4a9:/app]# cat /etc/resolv.conf nameserver 127.0.0.11 options ndots:0 ❯ Starting backend ... ❯ Starting nginx ... [12/11/2024] [11:38:39 AM] [Global ] › ℹ info Using Sqlite: /data/database.sqlite [12/11/2024] [11:38:40 AM] [Migrate ] › ℹ info Current database version: none [12/11/2024] [11:38:40 AM] [Setup ] › ℹ info Logrotate Timer initialized [12/11/2024] [11:38:40 AM] [Global ] › ⬤ debug CMD: logrotate /etc/logrotate.d/nginx-proxy-manager [12/11/2024] [11:38:40 AM] [Setup ] › ℹ info Logrotate completed. [12/11/2024] [11:38:40 AM] [IP Ranges] › ℹ info Fetching IP Ranges from online services... [12/11/2024] [11:38:40 AM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json [12/11/2024] [11:38:40 AM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v4 [12/11/2024] [11:38:40 AM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v6 [12/11/2024] [11:38:40 AM] [SSL ] › ℹ info Let's Encrypt Renewal Timer initialized [12/11/2024] [11:38:40 AM] [SSL ] › ℹ info Renewing SSL certs expiring within 30 days ... [12/11/2024] [11:38:40 AM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized [12/11/2024] [11:38:40 AM] [Global ] › ℹ info Backend PID 157 listening on port 3000 ... [12/11/2024] [11:38:40 AM] [SSL ] › ℹ info Completed SSL cert renew process [12/11/2024] [11:38:43 AM] [Express ] › ⚠ warning invalid signature [12/11/2024] [11:39:29 AM] [SSL ] › ℹ info Testing http challenge for XXX.duckdns.org [12/11/2024] [11:39:40 AM] [SSL ] › ℹ info HTTP challenge test failed for domain XXX.duckdns.org because error was returned: Invalid domain or IP [12/11/2024] [11:40:47 AM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -t -g "error_log off;" [12/11/2024] [11:40:47 AM] [Nginx ] › ℹ info Reloading Nginx [12/11/2024] [11:40:47 AM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -s reload [12/11/2024] [11:40:53 AM] [SSL ] › ℹ info Requesting Let'sEncrypt certificates for Cert #1: bigweld.duckdns.org [12/11/2024] [11:40:53 AM] [SSL ] › ℹ info Command: certbot certonly --config '/etc/letsencrypt.ini' --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-1" --agree-tos --authenticator webroot --email '[email protected]' --preferred-challenges "dns,http" --domains "XXX.duckdns.org" [12/11/2024] [11:40:53 AM] [Global ] › ⬤ debug CMD: certbot certonly --config '/etc/letsencrypt.ini' --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-1" --agree-tos --authenticator webroot --email '[email protected]' --preferred-challenges "dns,http" --domains "XXX.duckdns.org" [12/11/2024] [11:41:04 AM] [Nginx ] › ⬤ debug Deleting file: /data/nginx/temp/letsencrypt_1.conf [12/11/2024] [11:41:04 AM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -t -g "error_log off;" [12/11/2024] [11:41:04 AM] [Nginx ] › ℹ info Reloading Nginx [12/11/2024] [11:41:04 AM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -s reload [12/11/2024] [11:41:04 AM] [Express ] › ⚠ warning Saving debug log to /tmp/letsencrypt-log/letsencrypt.log Some challenges have failed. Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /tmp/letsencrypt-log/letsencrypt.log or re-run Certbot with -v for more details.
December 12, 20241 yr 19 hours ago, bristopher said: so very odd so I tried creating new files and just copying my proxy_host folder but now I get this error That won't work, as NPM uses a database to store everything it shows in the UI. You'll have to configure everything again from scratch for the least number of headaches. If the NPM docker is installed as instructed and your Unraid system's DNS works, then it will also work from within the NPM docker, so I suggest starting over, and deleting your NPM appdata folder to make sure nothing is reused. Edited December 12, 20241 yr by Espressomatic
December 12, 20241 yr 3 hours ago, Espressomatic said: That won't work, as NPM uses a database to store everything it shows in the UI. You'll have to configure everything again from scratch for the least number of headaches. If the NPM docker is installed as instructed and your Unraid system's DNS works, then it will also work from within the NPM docker, so I suggest starting over, and deleting your NPM appdata folder to make sure nothing is reused. ah darn Just tried a completely new instance and it still can't find my domain (tested it using nmap and it's up), I can't image what's wrong, recently moved drives/data and it might've fragmented NPM but not sure why the DNS isn't working now with a clean install. The port forwarded ports for NPM seem correct with 443-443 and 80-80 with my docker assignment below I can't think of what could go wrong 192.168.1.XXX:443/TCP192.168.1.XXX:443 192.168.1.XXX:80/TCP192.168.1.XXX:80 192.168.1.XXX:81/TCP192.168.1.XXX:81 [12/12/2024] [11:14:08 AM] [SSL ] › ℹ info Completed SSL cert renew process [12/12/2024] [11:14:52 AM] [Express ] › ⚠ warning invalid signature [12/12/2024] [11:15:24 AM] [SSL ] › ℹ info Testing http challenge for XXX.duckdns.org [12/12/2024] [11:15:34 AM] [SSL ] › ℹ info HTTP challenge test failed for domain XXX.duckdns.org because error was returned: Invalid domain or IP
December 12, 20241 yr ping/dig duckdns.org - if that's working, then DNS may no longer be an issue, and it might be as simple as bad setup at duckDNS or challenge string. The error messages make enough sense to possibly point in the wrong direction - example what invalid domain? Duckdns itself or the domain you're running the challenge against?
December 13, 20241 yr I can ping my subdomain at Duckdns from unraid, but the NPM container doesn't have nmap/ping/dig. There's also no config at Duckdns other than your public ip and sub domain which is correct (and haven't changed) and also updates with a duckdns container I also run on unaird. Really stumpted Edit: did what it said in the link below and also started adding duckdns dns challenge, not sure which fixed it, thanks everybody! https://community.alarmiator.de/t/lets-encrypt-zertifikat-wird-von-nginx-proxy-manager-nicht-aktualisiert/380/3 Source: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/396 Edited December 13, 20241 yr by bristopher fixed my problem
December 13, 20241 yr For anyone having issues of not being able to renew certificates. This method worked for me. I was pulling my hair out all over this issue. lol.... Found on Github..... https://github.com/NginxProxyManager/nginx-proxy-manager/issues/396 Found the solution. Steps I took: Go to cloudflare, set proxy status to "DNS Only" Wait a couple of minutes. Go to Dashboard, Proxy Hosts, disable source, now you can update the ssl certificate. Enable source, and set proxy status back to Proxied on cloudflare. Hopefully I'm helping someone out there.
December 13, 20241 yr 1 hour ago, Mrtj18 said: For anyone having issues of not being able to renew certificates. This method worked for me. I was pulling my hair out all over this issue. lol.... Found on Github..... https://github.com/NginxProxyManager/nginx-proxy-manager/issues/396 Found the solution. Steps I took: Go to cloudflare, set proxy status to "DNS Only" Wait a couple of minutes. Go to Dashboard, Proxy Hosts, disable source, now you can update the ssl certificate. Enable source, and set proxy status back to Proxied on cloudflare. Hopefully I'm helping someone out there. interesting I found a backup of my working NPM folder and now are also having the same issues as everyone, but I use DuckDns and can't set proxy status or anything and stuck looping these errors and can't access GUI because of it oh geez. Trying to figure out how to remove my cert without the GUI Edit: had to use this to link to fix it and use new cert which I got using code below https://github.com/NginxProxyManager/nginx-proxy-manager/issues/396#issuecomment-2409082914 docker exec -it Nginx-Proxy-Manager-Official /bin/sh certbot certonly --webroot -w /data/letsencrypt-acme-challenge -d yourdomain.com or this command certbot certonly --manual --preferred-challenges=dns -d yourdomain.com then using this to fix all the errors as seen here https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4060#issuecomment-2478182722 for file in /mnt/user/appdata/Nginx-Proxy-Manager-Official/data/nginx/proxy_host/*.conf; do sed -i 's/listen 443 ssl http2;/listen 443 ssl;\nhttp2 on;/g' "$file" done and fixed it all but the database still wiped itself womp womp oh well atleast I can create certs again ❯ Starting nginx ... nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/10.conf:14 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/10.conf:15 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/13.conf:19 nginx: [warn] protocol options redefined for 0.0.0.0:443 in /data/nginx/proxy_host/13.conf:19 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/13.conf:20 nginx: [warn] protocol options redefined for [::]:443 in /data/nginx/proxy_host/13.conf:20 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/14.conf:19 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/14.conf:20 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/15.conf:19 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/15.conf:20 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/16.conf:14 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/16.conf:15 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/17.conf:14 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/17.conf:15 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/18.conf:19 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/18.conf:20 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/25.conf:19 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/25.conf:20 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/25old.conf:19 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/25old.conf:20 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/26.conf:19 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/26.conf:20 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/28.conf:19 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/28.conf:20 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/7.conf:14 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/7.conf:15 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/8.conf:14 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/8.conf:15 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/9.conf:19 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/9.conf:20 nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-5/fullchain.pem": PEM_read_bio_X509_AUX() failed (SSL: error:0480006C:PEM routines::no start line:Expecting: TRUSTED CERTIFICATE) ❯ Starting nginx ... Edited December 13, 20241 yr by bristopher the process man
December 13, 20241 yr 59 minutes ago, bristopher said: interesting I found a backup of my working NPM folder and now are also having the same issues as everyone, but I use DuckDns and can't set proxy status or anything and stuck looping these errors and can't access GUI because of it oh geez. Trying to figure out how to remove my cert without the GUI ❯ Starting nginx ... nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/10.conf:14 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/10.conf:15 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/13.conf:19 nginx: [warn] protocol options redefined for 0.0.0.0:443 in /data/nginx/proxy_host/13.conf:19 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/13.conf:20 nginx: [warn] protocol options redefined for [::]:443 in /data/nginx/proxy_host/13.conf:20 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/14.conf:19 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/14.conf:20 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/15.conf:19 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/15.conf:20 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/16.conf:14 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/16.conf:15 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/17.conf:14 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/17.conf:15 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/18.conf:19 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/18.conf:20 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/25.conf:19 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/25.conf:20 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/25old.conf:19 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/25old.conf:20 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/26.conf:19 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/26.conf:20 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/28.conf:19 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/28.conf:20 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/7.conf:14 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/7.conf:15 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/8.conf:14 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/8.conf:15 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/9.conf:19 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/9.conf:20 nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-5/fullchain.pem": PEM_read_bio_X509_AUX() failed (SSL: error:0480006C:PEM routines::no start line:Expecting: TRUSTED CERTIFICATE) ❯ Starting nginx ... I ran into this error when I attempted to do the same. Copy over a " previous working" copy of NGIX. I think there is some sort of file difference between the current version and older version's preventing NGIX from starting. And not seeing any GUI. I had to just resort to a current total build
December 13, 20241 yr The bottom line is that you can't easily port settings from one instance to another. The easiest thing to do is to make a full/complete backup and restore. There are a lot of config files in a number of places, plus database files. Lots of encryption keys and other settings, if anything is mismatched, it leads to unrecoverable errors and things break. Some of those cause the entire UI to go tits-up. NPM is like a delicate and elaborate castle made of loose playing cards. If you don't look at it the wrong way, it's reliable. Start to poke under the hood too much and.... As an aside: I'm sure that Caddy and Traefik are far more reliable and robust alternatives for anyone interested. It's just that they've been designed to be impossible to understand, even for people who claim to be experts on the topic, and near-impossible to install correctly for anyone else. So that's why I also continue to use NPM. Edited December 13, 20241 yr by Espressomatic
December 16, 20241 yr This evening Nginx Proxy Manager hung up. Log was full of this so unsure if it’s the cause? What can I do or do I need to change where to remove this error from spamming the log? Edited December 16, 20241 yr by blaine07
December 16, 20241 yr 4 hours ago, blaine07 said: Log was full of this so unsure if it’s the cause? Thats because the container saves the config files still in an old way. 4 hours ago, blaine07 said: What can I do or do I need to change where to remove this error from spamming the log? You *could* change all the config files manually BUT if you change anything through the GUI it will resurface. Gotta wait till the container is updated. The fix was already merged for that To temporarily fix it, stop the container and edit any listen X.X.X.X:443 ssl http2; needs the http2 line removed to look like listen X.X.X.X:443 ssl; and only place http2 on; below it once
December 16, 20241 yr 2 hours ago, Mainfrezzer said: Thats because the container saves the config files still in an old way. You *could* change all the config files manually BUT if you change anything through the GUI it will resurface. Gotta wait till the container is updated. The fix was already merged for that To temporarily fix it, stop the container and edit any listen X.X.X.X:443 ssl http2; needs the http2 line removed to look like listen X.X.X.X:443 ssl; and only place http2 on; below it once Could that have indeed been cause for my container freezing or no? Thank you!
December 18, 20241 yr Hey there, i recently got some issues with the basic auth thingy. I have a basic "public" group, which redirects to authelia and for some servies i created a basic auth with IP based allowance (like searchnxg), when updating to the latest i get SSL issues or something, while it runs fine on 2.11.3 - does anyone know waht exactly changed? Couldn´t really find a hint in the changelogs or anywhere else Cheers!
December 28, 20241 yr On 12/26/2024 at 7:00 PM, NLS said: Is this like an alternative (or better) SWAG? Insofar as it's a reverse proxy, yes. It also comes with certbot for certificate provisioning and can serve web indexes/pages if you need a fast/quick way to get up a basic page or two locally.
December 31, 20241 yr Hi all, i recently had to find out two of my four Proxy Hosts are no longer reachable (via IP: no problem). I get a "error 504" I can't remember of any changes in network in nearer past, so i can't explain why from one day to the other it no longer works. Only obvious difference between the two working and the two not working Proxy Hosts is: The NON-working are hosted on Unraid in Host or bridge mode while the two working Hosts are in custom eth0 network (vaultwarden) or on another machine (homeassistant) NPM is running in custom eth0 I activated (due to older MACVLAN issue with Fritzbox) Host access to custom networks: Proxy Host overview: Any hints where to problem could be?
January 3, 20251 yr @mgutt hi mgutt is it possible for mail.example.com ==> 192.168.1.1:5000/?launchApp=SYNO.SDS.MailClient.Application if yes, how to make setting in NPM thanks
January 5, 20251 yr Hello Im having some trouble with having npm to work?? This is my output.. User: npm PUID:0 ID:0 GROUP:0 Group: npm PGID:0 ID:0 ------------------------------------- ❯ Starting nginx ... ❯ Starting backend ... [1/5/2025] [2:01:42 PM] [Global ] › ℹ info Using Sqlite: /data/database.sqlite [1/5/2025] [2:01:42 PM] [Migrate ] › ℹ info Current database version: none [1/5/2025] [2:01:42 PM] [Setup ] › ℹ info Logrotate Timer initialized [1/5/2025] [2:01:42 PM] [Global ] › ⬤ debug CMD: logrotate /etc/logrotate.d/nginx-proxy-manager [1/5/2025] [2:01:42 PM] [Setup ] › ℹ info Logrotate completed. [1/5/2025] [2:01:42 PM] [IP Ranges] › ℹ info Fetching IP Ranges from online services... [1/5/2025] [2:01:42 PM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json [1/5/2025] [2:01:58 PM] [IP Ranges] › ✖ error getaddrinfo EAI_AGAIN ip-ranges.amazonaws.com [1/5/2025] [2:01:58 PM] [SSL ] › ℹ info Let's Encrypt Renewal Timer initialized [1/5/2025] [2:01:58 PM] [SSL ] › ℹ info Renewing SSL certs expiring within 30 days ... [1/5/2025] [2:01:58 PM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized [1/5/2025] [2:01:58 PM] [Global ] › ℹ info Backend PID 155 listening on port 3000 ... [1/5/2025] [2:01:58 PM] [SSL ] › ℹ info Completed SSL cert renew process [1/5/2025] [2:13:19 PM] [Global ] › ℹ info PID 155 received SIGTERM [1/5/2025] [2:13:19 PM] [Global ] › ℹ info Stopping. ❯ Configuring npm user ... 0 usermod: no changes ❯ 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/log.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 ... I do not know how to fix this.. Hope you have an idea Thank you regards..
January 6, 20251 yr 20 hours ago, Mattti1912 said: Hello Im having some trouble with having npm to work?? This is my output.. User: npm PUID:0 ID:0 GROUP:0 Group: npm PGID:0 ID:0 ------------------------------------- ❯ Starting nginx ... ❯ Starting backend ... [1/5/2025] [2:01:42 PM] [Global ] › ℹ info Using Sqlite: /data/database.sqlite [1/5/2025] [2:01:42 PM] [Migrate ] › ℹ info Current database version: none [1/5/2025] [2:01:42 PM] [Setup ] › ℹ info Logrotate Timer initialized [1/5/2025] [2:01:42 PM] [Global ] › ⬤ debug CMD: logrotate /etc/logrotate.d/nginx-proxy-manager [1/5/2025] [2:01:42 PM] [Setup ] › ℹ info Logrotate completed. [1/5/2025] [2:01:42 PM] [IP Ranges] › ℹ info Fetching IP Ranges from online services... [1/5/2025] [2:01:42 PM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json [1/5/2025] [2:01:58 PM] [IP Ranges] › ✖ error getaddrinfo EAI_AGAIN ip-ranges.amazonaws.com [1/5/2025] [2:01:58 PM] [SSL ] › ℹ info Let's Encrypt Renewal Timer initialized [1/5/2025] [2:01:58 PM] [SSL ] › ℹ info Renewing SSL certs expiring within 30 days ... [1/5/2025] [2:01:58 PM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized [1/5/2025] [2:01:58 PM] [Global ] › ℹ info Backend PID 155 listening on port 3000 ... [1/5/2025] [2:01:58 PM] [SSL ] › ℹ info Completed SSL cert renew process [1/5/2025] [2:13:19 PM] [Global ] › ℹ info PID 155 received SIGTERM [1/5/2025] [2:13:19 PM] [Global ] › ℹ info Stopping. ❯ Configuring npm user ... 0 usermod: no changes ❯ 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/log.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 ... I do not know how to fix this.. Hope you have an idea Thank you regards.. The error: [1/5/2025] [2:01:58 PM] [IP Ranges] › ✖ error getaddrinfo EAI_AGAIN ip-ranges.amazonaws.com Is indicating a DNS issue. Edited January 6, 20251 yr by pacnpal
January 11, 20251 yr On 12/31/2024 at 1:00 PM, jj1987 said: Hi all, i recently had to find out two of my four Proxy Hosts are no longer reachable (via IP: no problem). I get a "error 504" I can't remember of any changes in network in nearer past, so i can't explain why from one day to the other it no longer works. ... After updating to Unraid v7 stable, everything is fine again🤷♂️
January 17, 20251 yr On 1/6/2025 at 5:57 PM, pacnpal said: The error: [1/5/2025] [2:01:58 PM] [IP Ranges] › ✖ error getaddrinfo EAI_AGAIN ip-ranges.amazonaws.com Is indicating a DNS issue. I got the same one. Any suggestions for a solution??
January 25, 20251 yr May i ask for a working NPM conf file for a local plex docker server? I have several services running via NPM but I just can't get Plex to work via NPM. Something small is missing in my conf file Thank you, -faxxe
January 25, 20251 yr Author 22 minutes ago, faxxe71 said: I have several services running via NPM but I just can't get Plex to work via NPM. Was it possible to receive an SSL cert? It yes, then maybe npm is not able to reach the Plex IP / Port. Different networks? Copying the config from someone else is no guarantee that it works as there are many different IP/port/network settings possible. My config as an example (npm runs on host network and Plex on bridge):
January 25, 20251 yr Sorry, it was my fault. I missed the Unraid setting for the host<>docker communication, which was disabled. Therefore i cant reach the Plex docker (run in host mode). Now it works flawless Thanks for your fast reply.
January 27, 20251 yr Hello, This is the 3rd time i've setup NGINX. after several weeks of running the NGINX instance becomes unstable or fails altogether. The docker shows running and the logs appear normal see logs at the bottom. I restart unraid, reboot the server, restart the docker, makes no difference. the docker shows running with the log below, the API key has been redacted. If i try to open the WebUI page I get a generic unable to connect message. From another pc on the network i can ping the dockers IP. Ports 80, 81 and 443 fail to connect when using TCPING to try to verify the ports are open so I can only assume the service is failing to actually start. I am using the default configs BR0 network etc. I can blow away everything, recreate it and reenter all my config and it works fine for a couple weeks then dies again. the config was configured 3 weeks ago, i have not logged into the WebUI or made a single change to NGINX since it was deployed. Suggestions on where to go from here would be greatly appreciated. ❯ Starting backend ... ❯ Starting nginx ... [1/27/2025] [10:10:00 AM] [Global ] › ℹ info Using Sqlite: /data/database.sqlite [1/27/2025] [10:10:01 AM] [Migrate ] › ℹ info Current database version: none [1/27/2025] [10:10:01 AM] [Global ] › ⬤ debug CMD: [ -f '/etc/letsencrypt/credentials/credentials-4' ] || { mkdir -p /etc/letsencrypt/credentials 2> /dev/null; echo '# Cloudflare API token dns_cloudflare_api_token=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' > '/etc/letsencrypt/credentials/credentials-4' && chmod 600 '/etc/letsencrypt/credentials/credentials-4'; } [1/27/2025] [10:10:01 AM] [Certbot ] › ▶ start Installing cloudflare... [1/27/2025] [10:10:01 AM] [Global ] › ⬤ debug CMD: . /opt/certbot/bin/activate && pip install --no-cache-dir cloudflare==2.19.* acme==$(certbot --version | grep -Eo '[0-9](\.[0-9]+)+') certbot-dns-cloudflare==$(certbot --version | grep -Eo '[0-9](\.[0-9]+)+') && deactivate [1/27/2025] [10:10:04 AM] [Certbot ] › ☒ complete Installed cloudflare [1/27/2025] [10:10:04 AM] [Setup ] › ℹ info Added Certbot plugins cloudflare [1/27/2025] [10:10:04 AM] [Setup ] › ℹ info Logrotate Timer initialized [1/27/2025] [10:10:04 AM] [Global ] › ⬤ debug CMD: logrotate /etc/logrotate.d/nginx-proxy-manager [1/27/2025] [10:10:04 AM] [Setup ] › ℹ info Logrotate completed. [1/27/2025] [10:10:04 AM] [IP Ranges] › ℹ info Fetching IP Ranges from online services... [1/27/2025] [10:10:04 AM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json [1/27/2025] [10:10:05 AM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v4 [1/27/2025] [10:10:05 AM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v6 [1/27/2025] [10:10:05 AM] [SSL ] › ℹ info Let's Encrypt Renewal Timer initialized [1/27/2025] [10:10:05 AM] [SSL ] › ℹ info Renewing SSL certs expiring within 30 days ... [1/27/2025] [10:10:05 AM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized [1/27/2025] [10:10:05 AM] [Global ] › ℹ info Backend PID 163 listening on port 3000 ... [1/27/2025] [10:10:05 AM] [SSL ] › ℹ info Completed SSL cert renew process [1/27/2025] [10:24:12 AM] [Global ] › ℹ info PID 163 received SIGTERM [1/27/2025] [10:24:12 AM] [Global ] › ℹ info Stopping. ❯ Configuring npm user ... 0 usermod: no changes ❯ 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/log.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 - /data/nginx/proxy_host/2.conf - /data/nginx/proxy_host/3.conf - /data/nginx/proxy_host/5.conf - /data/nginx/proxy_host/6.conf - /data/nginx/proxy_host/8.conf - /data/nginx/proxy_host/9.conf - /data/nginx/proxy_host/4.conf - /data/nginx/proxy_host/7.conf ❯ Docker secrets ... ------------------------------------- _ _ ____ __ __ | \ | | _ \| \/ | | \| | |_) | |\/| | | |\ | __/| | | | |_| \_|_| |_| |_| ------------------------------------- User: npm PUID:0 ID:0 GROUP:0 Group: npm PGID:0 ID:0 ------------------------------------- ❯ Starting nginx ... ❯ Starting backend ... [1/27/2025] [10:25:05 AM] [Global ] › ℹ info Using Sqlite: /data/database.sqlite [1/27/2025] [10:25:06 AM] [Migrate ] › ℹ info Current database version: none [1/27/2025] [10:25:06 AM] [Global ] › ⬤ debug CMD: [ -f '/etc/letsencrypt/credentials/credentials-4' ] || { mkdir -p /etc/letsencrypt/credentials 2> /dev/null; echo '# Cloudflare API token dns_cloudflare_api_token=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' > '/etc/letsencrypt/credentials/credentials-4' && chmod 600 '/etc/letsencrypt/credentials/credentials-4'; } [1/27/2025] [10:25:06 AM] [Certbot ] › ▶ start Installing cloudflare... [1/27/2025] [10:25:06 AM] [Global ] › ⬤ debug CMD: . /opt/certbot/bin/activate && pip install --no-cache-dir cloudflare==2.19.* acme==$(certbot --version | grep -Eo '[0-9](\.[0-9]+)+') certbot-dns-cloudflare==$(certbot --version | grep -Eo '[0-9](\.[0-9]+)+') && deactivate [1/27/2025] [10:25:09 AM] [Certbot ] › ☒ complete Installed cloudflare [1/27/2025] [10:25:09 AM] [Setup ] › ℹ info Added Certbot plugins cloudflare [1/27/2025] [10:25:09 AM] [Setup ] › ℹ info Logrotate Timer initialized [1/27/2025] [10:25:09 AM] [Global ] › ⬤ debug CMD: logrotate /etc/logrotate.d/nginx-proxy-manager [1/27/2025] [10:25:09 AM] [Setup ] › ℹ info Logrotate completed. [1/27/2025] [10:25:09 AM] [IP Ranges] › ℹ info Fetching IP Ranges from online services... [1/27/2025] [10:25:09 AM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json [1/27/2025] [10:25:10 AM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v4 [1/27/2025] [10:25:10 AM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v6 [1/27/2025] [10:25:10 AM] [SSL ] › ℹ info Let's Encrypt Renewal Timer initialized [1/27/2025] [10:25:10 AM] [SSL ] › ℹ info Renewing SSL certs expiring within 30 days ... [1/27/2025] [10:25:10 AM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized [1/27/2025] [10:25:10 AM] [Global ] › ℹ info Backend PID 163 listening on port 3000 ... [1/27/2025] [10:25:10 AM] [SSL ] › ℹ info Completed SSL cert renew process
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.