Resolved ALPN support for CentOS 6.8

[Aitana]

Hi there,

On 30 May 2016 with the 12.5.30 Update 35 in Linux there was added the ALPN (Application-Layer Protocol Negotiation) support for nginx making HTTP/2 available in the Chrome browser.

Unfortunately the ALPN support is not available for CentOS 6.8 (update applicable for CentOS 7, RHEL 7, Cloudlinux 7, Ubuntu 14, and Debian 8 - for details, refer to https://kb.plesk.com/en/128733).

When will there be ALPN support for CentOS 6.8?

Best regards from Spain.

 

[Linulex]

i guess: never.

ALPN requires at least OpenSSL 1.0.2.
centos 6.x comes with OpenSSL 1.0.1. (1.0.1e-48.el6_8.1 to be precize)

everything that uses ssl is comiled against this version of openssl, so replacing it will most certainly brake stuff.

regards
Jan

 

[Aitana]

Hi Jan,

Thanks for the info. We were asking this because Plesk has it's own nginx (sw-nginx) and doesn't run with the server nginx (as far as we know). Wouldn't it be possible to replace the OpenSSL compiled in the Plesk sw-nginx to a OpenSSL version at least 1.0.2?

Regards.

 

[IgorG]

Wouldn't it be possible to replace the OpenSSL compiled in the Plesk sw-nginx to a OpenSSL version at least 1.0.2?

You can do it and some people on the forum have already done it, but note - your custom nginx will be overwritten by next Plesk update.

 

[Aitana]

Hi IgorG,

Are there no plans from Plesk to include this functionality by default in sw-nginx?

Thanks for your help.

 

[IgorG]

Hi IgorG,

Are there no plans from Plesk to include this functionality by default in sw-nginx?

Thanks for your help.

We support ALPN only for latest OS versions. You can migrate to CentOS7 for example. If you don't want it - it will not lead to any problems, but for Chrome browser, for instance, sites will work with standard https instead of http/2.

 

[Aitana]

Thanks for the info. The thing is that we understood that we can't migrate to Centos 7 from Centos 6.8 with Plesk, but we have to create a new installation and then import Plesk data. Or can we update to Centos7 without reinstalling?

 

[IgorG]

Or can we update to Centos7 without reinstalling?

No. Dist-upgrade is supported only for Debian and Ubuntu, more detail in documentation.

 

[G J Piper]

I too am trying to find a solution that doesn't require me to move a bunch of domains to a new Plesk 17/CentOS7 install from CentOS6. Everything is working beautifully except ALPN. I wonder if I should trust a full migration using the built-in Plesk Migrator. Anyone try it with a full server of dozens of domains?

 

[IgorG]

I wonder if I should trust a full migration using the built-in Plesk Migrator.

Yes, you can trust Plesk Migration and safely use it for migration. Also you can request free migration assistance here Free migration to Plesk - Plesk

 

[websavers]

FYI: cPanel has statically compiled OpenSSH 1.0.2 specifically to enable ALPN support on CentOS6 machines. Given that Plesk is now more costly than cPanel, I'd expect similar support from you. You should be releasing nginx binaries cross-compiled with a custom version of OpenSSH to ensure ALPN HTTP/2 support is available on CentOS6.

 

[G J Piper]

FYI: cPanel has statically compiled OpenSSH 1.0.2 specifically to enable ALPN support on CentOS6 machines. Given that Plesk is now more costly than cPanel, I'd expect similar support from you. You should be releasing nginx binaries cross-compiled with a custom version of OpenSSH to ensure ALPN HTTP/2 support is available on CentOS6.

I LOVE this idea.

 

[Linulex]

me too, and it cant be that hard. Here is an example how plesk could do it

RPM build Nginx 1.11.x with ALPN on CentOS 6/7 using static OpenSSL 1.1 (v 1.02+ required for http/2 support in Chrome) · GitHub

regards
Jan

 

[Linulex]

I found this, use at your own risk

nginx-alpn/mainline - Packages - packagecloud.io | packagecloud

regards
Jan

 

[IgorG]

Guys,

I can say that we are discussing this topic now, and a little later we will update this thread with more details.

As temporary possible solution you can try to use this script - Archive - Script for building replacement of default sw-nginx Plesk package (CentOS6 ONLY!)
Maybe for experiments. For instance, I use it right now on my personal Plesk based WordPress site.

 

[Linulex]

@IgorG

I have used the package from packagecloud.io and disabled the plesk_nginx repositry. (only on a test server so far).

Would this give problems with plesk updates or will they just skip nginx and happelly motor on? Or maybe other points to consider?

regards
Jan

 

[G J Piper]

Guys,
I can say that we are discussing this topic now, and a little later we will update this thread with more details.

I'm happy to hear some talking has begun on this, as I prefer to wait for the official Plesk solution for this rather than risk any of the "use at your own risk" solutions presented here. It is a bit frustrating having CentOS 6.9 and http2 running finally but having 80% of the desktop browsers out there completely ignoring it and hitting with http1.1 still. Thank goodness Apple's browsers are still all hitting at H2 without ALPN at least.

 

[IgorG]

@IgorG

I have used the package from packagecloud.io and disabled the plesk_nginx repositry. (only on a test server so far).

Would this give problems with plesk updates or will they just skip nginx and happelly motor on? Or maybe other points to consider?

regards
Jan

I see no problem for months with this setting:

 

[IgorG]

I'm happy to hear some talking has begun on this, as I prefer to wait for the official Plesk solution for this rather than risk any of the "use at your own risk" solutions presented here. It is a bit frustrating having CentOS 6.9 and http2 running finally but having 80% of the desktop browsers out there completely ignoring it and hitting with http1.1 still. Thank goodness Apple's browsers are still all hitting at H2 without ALPN at least.

Of course, this is up to you. But many people like to experiment, and at least for a single personal Plesk server this is quite a working solution.

 

[Ruslan Kosolapov]

Hi all.

The case is clear, thanks!
I suggest creating a UserVoice request for the feature. It could help to prioritize the case.