⬆️ Update NginxProxyManager/nginx-proxy-manager to v2.12.1

[renovate]

This PR contains the following updates:

Package	Update	Change
NginxProxyManager/nginx-proxy-manager	minor	v2.10.4 -> v2.12.1

---

Release Notes

NginxProxyManager/nginx-proxy-manager (NginxProxyManager/nginx-proxy-manager)

v2.12.1

Compare Source

Changes

• Fixes saving default site settings and auto scheme redirects (thanks @​Nephiel)
• Adds test suite for settings
• Some schema fixes

Docker images

• jc21/nginx-proxy-manager:latest
• jc21/nginx-proxy-manager:2
• jc21/nginx-proxy-manager:2.12.1

v2.12.0

Compare Source

Important: Back up your entire instance before using this new version! As with any new version, there may be breaking changes.

1. Bring your docker instance down
2. Zip or copy your data and letsencrypt folders
3. Pull this new image jc21/nginx-proxy-manager:2.11.3
4. Bring up your docker stack and check for any problems in the logs
5. Renew your DNS certs manually
6. Check some or all of your hosts for expected behaviour

Changes

• Fix CVE-2024-46256 and CVE-2024-46257
• Reworked API Schema and validation, full openapi/swagger spec can be fetched from /api/schema endpoint
• ⚠️ Boolean fields in API responses are actual booleans now, not 0/1
• API correctly returns 404 for operations on incorrect objects
• Vastly improved API Cypress test suite, spins up local acme server for DNS certificate testing
• Updated security deps
• Add mijn.host dns plugin (thanks @​RafaelSchridi)
• Added active24 DNS provider (thanks @​vggscqq)
• swap mysql library and knex client for mysql2 (thanks @​nlynzaad)
• Add set directives for proxied paths to keep nginx from crashing if upstream is down (thanks @​ddshd)
• Fix app not restarting after log rotate (thanks @​cqhtyi)
• Add rockenstein AG DNS Plugin (thanks @​rag-franky)
• Add Edge DNS by Akamai (thanks @​egobude)
• fixed wedos password description (thanks @​Hadatko)

Docker images

• jc21/nginx-proxy-manager:latest
• jc21/nginx-proxy-manager:2
• jc21/nginx-proxy-manager:2.12.0

Should you encounter problems, use the docker tag 2.11.3 to downgrade.

v2.11.3

Compare Source

Important: Back up your entire instance before using this new version! As with any new version, there may be breaking changes.

1. Bring your docker instance down
2. Zip or copy your data and letsencrypt folders
3. Pull this new image jc21/nginx-proxy-manager:2.11.3
4. Bring up your docker stack and check for any problems in the logs
5. Renew your DNS certs manually
6. Check some or all of your hosts for expected behaviour

Changes

• #​3764 Fix Cloudflare DNS Auth (thanks @​ransbachm)
• #​3729 Move advanced_config section to top of default config (thanks @​clhey)
• #​3815 Add Hover.com DNS plugin (thanks @​alexjsp)
• #​3810 Changing log_format proxy default location (thanks @​Brendon-Mendicino)
• #​3843 Fix syntax that causes errors (generateKeys log) (thanks @​jay-lab)
• #​3790 Read initial admin email and password from env vars (thanks @​DavidLievrouw)
• #​3781 Remove spaces around Cloudflare API Credential (thanks @​jinhei)
• #​3766 Add include for root_top.conf in the nginx.conf (thanks @​kroegerama)
• #​3662 Fix command injection when passing bash commands into the DNS provider config (thanks @​IgorDuino)

Docker images

• jc21/nginx-proxy-manager:latest
• jc21/nginx-proxy-manager:2
• jc21/nginx-proxy-manager:2.11.3

v2.11.2

Compare Source

Important: Back up your entire instance before using this new version! As with any new version, there may be breaking changes.

1. Bring your docker instance down
2. Zip or copy your data and letsencrypt folders
3. Pull this new image jc21/nginx-proxy-manager:2.11.2
4. Bring up your docker stack and check for any problems in the logs
5. Renew your DNS certs manually
6. Check some or all of your hosts for expected behaviour

Changes

