[GH-ISSUE #4355] Failed to renew certificate with error: The requested certbot-dns-netcup:dns-netcup plugin does not appear to be installed #2795

Closed
opened 2026-02-26 07:36:48 +03:00 by kerem · 1 comment
Owner

Originally created by @zawnk on GitHub (Feb 7, 2025).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4355

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
After a bit of struggling I just updated from 2.9.4 to 2.12.3 and everything seems to work fine so far. The only issue I've had is that if I run the renew command, it tells me that the netcup plugin is not installed. It expires in a long time and is not due for renewal yet, so I assume before updating today it still worked.

When I click to renew, the log prints the following:

[2/7/2025] [7:56:47 PM] [SSL      ] › ℹ  info      Renewing Let'sEncrypt certificates via netcup for Cert #6: *.domain.de, domain.de

[2/7/2025] [7:56:47 PM] [SSL      ] › ℹ  info      Command: certbot renew --force-renewal --config "/etc/letsencrypt.ini" --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name 'npm-6' --disable-hook-validation --no-random-sleep-on-renew 

[2/7/2025] [7:56:47 PM] [Global   ] › ⬤  debug     CMD: certbot renew --force-renewal --config "/etc/letsencrypt.ini" --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name 'npm-6' --disable-hook-validation --no-random-sleep-on-renew 

[2/7/2025] [7:56:48 PM] [Express  ] › ⚠  warning   Saving debug log to /tmp/letsencrypt-log/letsencrypt.log

Failed to renew certificate npm-6 with error: The requested certbot-dns-netcup:dns-netcup plugin does not appear to be installed

All renewals failed. The following certificates could not be renewed:
  /etc/letsencrypt/live/npm-6/fullchain.pem (failure)
1 renew failure(s), 0 parse failure(s)

To Reproduce
Steps to reproduce the behavior:

  1. Go to the web ui
  2. Click on SSL certificates
  3. Click the dropdown
  4. Click Renew Now
  5. Internal Error is shown

Expected behavior
Renewing the cert or telling me it's not due for renewal yet and no error in the log

Screenshots
n/a

Operating System
NPM in a docker container with docker compose and MariaDB

Interestingly, when starting the container, there's this in the logs that all seems to work fine:

[2/7/2025] [7:49:27 PM] [Global   ] › ⬤  debug     CMD: [ -f '/etc/letsencrypt/credentials/credentials-6' ] || { mkdir -p /etc/letsencrypt/credentials 2> /dev/null; echo 'certbot_dns_netcup:dns_netcup_customer_id=XXXXXXX
certbot_dns_netcup:dns_netcup_api_key=XXXXXXXXXX
certbot_dns_netcup:dns_netcup_api_password=XXXXXXXX' > '/etc/letsencrypt/credentials/credentials-6' && chmod 600 '/etc/letsencrypt/credentials/credentials-6'; }

[2/7/2025] [7:49:27 PM] [Certbot  ] › ▶  start     Installing netcup...

[2/7/2025] [7:49:27 PM] [Global   ] › ⬤  debug     CMD: . /opt/certbot/bin/activate && pip install --no-cache-dir  certbot-dns-netcup~=1.0.0  && deactivate

[2/7/2025] [7:49:28 PM] [Certbot  ] › ☒  complete  Installed netcup

[2/7/2025] [7:49:28 PM] [Setup    ] › ℹ  info      Added Certbot plugins netcup
Originally created by @zawnk on GitHub (Feb 7, 2025). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4355 **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** After a bit of struggling I just updated from 2.9.4 to 2.12.3 and everything seems to work fine so far. The only issue I've had is that if I run the renew command, it tells me that the netcup plugin is not installed. It expires in a long time and is not due for renewal yet, so I assume before updating today it still worked. When I click to renew, the log prints the following: ``` [2/7/2025] [7:56:47 PM] [SSL ] › ℹ info Renewing Let'sEncrypt certificates via netcup for Cert #6: *.domain.de, domain.de [2/7/2025] [7:56:47 PM] [SSL ] › ℹ info Command: certbot renew --force-renewal --config "/etc/letsencrypt.ini" --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name 'npm-6' --disable-hook-validation --no-random-sleep-on-renew [2/7/2025] [7:56:47 PM] [Global ] › ⬤ debug CMD: certbot renew --force-renewal --config "/etc/letsencrypt.ini" --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name 'npm-6' --disable-hook-validation --no-random-sleep-on-renew [2/7/2025] [7:56:48 PM] [Express ] › ⚠ warning Saving debug log to /tmp/letsencrypt-log/letsencrypt.log Failed to renew certificate npm-6 with error: The requested certbot-dns-netcup:dns-netcup plugin does not appear to be installed All renewals failed. The following certificates could not be renewed: /etc/letsencrypt/live/npm-6/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) ``` **To Reproduce** Steps to reproduce the behavior: 1. Go to the web ui 2. Click on SSL certificates 3. Click the dropdown 4. Click Renew Now 5. Internal Error is shown **Expected behavior** Renewing the cert or telling me it's not due for renewal yet and no error in the log **Screenshots** n/a **Operating System** NPM in a docker container with docker compose and MariaDB Interestingly, when starting the container, there's this in the logs that all seems to work fine: ``` [2/7/2025] [7:49:27 PM] [Global ] › ⬤ debug CMD: [ -f '/etc/letsencrypt/credentials/credentials-6' ] || { mkdir -p /etc/letsencrypt/credentials 2> /dev/null; echo 'certbot_dns_netcup:dns_netcup_customer_id=XXXXXXX certbot_dns_netcup:dns_netcup_api_key=XXXXXXXXXX certbot_dns_netcup:dns_netcup_api_password=XXXXXXXX' > '/etc/letsencrypt/credentials/credentials-6' && chmod 600 '/etc/letsencrypt/credentials/credentials-6'; } [2/7/2025] [7:49:27 PM] [Certbot ] › ▶ start Installing netcup... [2/7/2025] [7:49:27 PM] [Global ] › ⬤ debug CMD: . /opt/certbot/bin/activate && pip install --no-cache-dir certbot-dns-netcup~=1.0.0 && deactivate [2/7/2025] [7:49:28 PM] [Certbot ] › ☒ complete Installed netcup [2/7/2025] [7:49:28 PM] [Setup ] › ℹ info Added Certbot plugins netcup ```
kerem 2026-02-26 07:36:48 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@zawnk commented on GitHub (Feb 7, 2025):

Solved it with the help of the netcup dns repo. The naming got adjusted in the meanwhile (should this have been handled automatically?). So in my renew configuration I needed to replace the info before the colon (the plugin name). And the settings got renamed, so the underscored had to be replaced with regular hyphens. Now everything works again :)

<!-- gh-comment-id:2644160822 --> @zawnk commented on GitHub (Feb 7, 2025): Solved it with the help of the netcup dns repo. The naming got adjusted in the meanwhile (should this have been handled automatically?). So in my renew configuration I needed to replace the info before the colon (the plugin name). And the settings got renamed, so the underscored had to be replaced with regular hyphens. Now everything works again :)
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#2795
No description provided.