Nginx Proxy Manager 2.17.0 upgrade: Certbot breaking changes
Summary
2.17.0 updates OpenResty (1.31.8.1), Certbot (5.9.0) and s6-overlay (3.2.3.2). It adds a Scaleway DNS plugin and updates several other DNS plugins. It also includes security fixes: rate limiting on auth endpoints, authentication required to validate certificates, and certificate_key no longer returned in certificate API responses. The dark mode colours change because of a Tabler theme update.
Breaking changes and deprecations
Reported by the release notes:
- Certbot was updated. The notes say your DNS plugins may not work as expected and may need dependency tweaks. See the Certbot doc.
- The Akamai EdgeDNS, Beget and Infomaniak DNS plugins have breaking changes. The notes suggest creating new DNS certificates with these providers and removing the old ones.
- Dark mode looks different.
Tested in our lab
We upgraded from 2.16.0 to 2.17.0 with Docker Compose and the default SQLite setup. Before the upgrade we created an admin user and one proxy host. We stopped the container with docker compose down, changed the image tag, pulled and started it again.
- The API reported version 2.17.0 after the upgrade.
- Login worked with the existing admin account.
- The proxy host was still there, and nginx still answered for it with HTTP 200.
- The container was up after the upgrade.
- The logs had two warnings, about s6-overlay user bundles and a
useraddUID range. We did not check whether 2.16.0 printed them too.
We did not test any DNS challenge certificates, Let’s Encrypt issuance, or the Akamai, Beget or Infomaniak plugins. The Certbot warning is therefore untested here.
Lab log
$ curl -s localhost:81/api/
{"status":"OK","setup":false,"version":{"major":2,"minor":16,"revision":0}}
$ docker compose down
[...]
Container npm-app-1 Removed
$ docker compose pull
[...]
Image jc21/nginx-proxy-manager:2.17.0 Pulled
$ docker compose up -d
[...]
Container npm-app-1 Started
$ curl -s localhost:81/api/
{"status":"OK","setup":true,"version":{"major":2,"minor":17,"revision":0}}
$ curl -s -H "Authorization: Bearer [redacted]" localhost:81/api/nginx/proxy-hosts
[{"id":1,"created_on":"2026-11-12 08:32:45","modified_on":"2026-11-12 08:32:46","owner_user_id":1,"domain_names":["test.example.com"],"forward_host":"127.0.0.1","forward_port":81,[...]
$ curl -s -H "Host: test.example.com" -o /dev/null -w "%{http_code}\n" localhost:80/
200
$ docker compose ps --format "{{.Status}}"
Up 50 seconds
Reported by others
Nothing beyond the release notes. We did not review issue reports.
Verdict
Wait if you use DNS challenge certificates, especially with Akamai EdgeDNS, Beget or Infomaniak. Read the Certbot doc first and back up data and letsencrypt. If you only use HTTP validation or no certificates, the upgrade was clean in our test, and the security fixes are a good reason to move.