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 #4711] Let's Encrypt - Propagation Seconds (GUI) not applied for Active24 DNS challenge #2992

New issue

Open

opened 2026-02-26 07:37:31 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 07:37:31 +03:00

Owner

Originally created by @elvisek2020 on GitHub (Aug 13, 2025).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4711

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 (found #4702 and #1862 for other DNS providers)

Describe the bug

When using the initial wizard to request a Let's Encrypt certificate via DNS Challenge (specifically with Active24), the value entered in the Propagation Seconds field is ignored. Certbot starts DNS validation almost immediately, regardless of what value is entered.

From UI, it appears that the value is acknowledged (e.g. "Waiting up to 600 seconds"), but the challenge is still sent within ~2 seconds. This leads to No TXT record found errors due to insufficient DNS propagation time.

Nginx Proxy Manager Version
jc21/nginx-proxy-manager:latest (tested with version 2.12.6)

To Reproduce

Open the SSL Certificate wizard (before saving any entries to DB).
Select Active24 as DNS provider.
Set a value in Propagation Seconds (e.g. 600).
Complete required fields and start certificate request.
Observe logs and certbot behavior: DNS validation starts too early and fails.

Expected behavior

Certbot should be instructed to wait the specified number of seconds before attempting DNS validation. For Active24, this means passing: –dns-active24-propagation-seconds 600
to the underlying certbot call.

Screenshots

N/A – but can provide if needed.

Operating System

Docker on Debian 12 (but container logic is NPM-specific)

Thank you for your awesome work! Happy to assist with debugging or testing fixes.

Originally created by @elvisek2020 on GitHub (Aug 13, 2025). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4711  **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 (found #4702 and #1862 for other DNS providers) --- **Describe the bug** When using the initial wizard to request a Let's Encrypt certificate via DNS Challenge (specifically with Active24), the value entered in the **Propagation Seconds** field is ignored. Certbot starts DNS validation almost immediately, regardless of what value is entered. From UI, it appears that the value is acknowledged (e.g. "Waiting up to 600 seconds"), but the challenge is still sent within ~2 seconds. This leads to `No TXT record found` errors due to insufficient DNS propagation time. --- **Nginx Proxy Manager Version** `jc21/nginx-proxy-manager:latest` (tested with version 2.12.6) --- **To Reproduce** 1. Open the SSL Certificate wizard (before saving any entries to DB). 2. Select Active24 as DNS provider. 3. Set a value in **Propagation Seconds** (e.g. 600). 4. Complete required fields and start certificate request. 5. Observe logs and certbot behavior: DNS validation starts too early and fails. --- **Expected behavior** Certbot should be instructed to wait the specified number of seconds before attempting DNS validation. For Active24, this means passing: –dns-active24-propagation-seconds 600 to the underlying certbot call. --- **Screenshots** _N/A – but can provide if needed._ --- **Operating System** Docker on Debian 12 (but container logic is NPM-specific) --- Thank you for your awesome work! Happy to assist with debugging or testing fixes.

kerem added the

stale

bug

labels

2026-02-26 07:37:31 +03:00

kerem commented

2026-02-26 07:37:31 +03:00

Author

Owner

@elvisek2020 commented on GitHub (Aug 13, 2025):

This screenshot shows that I’ve set Propagation Seconds to 900 seconds in the NPM GUI.
However, in the logs, it’s clear that Certbot initiates DNS validation immediately after creating the TXT record, without waiting.

This proves that the propagation_seconds value entered in the wizard is not applied.

This logs confirms that the propagation_seconds value entered in the wizard is not applied at all.

2025-08-13 14:51:14,373:DEBUG:certbot._internal.display.obj:Notifying user: Waiting at most 900 seconds for DNS changes to propagate
2025-08-13 14:51:15,016:DEBUG:acme.client:Sending POST request to https://acme-v02.api.letsencrypt.org/acme/chall/.../G2qfDg
2025-08-13 14:51:16,339:DEBUG:acme.client:Received response:
{
  "type": "dns-01",
  "status": "invalid",
  "error": {
    "type": "urn:ietf:params:acme:error:unauthorized",
    "detail": "No TXT record found at _acme-challenge.test.example.com"
  }
}```

@elvisek2020 commented on GitHub (Aug 13, 2025): This screenshot shows that I’ve set Propagation Seconds to 900 seconds in the NPM GUI. However, in the logs, it’s clear that Certbot initiates DNS validation immediately after creating the TXT record, without waiting. This proves that the propagation_seconds value entered in the wizard is not applied. <img width="496" height="1354" alt="Image" src="https://github.com/user-attachments/assets/a04e21db-1591-40fa-9de6-e0540c648792" /> <br> <br> <br> This logs confirms that the propagation_seconds value entered in the wizard is not applied at all. ```2025-08-13 14:51:14,372:DEBUG:certbot_dns_active24.dns_active24:Successfully added TXT record 2025-08-13 14:51:14,373:DEBUG:certbot._internal.display.obj:Notifying user: Waiting at most 900 seconds for DNS changes to propagate 2025-08-13 14:51:15,016:DEBUG:acme.client:Sending POST request to https://acme-v02.api.letsencrypt.org/acme/chall/.../G2qfDg 2025-08-13 14:51:16,339:DEBUG:acme.client:Received response: { "type": "dns-01", "status": "invalid", "error": { "type": "urn:ietf:params:acme:error:unauthorized", "detail": "No TXT record found at _acme-challenge.test.example.com" } }```

kerem commented

2026-02-26 07:37:31 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Feb 25, 2026):

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

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

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

No description provided.

Rows
Columns