Skip to content

Fix Tencent Cloud apex and wildcard certificate issuance - #5795

Open
xzy103 wants to merge 1 commit into
NginxProxyManager:developfrom
xzy103:fix/tencentcloud-dns-apex-wildcard
Open

Fix Tencent Cloud apex and wildcard certificate issuance#5795
xzy103 wants to merge 1 commit into
NginxProxyManager:developfrom
xzy103:fix/tencentcloud-dns-apex-wildcard

Conversation

@xzy103

@xzy103 xzy103 commented Aug 22, 2026

Copy link
Copy Markdown

Why

Nginx Proxy Manager v2.15.1 currently installs certbot-dns-tencentcloud~=2.0.2.

This version fails when requesting a certificate that combines an apex domain and its wildcard domain.

Upgrading certbot-dns-tencentcloud to 2.1.1 fixes the issue. The upstream changelog specifically mentions fixing TXT record cleanup for combined apex and wildcard certificates: https://github.com/Frefreak/certbot-dns-tencentcloud/blob/master/CHANGELOG.md#211

Version 2.1.1 is available on PyPI: https://pypi.org/project/certbot-dns-tencentcloud/2.1.1/

Changes

Update the Tencent Cloud DNS plugin requirement from:

certbot-dns-tencentcloud~=2.0.2

to:

certbot-dns-tencentcloud~=2.1.1

Verification

  • Confirmed that dns-plugins.json remains valid JSON.
  • Confirmed that the change only affects the Tencent Cloud plugin version.
  • Reproduced the failure with Nginx Proxy Manager v2.15.1 and
    certbot-dns-tencentcloud 2.0.2.
  • Manually upgraded the plugin to 2.1.1 in the same container.
  • Successfully requested a certificate containing both the apex domain
    and wildcard domain after the upgrade.

Type of Change

  • Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update
  • Code refactoring
  • API changes
  • Performance improvement
  • Test addition or update

AI Usage

  • AI was used to write this
  • AI was used to review this

@nginxproxymanagerci

Copy link
Copy Markdown

Docker Image for build 1 is available on DockerHub:

nginxproxymanager/nginx-proxy-manager-dev:pr-5795

Note

Ensure you backup your NPM instance before testing this image! Especially if there are database changes.
This is a different docker image namespace than the official image.

Warning

Changes and additions to DNS Providers require verification by at least 2 members of the community!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant