[GH-ISSUE #748] Option to use TLSv1.2 instead of TLSv1.3 #635

New issue

Closed

opened 2026-02-26 06:33:46 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 06:33:46 +03:00

Owner

Originally created by @PlasmatikSteak on GitHub (Dec 1, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/748

Is your feature request related to a problem? Please describe.
Not a problem with nginx-proxy-manager, but Home Assistant and SmartThings integration not working with TLSv1.3.

Describe the solution you'd like
Option use TLSv1.2 instead of 1.3 under settings for any given proxy-host.

Describe alternatives you've considered
I tried to add ssl_protocols TLSv1.2; to the "Custom Nginx Configuration" section under Advanced for a given proxy-host but the result is that TLSv1.3 is still used.

Additional context
https://www.home-assistant.io/integrations/smartthings/#webhook-troubleshooting-checklist

Originally created by @PlasmatikSteak on GitHub (Dec 1, 2020). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/748 **Is your feature request related to a problem? Please describe.** Not a problem with nginx-proxy-manager, but Home Assistant and SmartThings integration not working with TLSv1.3. **Describe the solution you'd like** Option use TLSv1.2 instead of 1.3 under settings for any given proxy-host. **Describe alternatives you've considered** I tried to add ssl_protocols TLSv1.2; to the "Custom Nginx Configuration" section under Advanced for a given proxy-host but the result is that TLSv1.3 is still used. **Additional context** https://www.home-assistant.io/integrations/smartthings/#webhook-troubleshooting-checklist

kerem

2026-02-26 06:33:46 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-02-26 06:33:46 +03:00

Author

Owner

@mochman commented on GitHub (Dec 3, 2020):

It looks like this is an issue with nginx itself.
A workaround would be to set all of your sites to v1.2. You can do that by modifying the ssl_protocols portion of the /etx/nginx/conf.d/include/ssl-ciphers.conf file in the app container.

@mochman commented on GitHub (Dec 3, 2020): It looks like this is an [issue](https://trac.nginx.org/nginx/ticket/676) with nginx itself. A workaround would be to set all of your sites to v1.2. You can do that by modifying the `ssl_protocols` portion of the `/etx/nginx/conf.d/include/ssl-ciphers.conf` file in the app container.

kerem referenced this issue

2026-02-26 07:38:42 +03:00

[PR #635] [MERGED] Allow DNS challenges not just for cloudflare #3274

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#635

No description provided.

Rows
Columns