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

Recent content by Alex Bosch

  1. A

    Resolved How to add response headers to the port 8443?

    I already solved that with the help of this article: https://support.plesk.com/hc/en-us/articles/360016977493-How-to-add-headers-to-a-Plesk-page- Yesterday I tried it but failed because a lack of a ; Now it is working!
  2. A

    Resolved How to add response headers to the port 8443?

    Hi, @Peter Debik Thank you for your answer. I don't know how, but HSTS it is already applied on the 8443 port URL, but not other security headers that are needed. I don't want to mess, but without these headers, Security Scorecard and other security checkers flag my server with security...
  3. A

    Resolved How to add response headers to the port 8443?

    Hi; I use a subdomain as a hostname and I set the access to the plesk interface with it. I managed to add http security headers when accessing to plesk with the subdomain URL, with the help of this article: Resolved - How can I adjust HSTS in Plesk? But when I try to access to plesk via...
See more
Back
Top