Nginx Proxy Manager not starting after upgrage

[DJKatastrof]

Any ideas?

[tteck]

Since I don't utilize Nginx Proxy Manager, I created a new container and updated it without encountering any problems. You didn't specify the version from which you were upgrading.

    _   __      _               ____                           __  ___                                 
   / | / /___ _(_)___  _  __   / __ \_________ __  ____  __   /  |/  /___ _____  ____ _____ ____  _____
  /  |/ / __  / / __ \| |/_/  / /_/ / ___/ __ \| |/_/ / / /  / /|_/ / __  / __ \/ __  / __  / _ \/ ___/
 / /|  / /_/ / / / / />  <   / ____/ /  / /_/ />  </ /_/ /  / /  / / /_/ / / / / /_/ / /_/ /  __/ /    
/_/ |_/\__, /_/_/ /_/_/|_|  /_/   /_/   \____/_/|_|\__, /  /_/  /_/\__,_/_/ /_/\__,_/\__, /\___/_/     
      /____/                                      /____/                            /____/             
 
Using Advanced Settings
Using Distribution: debian
Using debian Version: 12
Using Container Type: 1
Using Root Password: Automatic Login
Container ID: 112
Using Hostname: nginxproxymanager
Using Disk Size: 4
Allocated Cores: 1
Allocated RAM: 1024
Using Bridge: vmbr0
Using IP Address: dhcp
Using Gateway IP Address: Default
Disable IPv6: yes
Using Interface MTU Size: Default
Using DNS Search Domain: Host
Using DNS Server IP Address: Host
Using MAC Address: AE:1A:60:07:B7:59
Using Vlan: Default
Enable Root SSH Access: no
Enable Verbose Mode: no
Creating a Nginx Proxy Manager LXC using the above advanced settings
 ✓ Using local for Template Storage.
 ✓ Using local-lvm for Container Storage.
 ✓ Updated LXC Template List
 ✓ LXC Container 112 was successfully created.
 ✓ Started LXC Container
 ✓ Set up Container OS
 ✓ Network Connected: 192.168.86.253 
 ✓ Internet Connected
 ✓ DNS Resolved github.com to 140.82.112.3
 ✓ Updated Container OS
 ✓ Installed Dependencies
 ✓ Installed Python Dependencies
 ✓ Installed Openresty
 ✓ Installed Node.js
 ✓ Installed Yarn
 ✓ Downloaded Nginx Proxy Manager v2.10.4
 ✓ Set up Enviroment
 ✓ Built Frontend
 ✓ Initialized Backend
 ✓ Created Service
 ✓ Customized Container
 ✓ Started Services
 ✓ Cleaned
 ✓ Completed Successfully!

Nginx Proxy Manager should be reachable by going to the following URL.
         http://192.168.86.253:81 

    _   __      _               ____                           __  ___                                 
   / | / /___ _(_)___  _  __   / __ \_________ __  ____  __   /  |/  /___ _____  ____ _____ ____  _____
  /  |/ / __  / / __ \| |/_/  / /_/ / ___/ __ \| |/_/ / / /  / /|_/ / __  / __ \/ __  / __  / _ \/ ___/
 / /|  / /_/ / / / / />  <   / ____/ /  / /_/ />  </ /_/ /  / /  / / /_/ / / / / /_/ / /_/ /  __/ /    
/_/ |_/\__, /_/_/ /_/_/|_|  /_/   /_/   \____/_/|_|\__, /  /_/  /_/\__,_/_/ /_/\__,_/\__, /\___/_/     
      /____/                                      /____/                            /____/             
 
 ✓ Stopped Services
 ✓ Cleaned Old Files
 ✓ Downloaded NPM v2.10.4
 ✓ Setup Enviroment
 ✓ Built Frontend
 ✓ Initialized Backend
 ✓ Started Services
 ✓ Cleaned
 ✓ Updated Successfully
root@nginxproxymanager:~# 

[DJKatastrof]

Hi!

Yes, thats what I just did, we can close this. Sorry.

[Stephan-4711]

I have the same problem.
I updated my LXCs and now nginx isn't starting any more.
nginx.service: Can't open PID file /run/nginx.pid (yet?) after start: No such file or directory

I just installed nginx last week, don't know which version it was excatly

[LoaneShark]

Hi, I have the same issue. I was going from nginx-proxy-manager-2.9.18 to nginx-proxy-manager-2.10.4.
It seems like my cert files are missing? Or looking in the wrong place at least.

Here's my output from trying to start the openresty service manually, which appears to be where the error is getting thrown specifically.

Nov 30 22:31:16 nginx systemd[1]: Starting The OpenResty Application Platform...
Nov 30 22:31:16 nginx nginx[4084]: nginx: [warn] low address bits of 192.168.1.1/8 are meaningless in /data/nginx/proxy_host/16.conf:50
Nov 30 22:31:17 nginx nginx[4084]: nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-26/fullchain.pem": BIO_new_file() failed (SSL: error:0>
Nov 30 22:31:17 nginx nginx[4084]: nginx: configuration file /usr/local/openresty/nginx/conf/nginx.conf test failed
Nov 30 22:31:17 nginx systemd[1]: openresty.service: Control process exited, code=exited, status=1/FAILURE
Nov 30 22:31:17 nginx systemd[1]: openresty.service: Failed with result 'exit-code'.
Nov 30 22:31:17 nginx systemd[1]: Failed to start The OpenResty Application Platform.

Here's the subdirectories that actually exist in the folder it's searching in:

root@nginx:~# ls -lh /etc/letsencrypt/live/
total 12K
-rwxr-xr-x 1 root root  740 Mar 28  2022 README
drwxr-xr-x 2 root root 4.0K Apr 10  2022 npm-2
drwxr-xr-x 2 root root 4.0K Nov 24 09:10 npm-50