mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #2047] Portainer uses TLS 1.3 that is not supported by NPM #1478
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#1478
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 @TheSander562 on GitHub (May 10, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2047
Checklist
jc21/nginx-proxy-manager:latestdocker image?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:
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)
@nicreuss commented on GitHub (May 11, 2022):
I am experiencing exactly the same issue!
@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.
@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.
@wombatinua commented on GitHub (May 15, 2022):
jacepalm.jpg
@wombatinua commented on GitHub (May 15, 2022):
Minimum TLS version is 1.3 for the latest portainer release. What "temporary" are you talking about?
@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.