Nginx Proxy Manager 2.17.1 upgrade: Certbot 5 warning, clean test
Summary
2.17.1 is a small release. It uses a new base OpenResty image (1.31.8.1) with backported fixes from nginx2root. It fixes a bug where SSL toggles reset to off when you request a new certificate while creating a host. It also moves nginx variables into their own include file and brings back the forward_host variable. The bundled Certbot is 5.10.0.
Breaking changes and deprecations
Reported by the project: the release notes warn that Certbot has been updated. DNS plugins may not work as expected and may need tweaks to their dependencies. See the Certbot docs.
Nothing else is listed as breaking.
Tested in our lab
We started 2.17.0 with the standard Docker Compose setup (data and letsencrypt volumes). We created an admin user and one proxy host, and confirmed the proxy answered. Then we ran docker compose down, changed the tag to 2.17.1, pulled it and started it again.
Results after the upgrade:
- The container came up and the API reported version 2.17.1.
- The admin user could still log in, and the proxy host was still there.
- The proxy host still answered with HTTP 200.
nginx -tpassed, and Certbot in the container reported 5.10.0.- The logs showed only two warnings, and the 2.17.0 logs showed the same two: an s6 deprecation message and a
useraddUID message.
Not tested: requesting certificates (HTTP or DNS challenge), DNS provider plugins, the SSL toggle fix, and custom nginx configs that use the moved variables. We tested no custom configs, so we can’t say whether the include file move affects them.
Lab log
$ docker compose down
[...]
Network npm_default Removed
$ docker compose pull
[...]
app Pulled
$ docker compose up -d
[...]
Container npm-app-1 Started
$ docker compose ps
NAME IMAGE COMMAND SERVICE CREATED STATUS PORTS
npm-app-1 jc21/nginx-proxy-manager:2.17.1 "/init" app 47 seconds ago Up 45 seconds 0.0.0.0:80-81->80-81/tcp, [::]:80-81->80-81/tcp, 0.0.0.0:443->443/tcp, [::]:443->443/tcp
$ curl -s localhost:81/api/
{"status":"OK","setup":true,"version":{"major":2,"minor":17,"revision":1}}
$ curl -s -o /dev/null -w "%{http_code}\n" -H "Host: test.example.com" localhost/
200
$ docker exec npm-app-1 nginx -t
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
$ docker exec npm-app-1 certbot --version
certbot 5.10.0
Reported by others
We did not look for community reports. The only outside source is the release notes, which warn about Certbot and DNS plugins.
Verdict
Wait if you rely on DNS challenge certificates, until you have checked the Certbot docs for your plugin. Back up data and letsencrypt first. If you only use HTTP validation or no certificates, the upgrade was uneventful in our test.