• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Question HTTP/2 Server Push for Apache possible?

mdde

Regular Pleskian
Hi,
with latest Plesk (17.5.x and Debian 8.9) can i enable HTTP/2?
I have nginx completely disabled (some years ago) and i don't want to enable it.

Is it possible with Apache2 only? If yes, how? I didn't find helpful KBs
 
Hm, i have a Server with multiple Joomlas and Wordpresses.
Can i just install NGINX and regenerate all vhosts configs?
Will that work on the fly? or do i have to take care over ALL htaccess files and so on?
 
In general, everything should work properly, but you understand that nothing is perfect and problems are possible.
If you have something special in your .htaccess files I can recommend you try to use this Plesk extension - htaccess to nginx - Plesk Extensions
 
Hi,
with latest Plesk (17.5.x and Debian 8.9) can i enable HTTP/2?
I have nginx completely disabled (some years ago) and i don't want to enable it.

Is it possible with Apache2 only? If yes, how? I didn't find helpful KBs
I don't know of anyone running Apache with http/2 support on Plesk. It can be done, but it's very convoluted and you might run into various packaging issues - dependencies, yum priorities and all that. For CentOS 7 I've got a non-Plesk test server running Apache 2.4.27 with http/2 support, but there are caveats:
- You need CentOS 7.4 with the latest OpenSSL 1.0.2k and you must rebuild httpd with http/2 support.
- http/2 requires a threaded multi processing module, so prefork won't work. However, if running worker you'll run into problems with various PHP libraries (php-imap comes to mind) which aren't thread safe and will experience random crashes.
- No NPN support, just ALPN, so certain older browsers will still use 1.1
For Plesk I'd stick with sw-nginx as proxy for Apache for the time being.
 
Back
Top