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 #4702] Let's Encrypt Certificate fails if Propagation Seconds is set for Route53 DNS Challenge #2986

New issue

Open

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

kerem commented

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

Owner

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

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 was trying to create a Let's Encrypt Certificate with DNS Challenge for Route53 and I noticed that if you set the parameter Propagation Seconds it fails with the following error

CommandError: usage: 
  certbot [SUBCOMMAND] [options] [-d DOMAIN] [-d DOMAIN] ...

Certbot can obtain and install HTTPS/TLS/SSL certificates.  By default,
it will attempt to use a webserver both for obtaining and installing the
certificate. 
certbot: error: unrecognized arguments: --dns-route53-propagation-seconds 60

    at /app/lib/utils.js:16:13
    at ChildProcess.exithandler (node:child_process:430:5)
    at ChildProcess.emit (node:events:524:28)
    at maybeClose (node:internal/child_process:1104:16)
    at ChildProcess._handle.onexit (node:internal/child_process:304:5)

Nginx Proxy Manager Version

v2.12.6

To Reproduce
Steps to reproduce the behavior:

Go to SSL Certificates
Click on Add SSL Certificate > Let's Encrypt
Fill the form with DNS Challenge enabled
Set Route53 for DNS provider
Set any value for Propagation Seconds

Expected behavior

It seems that certbot deleted the parameter for propagation seconds in v3.0.0

The --dns-route53-propagation-seconds command line flag was removed.

Source: github.com/certbot/certbot@f0f036a34c/certbot/CHANGELOG.md

Screenshots

Operating System

Ubuntu 24

Additional context

N/A

Originally created by @pascaruchan on GitHub (Aug 10, 2025). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4702  **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 was trying to create a Let's Encrypt Certificate with DNS Challenge for Route53 and I noticed that if you set the parameter `Propagation Seconds` it fails with the following error ``` CommandError: usage: certbot [SUBCOMMAND] [options] [-d DOMAIN] [-d DOMAIN] ... Certbot can obtain and install HTTPS/TLS/SSL certificates. By default, it will attempt to use a webserver both for obtaining and installing the certificate. certbot: error: unrecognized arguments: --dns-route53-propagation-seconds 60 at /app/lib/utils.js:16:13 at ChildProcess.exithandler (node:child_process:430:5) at ChildProcess.emit (node:events:524:28) at maybeClose (node:internal/child_process:1104:16) at ChildProcess._handle.onexit (node:internal/child_process:304:5) ``` **Nginx Proxy Manager Version**  v2.12.6 **To Reproduce** Steps to reproduce the behavior: 1. Go to SSL Certificates 2. Click on Add SSL Certificate > Let's Encrypt 3. Fill the form with DNS Challenge enabled 4. Set Route53 for DNS provider 5. Set any value for Propagation Seconds **Expected behavior**  It seems that certbot deleted the parameter for propagation seconds in `v3.0.0` > The --dns-route53-propagation-seconds command line flag was removed. Source: https://github.com/certbot/certbot/blob/f0f036a34c7f5187025171e3c39dd941f30e273c/certbot/CHANGELOG.md **Screenshots**  <img width="515" height="1269" alt="Image" src="https://github.com/user-attachments/assets/1b56a4ee-1c72-4e9c-8294-b721c7b8a772" /> **Operating System**  Ubuntu 24 **Additional context**  N/A

kerem added the

stale

bug

labels

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

kerem commented

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

Author

Owner

@pascaruchan commented on GitHub (Aug 10, 2025):

I have created a Pull Request with a fix for this issue: https://github.com/NginxProxyManager/nginx-proxy-manager/pull/4703

@pascaruchan commented on GitHub (Aug 10, 2025): I have created a Pull Request with a fix for this issue: https://github.com/NginxProxyManager/nginx-proxy-manager/pull/4703

kerem commented

2026-02-26 07:37:30 +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#2986

No description provided.

Rows
Columns