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

HTTP/2 not working on browsers

@trialotto thank you so much for all the help. I've been trying to sort this out and every one of your answers is several google searches away from understanding it for me so sorry if I reply a bit late. I am still not getting it.. even in FF that you mentioned.

@learning_curve but it would be right to fix this yes? I think I will go for let's encrypt wildcard/multi-domain. Is it possible to solve this within plesk or the letsencrypt extension? if you have any online resource on how to set this up I'd love to read up. Thanks again!
 
@TonyD You can fix it if you want to, yes. In our case, it's not by using the (current) Plesk Extention, but by sourcing the Let's Encrypt certificate from an external provider. It's explained in the Plesk Extention thread in this forum HERE That link is to Post 184, so progress through to Post 187 and that gives some context, plus a link to an external Let's Encrypt provider.
 
Back
Top