mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 01:15:51 +03:00
[GH-ISSUE #950] New Certbot version + modern key/certificate options #802
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#802
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 @phantomski77 on GitHub (Mar 15, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/950
Is your feature request related to a problem? Please describe.
Requesting bump of
certbotto a version 1.10+ (ideally latest 1.13) which will allow to use Mozilla Modern TLS 1.3 configurations for keys and certificates.Describe the solution you'd like
certbotversion 1.13 (or at least 1.10) which in turn requiresAlpinev 3.13 (certbot 1.11.0-r1) or edge (certbot 1.13.0-r1)Related as an option
/etc/letsencrypt.inichanges tokey-type = ecdsaandelliptic-curve = secp384r1key-type,elliptic-curveandrsa-key-sizefor certificate issue and subsequent renewalscertbotis version 1.10+Describe alternatives you've considered
Manual file editing for
rsa-key-size, otherwise main package changes needed.Additional context
In the ideal world, it would be great to have a configurable choice of all these parameters individually, or ideally a composite option to choose between old, intermediate and modern configurations for both
certbotandnginxas per Mozilla specs (there’s a great configurator for these configurations available on their site above).As always - thank you for your great effort so far. No pressure and thank you for consideration.
@github-actions[bot] commented on GitHub (Mar 16, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Apr 28, 2025):
Issue was closed due to inactivity.