Checklist
- Have you pulled and found the error with
jc21/nginx-proxy-manager:latest docker image?
- Are you sure you're not using someone else's docker image?
- Have you searched for similar issues (both open and closed)?
Describe the bug
Hetzner has switched to a new URL. Atm its nots possible to renew certs. Its already fixed in the latest certbot version. This is the bug URL: bunkerity/bunkerweb#3526
Nginx Proxy Manager Version
latest just pulled today v2.14.0
To Reproduce
Steps to reproduce the behavior:
- Go to certificates tab
- Click on check hetzner certs and see that renewal does not work. you can also click on the three dts and renew but you only get an intern error. In the logs you can the this:
[5/29/2026] [10:32:16 AM] [Remote Version] › ℹ info Fetching https://api.github.com/repos/NginxProxyManager/nginx-proxy-manager/releases/latest
^[[A
[5/29/2026] [10:36:43 AM] [SSL ] › ℹ info Renewing LetsEncrypt certificates via Hetzner for Cert #62: *.it..domain.com
[5/29/2026] [10:36:43 AM] [SSL ] › ℹ info Command: certbot renew --force-renewal --config /etc/letsencrypt.ini --work-dir /tmp/letsencrypt-lib --logs-dir /data/logs --cert-name npm-62 --preferred-challenges dns --disable-hook-validation --no-random-sleep-on-renew
[5/29/2026] [10:36:46 AM] [Express ] › ⚠ warning Saving debug log to /data/logs/letsencrypt.log
Encountered exception during recovery: certbot_dns_hetzner.hetzner_client._MalformedResponseException: Received an unexpected response from Hetzner API:
Expecting value: line 1 column 1 (char 0)
Failed to renew certificate npm-62 with error: Received an unexpected response from Hetzner API:
Expecting value: line 1 column 1 (char 0)
All renewals failed. The following certificates could not be renewed:
/etc/letsencrypt/live/npm-62/fullchain.pem (failure)
1 renew failure(s), 0 parse failure(s)
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /data/logs/letsencrypt.log or re-run Certbot with -v for more details.
Expected behavior
Screenshots
Operating System
ubuntu24
Additional context
Checklist
jc21/nginx-proxy-manager:latestdocker image?Describe the bug
Hetzner has switched to a new URL. Atm its nots possible to renew certs. Its already fixed in the latest certbot version. This is the bug URL: bunkerity/bunkerweb#3526
Nginx Proxy Manager Version
latest just pulled today v2.14.0
To Reproduce
Steps to reproduce the behavior:
[5/29/2026] [10:32:16 AM] [Remote Version] › ℹ info Fetching https://api.github.com/repos/NginxProxyManager/nginx-proxy-manager/releases/latest
^[[A
[5/29/2026] [10:36:43 AM] [SSL ] › ℹ info Renewing LetsEncrypt certificates via Hetzner for Cert #62: *.it..domain.com
[5/29/2026] [10:36:43 AM] [SSL ] › ℹ info Command: certbot renew --force-renewal --config /etc/letsencrypt.ini --work-dir /tmp/letsencrypt-lib --logs-dir /data/logs --cert-name npm-62 --preferred-challenges dns --disable-hook-validation --no-random-sleep-on-renew
[5/29/2026] [10:36:46 AM] [Express ] › ⚠ warning Saving debug log to /data/logs/letsencrypt.log
Encountered exception during recovery: certbot_dns_hetzner.hetzner_client._MalformedResponseException: Received an unexpected response from Hetzner API:
Expecting value: line 1 column 1 (char 0)
Failed to renew certificate npm-62 with error: Received an unexpected response from Hetzner API:
Expecting value: line 1 column 1 (char 0)
All renewals failed. The following certificates could not be renewed:
/etc/letsencrypt/live/npm-62/fullchain.pem (failure)
1 renew failure(s), 0 parse failure(s)
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /data/logs/letsencrypt.log or re-run Certbot with -v for more details.
Expected behavior
Screenshots
Operating System
ubuntu24
Additional context