[GH-ISSUE #1525] Issue with latest certbot implementation and previous certificates #1163

Closed
opened 2026-02-26 06:36:01 +03:00 by kerem · 2 comments
Owner

Originally created by @mora-phi on GitHub (Oct 27, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1525

Checklist

  • Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
    • Yes
  • Are you sure you're not using someone else's docker image?
    • Yes
  • Have you searched for similar issues (both open and closed)?
    • Yes

Describe the bug
Since latest update (2.9.10), some previous certbot implementation has been broken :
'Namespace' object has no attribute 'dns_ovh_credentials'
Indeed, the field in the letsencrypt/renewal/npm-2.conf (in my case there is a "-2" suffix) has no prefix and is now called "credentials" instead of "dns_ovh_credentials".
A manual updates solves this issue.

Nginx Proxy Manager Version
2.9.10

To Reproduce
Steps to reproduce the behavior:

  1. Have a previous certificate (I saw the problem with ovh) with a previous version of NPM.
    The line in the certificate renewal should be something like :
    dns_ovh_credentials = /etc/letsencrypt/credentials/credentials-2
  2. Update the version of NPM
  3. Certbot renewal should fail with 'Namespace' object has no attribute 'dns_ovh_credentials'

Expected behavior
Correct certificate renewal.
If fields names in files have been modified, they should be upgraded when new NPM starts... Or a "Breaking warning" should be displayed on the release page.

Operating System
Linux alpine 5.10.61-0-lts #1-Alpine SMP Fri, 27 Aug 2021 05:29:55 +0000 x86_64 Linux
Docker version 20.10.7, build f0df35096d5f5e6b559b42c7fde6c65a2909f7c5

Originally created by @mora-phi on GitHub (Oct 27, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1525 **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? - Yes - Are you sure you're not using someone else's docker image? - Yes - Have you searched for similar issues (both open and closed)? - Yes **Describe the bug** Since latest update (2.9.10), some previous certbot implementation has been broken : 'Namespace' object has no attribute 'dns_ovh_credentials' Indeed, the field in the letsencrypt/renewal/npm-2.conf (in my case there is a "-2" suffix) has no prefix and is now called "credentials" instead of "dns_ovh_credentials". A manual updates solves this issue. **Nginx Proxy Manager Version** 2.9.10 **To Reproduce** Steps to reproduce the behavior: 1. Have a previous certificate (I saw the problem with ovh) with a previous version of NPM. The line in the certificate renewal should be something like : dns_ovh_credentials = /etc/letsencrypt/credentials/credentials-2 2. Update the version of NPM 3. Certbot renewal should fail with 'Namespace' object has no attribute 'dns_ovh_credentials' **Expected behavior** Correct certificate renewal. If fields names in files have been modified, they should be upgraded when new NPM starts... Or a "Breaking warning" should be displayed on the release page. **Operating System** Linux alpine 5.10.61-0-lts #1-Alpine SMP Fri, 27 Aug 2021 05:29:55 +0000 x86_64 Linux Docker version 20.10.7, build f0df35096d5f5e6b559b42c7fde6c65a2909f7c5
kerem 2026-02-26 06:36:01 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@chaptergy commented on GitHub (Nov 1, 2021):

The namespaces are deprecated in certbot for a while now and that's why they have been removed. It sounds like certbot is still on an old version in your container. Could you please run

certbot --version

inside your container to seen what version you have installed? If you don't have version 1.19 or 1.20 please provide a list of other dns providers you are using, one of them could cause certbot to downgrade.

<!-- gh-comment-id:956018343 --> @chaptergy commented on GitHub (Nov 1, 2021): The namespaces are deprecated in certbot for a while now and that's why they have been removed. It sounds like certbot is still on an old version in your container. Could you please run ``` certbot --version ``` inside your container to seen what version you have installed? If you don't have version `1.19` or `1.20` please provide a list of other dns providers you are using, one of them could cause certbot to downgrade.
Author
Owner

@mora-phi commented on GitHub (Nov 3, 2021):

Hi,
If it has been deprecated a while it's weird I haven't had the problem before, because all my containers are automatically updated using watchtower...
I have now updated and my certbot version inside the container is "certbot 1.20.0"
I close the issue, as I have manually updated my credentials file to remove the prefix : I just wanted to open it in case it could help anyone else.
Thanks.

<!-- gh-comment-id:958803773 --> @mora-phi commented on GitHub (Nov 3, 2021): Hi, If it has been deprecated a while it's weird I haven't had the problem before, because all my containers are automatically updated using watchtower... I have now updated and my certbot version inside the container is "certbot 1.20.0" I close the issue, as I have manually updated my credentials file to remove the prefix : I just wanted to open it in case it could help anyone else. Thanks.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#1163
No description provided.