[GH-ISSUE #2763] "ssl_reject_handshake on" disables TLSv1.3 #1898

Closed
opened 2026-02-26 07:33:07 +03:00 by kerem · 4 comments
Owner

Originally created by @Fulachs on GitHub (Mar 28, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2763

  • 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
If you use any version newer than v2.9.19
TLSv1.3 breaks and is no longer working.
See the change here
See issue ticket https://trac.nginx.org/nginx/ticket/2071

Nginx Proxy Manager Version
v2.9.20+

To Reproduce
Steps to reproduce the behavior:

  1. Install any version v2.9.20+
  2. add a proxy and check the TLS version
  3. maximum is TLSv1.2

Expected behavior
TLSv1.3 should work

Found by @piuswalter and myself.

Originally created by @Fulachs on GitHub (Mar 28, 2023). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2763 - 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** If you use any version newer than [v2.9.19](https://github.com/NginxProxyManager/nginx-proxy-manager/releases/tag/v2.9.19) TLSv1.3 breaks and is no longer working. See the change [here](https://github.com/NginxProxyManager/nginx-proxy-manager/commit/a7f0c3b730678ae4352ade2829d891a3ce3cd3bc#diff-28012d6b25fda389a907f6c2484bc834e5cff720ae799b41777a592ef4e3a5b7R35) See issue ticket https://trac.nginx.org/nginx/ticket/2071 **Nginx Proxy Manager Version** v2.9.20+ **To Reproduce** Steps to reproduce the behavior: 1. Install any version v2.9.20+ 2. add a proxy and check the TLS version 3. maximum is TLSv1.2 **Expected behavior** TLSv1.3 should work Found by @piuswalter and myself.
kerem 2026-02-26 07:33:07 +03:00
  • closed this issue
  • added the
    stale
    bug
    labels
Author
Owner

@nietzscheanic commented on GitHub (Mar 30, 2023):

+1

<!-- gh-comment-id:1491087486 --> @nietzscheanic commented on GitHub (Mar 30, 2023): +1
Author
Owner

@BlackKerio commented on GitHub (Apr 3, 2023):

+1

<!-- gh-comment-id:1493890228 --> @BlackKerio commented on GitHub (Apr 3, 2023): +1
Author
Owner

@nietzscheanic commented on GitHub (May 19, 2023):

pull request https://github.com/NginxProxyManager/nginx-proxy-manager/pull/2932

<!-- gh-comment-id:1554487350 --> @nietzscheanic commented on GitHub (May 19, 2023): pull request https://github.com/NginxProxyManager/nginx-proxy-manager/pull/2932
Author
Owner

@github-actions[bot] commented on GitHub (Jan 24, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

<!-- gh-comment-id:1907216986 --> @github-actions[bot] commented on GitHub (Jan 24, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
Sign in to join this conversation.
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#1898
No description provided.