[Support] Nginx Proxy Manager (NPM) Official


Recommended Posts

8 minutes ago, sisco223 said:

Hi all, I upgraded Unraid to 6.12 rc2 and now NPM doesn't work. The docker starts, but I get says page can't be displayed. Here is the logs window. Has anyone else had this issue? I see it says "failed to properly bring all the services up" But it is started and stuck on "settings ownership". 

 

image.thumb.png.f96690d7dd462ac648fcffba60714540.png 

jc21/nginx-proxy-manager:2.9.22

Link to comment

I have the same problem with the new version

My docker was already set to 911:911 as permissions and when i updated it did not work.

I tried to set PUID and PGID to 99 and 100, obviously it did not work because it is different from the file permissions.

I chown 'ed the folder to 99 100 and still it did not work.

I set the version to 2.9.22 as suggested by Tweak91 and it started.

Files user:group now is the same as variables on the docker. (99:100, before was 911:911)

 

 

Mind that I'm still at version 6.11.5 of UNRAID

Link to comment
12 hours ago, blaine07 said:

What did you set PUID and PGID as?

I used 99 for PUID and 100 for PGID per the results of ls -lahn. My variables looks identical to your screens. The container instantly fails when I try to start. Nothing has been written to the log folder since I updated or to /tmp/Nginx-Proxy-Manager-Official/var/log where error logs are pointed so I'm not sure even how to troubleshoot the issue.

Edited by iceperson
Link to comment
4 minutes ago, iceperson said:

I used 99 for PGID and 100 for PUID per the results of ls -lahn. My variables looks identical to your screens. The container instantly fails when I try to start. Nothing has been written to the log folder since I updated or to /tmp/Nginx-Proxy-Manager-Official/var/log where error logs are pointed so I'm not sure even how to troubleshoot the issue.

In shares browsing to that folder in appdata who does it show “owns” it out of curiosity? In a sec I can upload a pic of what I’m talking about…

Link to comment
Just now, iceperson said:

Tried 'chown root Nginx-Proxy-Manager-Official' but the container still doesn't start. Is there any other log location where I might be able to see any error when it instantly fails to start?

There was some way jc21 was telling them, on github, to enable a "debug" type mode that provided more logging but not sure if he was kicking it off with a ENV or what.

Link to comment

yeah #me-too 😞

Installed update of NPM this morning, does not start anymore 😞

 

nginx: [emerg] bind() to 0.0.0.0:80 failed (13: Permission denied)

 

What to do?

 

full log:

[3/29/2023] [7:51:13 AM] [SSL      ] › ℹ  info      Renewing SSL certs close to expiry...
[3/29/2023] [7:51:13 AM] [IP Ranges] › ℹ  info      IP Ranges Renewal Timer initialized
[3/29/2023] [7:51:13 AM] [Global   ] › ℹ  info      Backend PID 136 listening on port 3000 ...
[3/29/2023] [7:51:14 AM] [SSL      ] › ✖  error     Error: Command failed: /usr/sbin/nginx -t -g "error_log off;"
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: [emerg] bind() to 0.0.0.0:80 failed (13: Permission denied)
nginx: configuration file /etc/nginx/nginx.conf test failed

    at ChildProcess.exithandler (node:child_process:402:12)
    at ChildProcess.emit (node:events:513:28)
    at maybeClose (node:internal/child_process:1100:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)
❯ Starting nginx ...

 

Update: even rolling back the docker to the version 2 days before did not help. Still does not start anymore 😞

All certs lost???

 

Update2: back to nginx-proxy-manager:2.9.22, works again!!!

Edited by MAM59
Link to comment

Hallo zusammen

 

ich habe ein Problem mit meiner NPM Installation. Wenn ich einen neuen Proxy Host erfasse und für diesen ein SSL Zertifikat erstellen lassen will wird mir folgender Fehler angezeigt:

 

Error: Command failed: certbot certonly --config "/etc/letsencrypt.ini" --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-28" --agree-tos --authenticator webroot --email "hier-steht-meine-mail-adresse" --preferred-challenges "dns,http" --domains "satisfactory.beispieldomain.ch" 
Another instance of Certbot is already running.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /tmp/certbot-log-qtfywjgr/log or re-run Certbot with -v for more details.

    at ChildProcess.exithandler (node:child_process:402:12)
    at ChildProcess.emit (node:events:513:28)
    at maybeClose (node:internal/child_process:1100:16)
    at Socket. (node:internal/child_process:458:11)
    at Socket.emit (node:events:513:28)
    at Pipe. (node:net:301:12)

 

In den Logs vom Container wird folgendes angezeigt:

 

[3/28/2023] [9:15:06 PM] [Global   ] › ℹ  info      PID 134 received SIGTERM
[3/28/2023] [9:15:06 PM] [Global   ] › ℹ  info      Stopping.
❯ Configuring npmuser ...
911
❯ Checking paths ...
❯ Setting ownership ...
❯ Dynamic resolvers ...
❯ IPv6 ...
Enabling IPV6 in hosts in: /etc/nginx/conf.d
- /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/default.conf
- /etc/nginx/conf.d/production.conf
Enabling IPV6 in hosts in: /data/nginx
- /data/nginx/proxy_host/10.conf
- /data/nginx/proxy_host/11.conf
- /data/nginx/proxy_host/7.conf
- /data/nginx/proxy_host/3.conf
- /data/nginx/proxy_host/1.conf
- /data/nginx/proxy_host/4.conf
❯ Docker secrets ...

-------------------------------------
 _   _ ____  __  __
