• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Resolved http/2 in almalinux ?

I couldn't reproduce the issue.

Could you please show output of:
curl -v --http2 https://<youripaddress>
 
alma 8: domain point to ip, this is the default servername and has and let encrypt, no hosting

> curl -v --http2 https://kvm47004.linulex.net
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed

0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Trying 185.95.47.4:443...
* Connected to kvm47004.linulex.net (185.95.47.4) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* CAfile: none
* CApath: none
* loaded libnssckbi.so
* ALPN, server accepted to use http/1.1
* SSL connection using TLS_AES_128_GCM_SHA256
* Server certificate:
* subject: CN=kvm47004.linulex.net
* start date: Jan 31 15:28:15 2022 GMT
* expire date: May 01 15:28:14 2022 GMT
* common name: kvm47004.linulex.net
* issuer: CN=R3,O=Let's Encrypt,C=US
> GET / HTTP/1.1
> Host: kvm47004.linulex.net
> User-Agent: curl/7.80.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Server: nginx
< Date: Wed, 16 Feb 2022 09:42:48 GMT
< Content-Type: text/html
< Content-Length: 578
< Connection: keep-alive
< Vary: Accept-Encoding
< Last-Modified: Mon, 07 Feb 2022 22:14:20 GMT
< Accept-Ranges: bytes
< Cache-Control: max-age=300
< Expires: Wed, 16 Feb 2022 09:47:48 GMT
< Vary: Accept-Encoding,User-Agent
< Cache-Control: public

centos 7: domain points to ip adres, no hosting, no valid certificate for this domain

> curl -vk --http2 https://mijnhostingpanel.nl
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed

0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Trying 185.95.44.244:443...
* Connected to mijnhostingpanel.nl (185.95.44.244) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* CAfile: none
* CApath: none
* loaded libnssckbi.so
* skipping SSL peer certificate verification
* ALPN, server accepted to use h2
* SSL connection using TLS_AES_256_GCM_SHA384
* Server certificate:
* subject: CN=kvmtest244.linulex.net
* start date: Jan 13 10:29:09 2022 GMT
* expire date: Apr 13 10:29:08 2022 GMT
* common name: kvmtest244.linulex.net
* issuer: CN=R3,O=Let's Encrypt,C=US
* Using HTTP2, server supports multiplexing
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x15432c0)
> GET / HTTP/2
> Host: mijnhostingpanel.nl
> user-agent: curl/7.80.0
> accept: */*
>
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 200
< server: nginx
< date: Wed, 16 Feb 2022 09:56:14 GMT
< content-type: text/html
< content-length: 578
< vary: Accept-Encoding
< last-modified: Fri, 22 Apr 2016 16:12:23 GMT
< accept-ranges: bytes
< vary: Accept-Encoding,User-Agent
< cache-control: public


As you can see, alma 8 is http/1.1, centos 7 is http/2

regards
Jan
 
As you can see, alma 8 is http/1.1
Try following:
1. Create at least 1 domain in Plesk.
2. Execute 'plesk bin http2_pref enable'.
3. Check HTTP2 again using curl.
 
Back
Top