AWS Route53 DNS Challenge Issue Due to Propagation

I am running into an issue using the DNS challenge in AWS and I believe the previous place I posted on is now closed. The DNS challenge with AWS was working for me before, but as of the last few months, I'm getting the following when trying to get a new cert for a domain with DNS challenge in Route53. It happens whether I leave the propagation field blank or put in a value.

Version:

docker inspect npm | grep -i version
                "OPENRESTY_VERSION=1.27.1.2",
                "CROWDSEC_OPENRESTY_BOUNCER_VERSION=0.1.7",
                "NPM_BUILD_VERSION=2.14.0",
                "com.docker.compose.version": "5.0.2",
                "org.label-schema.schema-version": "1.0"

image: jc21/nginx-proxy-manager:latest

Log:

[3/17/2026] [1:39:27 PM] [Nginx    ] › ℹ  info      Reloading Nginx
[3/17/2026] [1:39:28 PM] [Certbot  ] › ▶  start     Installing route53...
[3/17/2026] [1:39:32 PM] [Certbot  ] › ☒  complete  Installed route53
[3/17/2026] [1:39:32 PM] [SSL      ] › ℹ  info      Requesting LetsEncrypt certificates via Route 53 (Amazon) for Cert #46: <redacted>
[3/17/2026] [1:39:32 PM] [SSL      ] › ℹ  info      Command: certbot certonly --config /etc/letsencrypt.ini --work-dir /tmp/letsencrypt-lib --logs-dir /data/logs --cert-name npm-46 --agree-tos -m <redacted> --preferred-challenges dns --domains <redacted> --authenticator dns-route53 --dns-route53-propagation-seconds
[3/17/2026] [1:39:34 PM] [Nginx    ] › ℹ  info      Reloading Nginx
[3/17/2026] [1:39:35 PM] [Express  ] › ⚠  warning   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

[3/17/2026] [1:42:46 PM] [Nginx    ] › ℹ  info      Reloading Nginx
[3/17/2026] [1:42:47 PM] [Certbot  ] › ▶  start     Installing route53...
[3/17/2026] [1:42:50 PM] [Certbot  ] › ☒  complete  Installed route53
[3/17/2026] [1:42:50 PM] [SSL      ] › ℹ  info      Requesting LetsEncrypt certificates via Route 53 (Amazon) for Cert #47: <redacted>
[3/17/2026] [1:42:51 PM] [SSL      ] › ℹ  info      Command: certbot certonly --config /etc/letsencrypt.ini --work-dir /tmp/letsencrypt-lib --logs-dir /data/logs --cert-name npm-47 --agree-tos -m <redacted> --preferred-challenges dns --domains <redacted> --authenticator dns-route53 --dns-route53-propagation-seconds 60
[3/17/2026] [1:42:53 PM] [Nginx    ] › ℹ  info      Reloading Nginx
[3/17/2026] [1:42:54 PM] [Express  ] › ⚠  warning   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

Originally posted by @bjmaynard01 in #4702

Start from the certificate request command shown in the issue and trace how the Route53 DNS challenge's propagation setting is passed to Certbot. Check the Route53 challenge integration and reproduce with the blank and 60-second propagation values; done means the generated command uses a supported option and the certificate request proceeds without the reported argument error.