Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
To continue sharing your ideas and feedback, please visit features.plesk.com
It is up to you which ciphers you enable and which not. Some ciphers may be needed for old browsers (compatibility issues), but some may be weak and should not be used. If you follow the article you have linked, it is your decision. You cannot only put ciphers into the file, they must be preceded by a directive "ssl_ciphers", and you should also include the protocol definition directive as shown in the example above.
There is no "best". It depends on what you want to achieve. If you want old browsers to work with your server, you will need to include weak cipher algorithms. If you want a very secure system, you only include the latest, strongest - at the price that some browsers won't be able to connect. I am pretty sure that example I posted above is a balanced solution.
Nginx must be reloaded or restarted after the change. I recommend to first run
# nginx -t
to ensure that all configuration files are correct before a reload or restart is done.
Plesk offers quite a lot of CLI commands as well, where additional / optional settings can be configured WITHOUT the need of manual edits ( which are often overwritten by updates/upgrades/patches! ) in your configuration files.
you are MIXING several ciphers suites recommendations now, which will lead to errors/issues/problems. Pls. stick to your preferred ciphers suites, which you choosed from