It could be that they match more strongly and surpass the file order. But I
guess it will then switch all vhosts to TLSv1.2.
> Am 14.10.2020 um 11:47 schrieb Thomas Plant :
>
> Thanks for the explanation.
> I've read that using a dedicated IP for the Virtualhost would work?
>
> Am 14.10.2020
Thanks for the explanation.
I've read that using a dedicated IP for the Virtualhost would work?
Am 14.10.2020 um 11:29 schrieb Stefan Eissing:
There has been work done by Ylavic regarding this. I do not known in which
release his changes made it.
However, up to then, certain SSL* configs did
There has been work done by Ylavic regarding this. I do not known in which
release his changes made it.
However, up to then, certain SSL* configs did only apply from the _first_
VirtuaLHost for a given port. Subsequent declarations in other vhosts had no
effect. (This is probably all
Am 14.10.2020 um 10:56 schrieb Thomas Plant:
Hello,
I have a virtualhost where i need to allow only TLSv1.2.
Tried following config:
ServerName xx
ServerAlias xx
..
.. cut rest to shorten a bit
..
SSLEngine On
SSLProtocol -all +TLSv1.2
SSLCertificateFile
Hello,
I have a virtualhost where i need to allow only TLSv1.2.
Tried following config:
ServerName xx
ServerAlias xx
..
.. cut rest to shorten a bit
..
SSLEngine On
SSLProtocol -all +TLSv1.2
SSLCertificateFile /etc/letsencrypt/live/x/cert.pem
SSLCertificateKeyFile
