• 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 Implementing HTTP Public Key Pinning on Plesk/Onyx

Hi UFHH01,
Are you saying that it's not possible to implement HTTP Public Key Pinning on Plesk/Onyx?

Thanks
 
Hi Chrisa,

you may add as many additional headers for your domain(s), that you wish to. For such ( unique ) configurations, you have the option to use "Additional directives" over your Plesk Control Panel, at :

=> HOME > Subscriptions > YOUR-DOMAIN.COM > Apache & nginx Settings
 
Hi UFHH01,
Thanks. I did see Scott's detailed instruction but wasn't sure if they would apply to a plesk implementation.
 
If HPKP is activated in PLESK Obsidian it seems it sets it's own report uri.
How can I change that to mine ?
 
Back
Top