Facebook
Twitter
thinkingcap
Basic Pleskian
Advisor states HTTP/2 isnt enabled, HTTP/2 is running all sites on this server.
Pressing "Enable" does nothing
Pressing "Enable" does nothing
-
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 -
Please beaware of a breaking change in the REST API on the current Plesk release (18.0.62).Starting from Plesk Obsidian 18.0.62, requests to REST API containing the Content-Type header with a media-type directive other than “application/json” will result in the HTTP “415 Unsupported Media Type” client error response code. Read more here
Resolved Advisor cant enable HTTP/2
- Thread starter thinkingcap
- Start date
learning_curve
Silver Pleskian
This is a well known bug in 17.8.11. The "Advisor" wrongly advises
the true http/2 status and... it's never been fixed. We asked the question elsewhere i.e. if this specifc Advisor bug had been fixed for Obsidian but our question wasn't answered. To be fair, quite a few bugs that are still in 17.8.11 have, actually, been fixed in Obsidian, or so the officlal Plesk records to date, do indicate. Your post would indicate that this one has not been fixed... so maybe that's why we never got an answer
We haven't upgraded to Obsidian - yet - as we're still reading through other people's experiences so far.
thinkingcap
Basic Pleskian
I've only upgraded 1 server with a dozen sites on it to see how things go.
No show stoppers so far but a few annoyances.
No show stoppers so far but a few annoyances.
Similar threads
