mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #128] Add TLS 1.3 Support #113
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#113
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 @ne4u on GitHub (Apr 30, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/128
Using the latest version of alpine linux should add nginx and openssl versions that support TLS 1.3
@jessebraham commented on GitHub (May 2, 2019):
Previously haven't had any issues, upon installing on a new machine tonight I get a
502whenever I try to hit a proxy host. Looking indata/logs/error.logI found:So yeah, looks like no TLS 1.3 support and therefore new certificates from Letsencrypt will not work.
@jc21 commented on GitHub (May 2, 2019):
Ok if someone wants to test the fix here, use this docker image and let me know how you go before I move forward:
jc21/nginx-proxy-manager:developnote this is an
amd64, won't work on any raspberry pi's@jessebraham commented on GitHub (May 2, 2019):
That was quick! So I think I had mis-configured something, and the error message was just a bit of a red-herring. I tested your develop image (which has some CSS oddities, by the way, seems fine otherwise though) and it worked. However, I then reverted to latest and everything seems happy still, so as I said I think I had made a mistake on my end 😄
@OhHeyAlan commented on GitHub (May 7, 2019):
@jc21 I've been running
jc21/nginx-proxy-manager:developfor about a week now with no problems and I modified the ssl-ciphers.conf to only allow TLSv1.2 & TLSv1.3@jc21 commented on GitHub (May 7, 2019):
Awesome. I'll promote this to a new release