• Update certbot-dns-infomaniak (thanks @​Fuechslein)
• update certbot-dns-strato to latest version (thanks @​jdolderer)
• Add DNS multi (thanks @​starsoccer)
• update certbot-dns-transip to latest version (thanks @​leinelissen)
• Update certbot-dns-goddaddy (thanks @​wolviex)
• replaced chown with find -not -user -execdir chown (thanks @​woodmichl)
• Update certbot-dns-duckdns version (thanks @​sdaqo)
• Access-List fix so that nginx config is loaded after configuration happens (thanks @​timob)
• Update README.md to support Podman (thanks @​michto01)
• Fix: increase max number of domains to 100 (match with Let's Encrypt) (thanks @​davidindra)
• Adding easyDNS provider (thanks @​drachul)
• Add FreeDNS certbot plugin (thanks @​bricas)
• Add DNS Provider TimeWeb Cloud (thanks @​hywax)
• Updated certbot-dns-websupport plugin to 2.0.1 (thanks @​setrin)

Docker images

• jc21/nginx-proxy-manager:latest
• jc21/nginx-proxy-manager:2
• jc21/nginx-proxy-manager:2.11.2

v2.11.1

Compare Source

Important: Back up your entire instance before using this new version! As with any new version, there may be breaking changes.

1. Bring your docker instance down
2. Zip or copy your data and letsencrypt folders
3. Pull this new image jc21/nginx-proxy-manager:2.11.1
4. Bring up your docker stack and check for any problems in the logs
5. Renew your DNS certs manually
6. Check some or all of your hosts for expected behaviour

Changes

• Fix startup hanging for instances where there are SSL certs but none of them are DNS challenges

Docker images

• jc21/nginx-proxy-manager:latest
• jc21/nginx-proxy-manager:2
• jc21/nginx-proxy-manager:2.11.1

v2.11.0

Compare Source

Important: Back up your entire instance before using this new version! As with any new version, there may be breaking changes.

1. Bring your docker instance down
2. Zip or copy your data and letsencrypt folders
3. Pull this new image jc21/nginx-proxy-manager:2.11.0
4. Bring up your docker stack and check for any problems in the logs
5. Renew your DNS certs manually
6. Check some or all of your hosts for expected behaviour

Changes

• Use nginxproxymanager/nginx-full image base #​3444
  • debian bookworm
  • python v3.11
  • certbot v2.8.0
• Refactor certbot plugins install, updated some plugins, remove packages that don't exist anymore
• Update mariadb example to auto upgrade from latest image
• @​FibreTTP: Make logrotate use the proper user and group #​3219
• @​AngusC222: minimum/maximum ports added on frontend #​3188
• @​benhubert: added support for dns.he.net certbot plugin #​2153
• @​devedse: Added force renewal + --dns-duckdns-no-txt-restore #​3155
• @​OpenSourceSimon: Add robots noindex meta tag to prevent indexing #​3190
• @​zhzy0077: certbot-dns-tencentcloud should be 2.0.2 or above. #​3194
• @​FlixMa: Strato Certbot Plugin: 2FA and International Site Support #​3212
• @​xiaoxinpro: Replace the description string on the default-site page with i18n #​3293
• @​AngusC222: min/max ports added for Streams #​3312
• @​jlesage: Fixed issue where the HTTP2 support was always enabled in nginx config #​3377
• @​r3na: fix: increasing maxOptions (amount of domains) to 30 #​3382
• @​clord: bump version of vultr certbot #​3387
• @​jlesage: Fixes for the server reachability test #​3388
• @​JeremieA: Update certbot-dns-plugins.js for gandi #​3401
• @​arussell: Add support for certbot-dns-plesk #​3408
• @​Encephala: Add documentation on customising logrotate config #​3422
• @​Encephala: Update year to 2024 in footer #​3427
• @​DarioViva42: only add hsts header with https. #​3360
• @​timob: Improve container startup time #​3361
• @​Encephala: Fix typo in logrotate config path #​3437
• @​ej52: update Proxmox Scripts link #​3367
• @​benhubert: added support for dns.he.net certbot plugin #​2153 #​2924
• @​tilalx: Update the vuepress config.js to fix #​3395 #​3445
• @​tilalx: upgrade docs to vuepress v2.0.0-rc and implement dark mode #​3395
• @​stevecrozz: Make auto-renew use built-in renew function #​3392
• @​existful: certbot-dns-cloudns update 0.6.0 #​3459
• @​iBobik: Removed /etc/letsencrypt from explicit volumes #​3258

Docker images

• jc21/nginx-proxy-manager:latest
• jc21/nginx-proxy-manager:2
• jc21/nginx-proxy-manager:2.11.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  -- I pushed a fix in commit <commit_id>, please review it.
  -- Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  -- @coderabbitai generate unit testing code for this file.
  -- @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  -- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  -- @coderabbitai read src/utils.ts and generate unit testing code.
  -- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  -- @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[gigatexel]

Could this be merged? Might fix this issue that is still persistent: #513

[poiromaniax]

This will also remediate #579

[bjwo]

Hi @frenck - is there anything that we as users can do to validate this PR? Especially for security-relevant components like NGINX I feel it would be vital to have a robust process in place that allows to upgrade to the latest upstream release in a timely manner. Many thanks.

[Super1337Boy]

Hopefully this pull request can be merged soon. It supposedly fixes this issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1189

[Cutriss]

I'm probably wrong but it looks like this is a series of dependency failures on renovate upgrades that are hinging on switching/updating alpine builds. So it's not just a matter of approving the merge?

[gigatexel]

I'm probably wrong but it looks like this is a series of dependency failures on renovate upgrades that are hinging on switching/updating alpine builds. So it's not just a matter of approving the merge?

Yes, but only @frenck can merge

[ARandomGitHubUser]

@frenck Could we please get some priority on this, as GHSA-mhxx-5693-798f (9.8 severity) and GHSA-5rqg-4vpc-fpm2 (6.3 severity) were just fixed in Nginx Proxy Manager v2.12.0 🙂