Nginx Proxy Manager 2.12.4 – Multiple Issues and Unresolved DNS Failure (Rollback Required)

Apps and Virtualization
21

For those that can’t roll back, for whatever reason, I was able to patch my docker-compose.yaml file to use a previous image.

  1. Verify that you have jc21/nginx-proxy-manager:2.12.3 downloaded in your docker images list. This can be done with a docker images | grep nginx
  2. Locate the docker-compose.yaml file. For me, it was located in /mnt/.ix-apps/app_configs/nginx-proxy-manager/versions/1.2.5/templates/rendered
  3. This file is weirdly formatted. Leave it alone. Just find and change the image version from 2.12.4 to 2.12.3.
  4. Save, close and restart your app from the gui.
1 Like
22

Cool, that will be helpful for some people who don’t seem to have ever installed the previous version.

On the introduced bugs subject in general there is a lot of discussion on the NginxProxyManager github, It’s all a lot of head scratching if you ask me.To many different problems & different solutions :confounded:

I hope they fix it :frowning:

1 Like
23

Ok so it looks like NPM is all patched up and after 2.12.6 should be working again.

I was just wondering how long it takes before the upstream will get to the app update on Scale? Mine is still at 2.12.4 ATM?

24

I am wondering this too as the Apps Market page says that it was updated 09.07.2025. I have been watching this issue unfold from Tuesday and the app version hasn’t even updated to 2.12.5…

25

Ok 2.12.6 is available now, and it works for me with the SKIP_CERTBOT_OWNERSHIP true set.

2 Likes
26

The same here. I also removed the S6_STAGE2_HOOK set to sed -i $d /etc/s6-overlay/s6-rc.d/prepare/30-ownership.sh.

2 Likes
27

Confirmed, 1.2.6 is the current available to me. Updated, and while it still takes its sweet time starting up, it will eventually deploy and run with cloudflare stuff inside. 3 patches later, so anyone waiting this one out I think it’s safe now.

1 Like
28

Just an update - jumped from v2.12.3 (working) to v2.12.6 (same issue, stuck deploying with below logs)… just updating to v2.12.6 didn’t fix it, though. Still getting:

2025-07-16 11:07:28.881201+00:00/etc/s6-overlay/s6-rc.d/prepare/30-ownership.sh: line 60: syntax error: unexpected end of file
2025-07-16 11:07:28.881415+00:00s6-rc: warning: unable to start service prepare: command exited 2
2025-07-16 11:07:28.881503+00:00/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.

To fix it, I had to do both of the below steps:

  1. Deleting the S6_STAGE2_HOOK environment variable that was set to sed -i $d /etc/s6-overlay/s6-rc.d/prepare/30-ownership.sh → within the TrueNAS GUI app config.
  2. Setting SKIP_CERTBOT_OWNERSHIP to true → within the TrueNAS GUI app config.

Thanks for the above users for their help! Hopefully a future releases don’t have this issue… does anyone know the implications of not using the 30-ownership.sh script long term? Just curious as I presume that it’s part of the deployment/spinup process for a reason…

2 Likes
29

This worked for me. I’m concerned if there are any unintended consequences from applying this setting.