starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 01:15:51 +03:00

[GH-ISSUE #1741] Certificate renewal doen't work, DNS Challange - ClouDNS #1295

New issue

Closed

opened 2026-02-26 06:36:37 +03:00 by kerem · 3 comments

kerem commented

2026-02-26 06:36:37 +03:00

Owner

Originally created by @poiNt3D on GitHub (Jan 9, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1741

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
I have set up DNS-Challange renewal for my wildcard domain. Provider is ClouDNS. API is enabled on my accound. The entry was added successfully, without errors. When i try to renew it, popup window spins and closes, no errors and the certificate does not update.
Here's the meta field from my database (redacted):

{
    "letsencrypt_email": "myemail@example.com",
    "dns_challenge": true,
    "dns_provider": "cloudns",
    "dns_provider_credentials": "# Target user ID (see https://www.cloudns.net/api-settings/)\r\n\t
	dns_cloudns_auth_id=myuserid\r\n\t#
	Alternatively, one of the following two options can be set:\r\n\t#
	dns_cloudns_sub_auth_id=1234\r\n\t# dns_cloudns_sub_auth_user=foobar \r\n\t\r\n\t# API password\r\n\tdns_cloudns_auth_password=mypassword",
    "propagation_seconds": 999,
    "letsencrypt_agree": true
}

Nginx Proxy Manager Version
v2.9.14

Expected behavior
Some log output would be nice.

Originally created by @poiNt3D on GitHub (Jan 9, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1741 **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** I have set up DNS-Challange renewal for my wildcard domain. Provider is ClouDNS. API is enabled on my accound. The entry was added successfully, without errors. When i try to renew it, popup window spins and closes, no errors and the certificate does not update. Here's the meta field from my database (redacted): ``` { "letsencrypt_email": "myemail@example.com", "dns_challenge": true, "dns_provider": "cloudns", "dns_provider_credentials": "# Target user ID (see https://www.cloudns.net/api-settings/)\r\n\t dns_cloudns_auth_id=myuserid\r\n\t# Alternatively, one of the following two options can be set:\r\n\t# dns_cloudns_sub_auth_id=1234\r\n\t# dns_cloudns_sub_auth_user=foobar \r\n\t\r\n\t# API password\r\n\tdns_cloudns_auth_password=mypassword", "propagation_seconds": 999, "letsencrypt_agree": true } ``` **Nginx Proxy Manager Version** v2.9.14 **Expected behavior** Some log output would be nice.

kerem

2026-02-26 06:36:37 +03:00

closed this issue
added the
stale

bug
labels

kerem commented

2026-02-26 06:36:37 +03:00

Author

Owner

@chaptergy commented on GitHub (Jan 11, 2022):

Have a look at the letsencrypt logs, as described in https://github.com/NginxProxyManager/nginx-proxy-manager/discussions/1749#user-content-certificate-error. Maybe they contain useful information.

@chaptergy commented on GitHub (Jan 11, 2022): Have a look at the letsencrypt logs, as described in https://github.com/NginxProxyManager/nginx-proxy-manager/discussions/1749#user-content-certificate-error. Maybe they contain useful information.

kerem commented

2026-02-26 06:36:37 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Feb 28, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

@github-actions[bot] commented on GitHub (Feb 28, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 06:36:37 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Apr 12, 2025):

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (Apr 12, 2025): Issue was closed due to inactivity.

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#1295

No description provided.

Rows
Columns