apachectl stop
apt-get install php7.4-fpm # Install the php-fpm from your PHP repository. This package name depends on the vendor.
a2enmod proxy_fcgi setenvif
a2enconf php7.4-fpm # Again, this depends on your PHP vendor.
a2dismod php7.4 # This disables mod_php.
a2dismod mpm_prefork # This disables the prefork MPM. Only one MPM can run at a time.
a2enmod mpm_event # Enable event MPM. You could also enable mpm_worker.
apachectl start
<VirtualHost *:80>
Protocols h2 http/1.1
...
Anything to check?
Apache log file doesnt say any related fault. I checked with Mozilla and Chrome but it`s still using http/1.1
The Guide says something about “cipher configurations” on older TLS versions, but doesn’t go further. How can I check whats needed? I don’t find much information there.
Apache Log says something which is maybe related:
nope, I did not. Which is opening a new topic for me. Didn’t work much on that layer. And exploring a bit, it turned out there is no standard solution.
With some combination of information I got that version running, but still no http/2
This is a non issue. The HTTP2 configuration does not decide whether you connect via HTTP or HTTPS and it can neither downgrade a HTTPS connection to HTTP nor upgrade a HTTP connection to HTTPS.
If you initiate a plain HTTP connection without h2c configured, then http1.1 will be used. The same applies to HTTPS connections when H2 is not configured. In both cases, the connection remains unencrypted or encrypted, respectively.
However, I agree that you could also simply omit h2c from the config. Afaik, most, if not all, browsers don’t support it anyways.