| \ | |  _ \|  \/  |
|  \| | |_) | |\/| |
| |\  |  __/| |  | |
|_| \_|_|   |_|  |_|
-------------------------------------
User UID: 911
User GID: 911
-------------------------------------

❯ Starting nginx ...
❯ Starting backend ...
[3/28/2023] [9:15:25 PM] [Global   ] › ℹ  info      Using Sqlite: /data/database.sqlite
[3/28/2023] [9:15:26 PM] [Migrate  ] › ℹ  info      Current database version: none
[3/28/2023] [9:15:26 PM] [Setup    ] › ℹ  info      Logrotate Timer initialized
[3/28/2023] [9:15:26 PM] [Setup    ] › ℹ  info      Logrotate completed.
[3/28/2023] [9:15:26 PM] [IP Ranges] › ℹ  info      Fetching IP Ranges from online services...
[3/28/2023] [9:15:26 PM] [IP Ranges] › ℹ  info      Fetching https://ip-ranges.amazonaws.com/ip-ranges.json
[3/28/2023] [9:15:26 PM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v4
[3/28/2023] [9:15:26 PM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v6
[3/28/2023] [9:15:26 PM] [SSL      ] › ℹ  info      Let's Encrypt Renewal Timer initialized
[3/28/2023] [9:15:26 PM] [SSL      ] › ℹ  info      Renewing SSL certs close to expiry...
[3/28/2023] [9:15:26 PM] [IP Ranges] › ℹ  info      IP Ranges Renewal Timer initialized
[3/28/2023] [9:15:26 PM] [Global   ] › ℹ  info      Backend PID 135 listening on port 3000 ...
[3/28/2023] [9:17:14 PM] [Nginx    ] › ⬤  debug     Deleting file: /data/nginx/proxy_host/11.conf
[3/28/2023] [9:17:14 PM] [Nginx    ] › ⬤  debug     Deleting file: /data/nginx/proxy_host/11.conf.err
[3/28/2023] [9:17:14 PM] [Nginx    ] › ⬤  debug     Could not delete file: {
  "errno": -2,
  "syscall": "unlink",
  "code": "ENOENT",
  "path": "/data/nginx/proxy_host/11.conf.err"
}
[3/28/2023] [9:17:14 PM] [Nginx    ] › ℹ  info      Reloading Nginx
[3/28/2023] [9:17:19 PM] [SSL      ] › ℹ  info      Requesting Let'sEncrypt certificates for Cert #28: satisfactory.beispieldomain.ch
[3/28/2023] [9:17:19 PM] [SSL      ] › ℹ  info      Command: certbot certonly --config "/etc/letsencrypt.ini" --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-28" --agree-tos --authenticator webroot --email "hier-steht-meine-mail-adresse" --preferred-challenges "dns,http" --domains "satisfactory.beispieldomain.ch" 
[3/28/2023] [9:17:19 PM] [Nginx    ] › ⬤  debug     Deleting file: /data/nginx/temp/letsencrypt_28.conf
[3/28/2023] [9:17:20 PM] [Nginx    ] › ℹ  info      Reloading Nginx
[3/28/2023] [9:17:20 PM] [Express  ] › ⚠  warning   Command failed: certbot certonly --config "/etc/letsencrypt.ini" --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-28" --agree-tos --authenticator webroot --email "hier-steht-meine-mail-adresse" --preferred-challenges "dns,http" --domains "satisfactory.beispieldomain.ch" 
Another instance of Certbot is already running.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /tmp/certbot-log-qtfywjgr/log or re-run Certbot with -v for more details.

 

Den Container habe ich bereits neu gestartet und aktualisiert, die bestehenden Proxy Hosts funktionieren aktuell noch, ich weiss aber nicht was passiert wenn die Zertifikate aktualisiert werden müssen. 

Ich habe den Docker Container von @mgutt installiert, die Ports 80 und 443 sind entsprechend im Router weitergeleitet. Ich bin aktuell auf Unraid 6.12.0-rc2.

 

Vielen Dank für eure Hilfe!

Edited by b_tob
Link to comment
9 hours ago, fir3drag0n said:

Kann ich das irgendwie backupen und dann neu einspielen bei einer Neuinstallation?

mach einfach ein downgrade, die Einstellungen bleiben erhalten.

Bei den (erweiterten) Docker Einstellungen

grafik.thumb.png.720467eaf4c0f3b36efaab8cd3afb284.png

Diese "Quelle" angeben (steht hinten normalerweise ":latest")

Und schon fluppt es wieder.

Keine Ahnung, warum jemand darumfudeln musste, fluppte doch eigentlich sauber und stressfrei

 

Link to comment
1 hour ago, Kilrah said:

Issue's been fixed in current 2.10.2

This is NOT true, I just tried. Still "permission denied" errors over and over and NPM does not start anymore (at least on UNRAID 6.12.rc2).

 

2.9.22 is the latest working version for now.

 

Edited by MAM59
Link to comment

Is there a way to increase the timeout for host requests for all proxy hosts?  I notice when I hit some Arr apps my manual search requests time out if there are too many results to load, I'm curious as to whether or not this is a timeout issue that I can increase the time interval for.  Thanks in advance.

Link to comment
3 hours ago, MAM59 said:

This is NOT true, I just tried. Still "permission denied" errors over and over and NPM does not start anymore (at least on UNRAID 6.12.rc2).

 

2.9.22 is the latest working version for now.

All fine here, but unlike some I didn't mess with stuff trying to fix things.

When it didn't start on 2.10.0 I directly reverted to 2.9.22 without changing anything. Now 2.10.2 is fine again. 

Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.