[GH-ISSUE #2047] Portainer uses TLS 1.3 that is not supported by NPM #1478

Closed
opened 2026-02-26 07:31:14 +03:00 by kerem · 6 comments
Owner

Originally created by @TheSander562 on GitHub (May 10, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2047

Checklist

  • 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
Portainer now requires TLS 1.3 and cannot be used with TLS 1.2. So i am getting bad TLS handshake errors.

Can NPM switch to TLS version 1.3 or make an option to only do certain proxies with TLS 1.3?

Nginx Proxy Manager Version
v2.9.18

To Reproduce
Steps to reproduce the behavior:

  1. In NPM make a proxy for Portainer HTTPS
  2. Use latest Portainer 2.13.0
  3. See the error when trying to access it.

Expected behavior
You should see the Portainer login page

Error
level=info msg="2022/05/10 22:06:12 http: TLS handshake error from 10.10.10.12:43718: tls: client offered only unsupported versions: [303 302 301]"

Operating System
Synology NAS 918+ (Ubuntu Linux of some sort)

Originally created by @TheSander562 on GitHub (May 10, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2047 **Checklist** - 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** Portainer now requires TLS 1.3 and cannot be used with TLS 1.2. So i am getting bad TLS handshake errors. Can NPM switch to TLS version 1.3 or make an option to only do certain proxies with TLS 1.3? **Nginx Proxy Manager Version** v2.9.18 **To Reproduce** Steps to reproduce the behavior: 1. In NPM make a proxy for Portainer HTTPS 2. Use latest Portainer 2.13.0 3. See the error when trying to access it. **Expected behavior** You should see the Portainer login page **Error** level=info msg="2022/05/10 22:06:12 http: TLS handshake error from 10.10.10.12:43718: tls: client offered only unsupported versions: [303 302 301]" **Operating System** Synology NAS 918+ (Ubuntu Linux of some sort)
kerem 2026-02-26 07:31:14 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@nicreuss commented on GitHub (May 11, 2022):

I am experiencing exactly the same issue!

<!-- gh-comment-id:1123761931 --> @nicreuss commented on GitHub (May 11, 2022): I am experiencing exactly the same issue!
Author
Owner

@wombatinua commented on GitHub (May 11, 2022):

Just add proxy_ssl_protocols TLSv1.3; to the Advanced section.
This is mentioned in the portainer release notes.

<!-- gh-comment-id:1123906364 --> @wombatinua commented on GitHub (May 11, 2022): Just add `proxy_ssl_protocols TLSv1.3;` to the Advanced section. This is mentioned in the portainer release notes.
Author
Owner

@TheSander562 commented on GitHub (May 11, 2022):

Yes thank you, this works as temporary fix.
I see now there is a fix to allow TLS1.2 again so i will close this issue.

<!-- gh-comment-id:1123918403 --> @TheSander562 commented on GitHub (May 11, 2022): Yes thank you, this works as temporary fix. I see now there is a fix to allow TLS1.2 again so i will close this issue.
Author
Owner

@wombatinua commented on GitHub (May 15, 2022):

jacepalm.jpg

<!-- gh-comment-id:1126889151 --> @wombatinua commented on GitHub (May 15, 2022): jacepalm.jpg
Author
Owner

@wombatinua commented on GitHub (May 15, 2022):

Minimum TLS version is 1.3 for the latest portainer release. What "temporary" are you talking about?

<!-- gh-comment-id:1126889268 --> @wombatinua commented on GitHub (May 15, 2022): Minimum TLS version is 1.3 for the latest portainer release. What "temporary" are you talking about?
Author
Owner

@TheSander562 commented on GitHub (May 15, 2022):

Well the best way is to integrate TLS 1.3 into the proxy itself instead to rely on the user.
And it was temporary because Portainer doesnt require the TLS 1.3 anymore as of https://github.com/portainer/portainer/releases/tag/2.13.1

So it works without it again.

<!-- gh-comment-id:1127010609 --> @TheSander562 commented on GitHub (May 15, 2022): Well the best way is to integrate TLS 1.3 into the proxy itself instead to rely on the user. And it was temporary because Portainer doesnt require the TLS 1.3 anymore as of https://github.com/portainer/portainer/releases/tag/2.13.1 So it works without it again.
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#1478
No description provided.