• 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.

Resolved ALPN support for CentOS 6.8

I suggest creating a UserVoice request for the feature.

Tip for Plesk: If there is a feature that is better for speed for safety and a lot more people are waiting for it then they where for docker, AND the competition already has it, you should scramble to implement it and not have customers beg for it via a "uservoice".

The internetgods already have spoken: a faster site with https gets a site in the ranking ... so http2 is becoming a must.

If a competitor has something and your client are asking for it too, then an attitude of "we'll think about it, if you ask for it long enough" is a good way of making sure that your clients start turning to that competition. Specially if there are on the web enough examples on how to do it, even full working solutions. Its not like its re-inventing ext5 or so. Its recompilation of an existing package with a few new parameters.

regards
Jan
 
Back
Top