![]() Open an instance of SSH from your Lightsail dashboard.I was also having this problem and put together the following solution: Of course after every change I used to restart Apache. I tryed to simply update the nf and the nf, but nothing appens: TLS 1.3 does not work and TLS 1.0 and TLS 1.1 are always anabled.Īfter my adds, this is my ssl directives in nf file: # SSLProtocol all -SSLv3īut nothing changed and now I really do not know how to enable TLS 1.3 and disable TLS 1.0 and TLS 1.1. Include "/opt/bitnami/apache2/conf/bitnami/nf" # Bitnami applications installed with a prefix URL (default) ![]() ![]() SSLCertificateKeyFile "/opt/bitnami/apache2/conf/mydomain.key" SSLCertificateFile "/opt/bitnami/apache2/conf/mydomain.crt" SSLCipherSuite "EECDH+ECDSA+AESGCM EECDH+aRSA+AESGCM EECDH+ECDSA+SHA384 EECDH+ECDSA+SHA$ So, inside the nf file I found this block, that seems the right place: # Default SSL Virtual Host configuration. Reading on the net I found that I must change the nf file to insert this directive SSLProtocol -all +TLSv1.2 Now it seems that my Apache version 2.4.39 supports also TLS 1.3 and I am trying to enable even it and disable the two older versions. This is my first experience with Amazon Lighsail, Wordpress Multisite, BitnamiĪnd even with Let's Encrypt now it seems everything just works, except for SSL directives in my virtualhost file.īecause it seems that major browsers – aka Chrome, Safari/Webkit, Mozilla Firefox and IE/Edge - are going to remove support to TLS 1.0 and TLS 1.1, as soon as the beginning of the new year – precisely among January and March – I would want to know how to disable them for my new Wordpress Multisite instance in Lightsail.Īfter I obtained a Let’s Encript SSL certificate and successfully deployed it I tested it to verify that TLS 1.0 and TLS 1.1 are enabled along with TLS 1.2.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |