mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #1570] Let's Encrypt DST Root CA X3 Expiration fix for DNS Challenge #1183
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#1183
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @binsentsu on GitHub (Nov 6, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1570
Checklist
jc21/nginx-proxy-manager:latestdocker image?Describe the bug
Within issue #1459 a fix was created for the http-challenge only. The DNS challenge command does not use the --config parameter which references the letsencrypt.ini file. I can confirm that adding the
--preferred-chain = "ISRG Root X1"directly within the requestLetsEncryptSslWithDnsChallenge method does the trick. Don't know if the same directive would be necessary for the renew command though.Nginx Proxy Manager Version
2.9.11
To Reproduce
Expected behavior
Screenshots
Operating System
Additional context