Facebook
Twitter-
Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
To get into the festive spirit, install the Skins extension. -
The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
-
The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
-
The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.
Resolved http/2 without nginx possible?
U
UFHH01
Guest
Hi Ralph,
as you already met the basic ( apache >= 2.4.17 ) requirements, you may certainly use "apache - only" as well. At the Plesk documentation you find for example:
with the example command ( for NGINX! ):
as you already met the basic ( apache >= 2.4.17 ) requirements, you may certainly use "apache - only" as well. At the Plesk documentation you find for example:
with the example command ( for NGINX! ):
Code:
plesk sbin sslmng --services=nginx --custom --ciphers="EECDH+AESGCM+AES128:EECDH+AESGCM+AES256:EECDH+CHACHA20:EDH+AESGCM+AES128:EDH+AESGCM+AES256:EDH+CHACHA20" --protocols="TLSv1 TLSv1.1 TLSv1.2"You may certainly use the very same command for the apache - service:
Code:
plesk sbin sslmng --services=apache --custom --ciphers="EECDH+AESGCM+AES128:EECDH+AESGCM+AES256:EECDH+CHACHA20:EDH+AESGCM+AES128:EDH+AESGCM+AES256:EDH+CHACHA20" --protocols="TLSv1 TLSv1.1 TLSv1.2"
Ralph
New Pleskian
Hi,
thanks for your reply.
Unfortunately, this doesn't works for me. This command seems to set the protocols and the ciphers but it's not activating HTTP/2 (without the use of NGINX).
To get HTTP/2 working I still have to install and activate NGINX, then running "plesk bin http2_pref enable".
Maybe I did something wrong?
Regards,
Ralph
thanks for your reply.
Unfortunately, this doesn't works for me. This command seems to set the protocols and the ciphers but it's not activating HTTP/2 (without the use of NGINX).
To get HTTP/2 working I still have to install and activate NGINX, then running "plesk bin http2_pref enable".
Maybe I did something wrong?
Regards,
Ralph
From documentation HTTP/2 Support in Plesk :
"HTTP/2 support is available for Plesk customers starting from the version 12.5.30 Update #28 and requires the latest version of nginx."
"... requires the latest version of nginx" means that it only works if the latest version of nginx is used. There is no support for Apache.
Apache does not handle http/2 connections in its core installation. For use with Apache, you need to install and activate mod_httpd2, which is a separate module for Apache that is not delivered with Plesk but needs to be installed separately by you (or a system administrator). It is available for Apache versions newer than 2.4.17. Your Apache qualifies for it. It might then require additional directives in the Apache configuration file.
mod_http2 - Apache HTTP Server Version 2.4
"HTTP/2 support is available for Plesk customers starting from the version 12.5.30 Update #28 and requires the latest version of nginx."
"... requires the latest version of nginx" means that it only works if the latest version of nginx is used. There is no support for Apache.
Apache does not handle http/2 connections in its core installation. For use with Apache, you need to install and activate mod_httpd2, which is a separate module for Apache that is not delivered with Plesk but needs to be installed separately by you (or a system administrator). It is available for Apache versions newer than 2.4.17. Your Apache qualifies for it. It might then require additional directives in the Apache configuration file.
mod_http2 - Apache HTTP Server Version 2.4
You can use HTTP/2 without nginx. Make sure that mod_http2 is installed and enabled, then go to
Apache & nginx settings -> Additional directives for HTTPS
And add the following line:
Note: http/1.1 also includes HTTP 1.0 support.
Regards,
Anthony Ananich
Apache & nginx settings -> Additional directives for HTTPS
And add the following line:
Code:
Protocols h2 http/1.1Regards,
Anthony Ananich
Lrnt
Regular Pleskian
This does not work.
Enabling http2 in Apache + Directive on domain = http 1.1
Similar threads
