Let's Encrypt - Propagation Seconds (GUI) not applied for Active24 DNS challenge

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.

Start by tracing the SSL Certificate wizard's Active24 DNS challenge handling through the certbot invocation. Verify how the Propagation Seconds value is carried into the request, then reproduce with 600 seconds and confirm the generated call includes --dns-active24-propagation-seconds 600 and delays validation accordingly.