• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved TLSv1.3

Walter

Basic Pleskian
It doesn't appear as though Plesk formally supports TLSv1.3. Either that or the sslmng command needs to be updated. How would you enable TLSv1.3 for nginx?

Code:
user@pleskserver:~# plesk sbin sslmng --custom --protocols="TLSv1.2 TLSv1.3"
WARNING:Ignoring unsuppored protocol TLSv1.3

Code:
user@pleskserver:~# plesk -v
Product version: Plesk Onyx 17.5.3 Update #22
    Update date: 2017/09/18 06:25
     Build date: 2017/03/17 16:00

Code:
user@pleskserver:~# nginx -v
nginx version: nginx/1.11.10
 
I missed my own version before posting the request. I am using nginx 1.11 and not 1.13

http://nginx.org/en/CHANGES
Changes with nginx 1.13.0 25 Apr 2017
*) Feature: the "TLSv1.3" parameter of the "ssl_protocols" directive.

Still interested in understanding where I can customize the TLS protocols and ciphers...
 
I realized my error before your response and altered my question... I posted that I found my issue with the nginx version but am still interested in understanding where one would customize the protocols and ciphers for nginx manually?
 
Hi Walter,

where one would customize the protocols and ciphers for nginx manually?
A "find" - command helps you to display the corresponding files over your command line ( logged in as user "root" over SSH ), which use settings for "ssl_ciphers" or/and "ssl_protocols" at nginx - configuration - files.

Examples:
Code:
find /etc/nginx -type f -name "*.conf" -exec grep --color -Hni "ssl_ciphers" {} \;
and
Code:
find /etc/nginx -type f -name "*.conf" -exec grep --color -Hni "ssl_protocols" {} \;
 
Thank you UFHH01. Didn't just hand me a fish but gave me the pole, worm and hook!

/etc/nginx/conf.d/ssl.conf
 
Back
Top