• 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 a-plesk-forum

  1. A

    Resolved error occurred during the signature verification

    Solved on OS: Debian 11.11 Product: Plesk Obsidian 18.0.70 Update #1 by using below in Terminal
  2. A

    Resolved error occurred during the signature verification

    Hello, I have the same issue, on two independent Plesk instances (one Debian 11, second Debian 12), both start sending the same error regarding PUM at the same day. Any thoughts ? Just waits another week for Plesk update ? I see that due to this I cannot update the whole repo :D in sudo...
  3. A

    Resolved Debian Upgrade 10 to 11 - atomicorp error

    I commented update line in file sources.list.d/tortix-common.list I found that on Debian 11 Atomicorp are still unavaliable -...
  4. A

    Resolved Debian Upgrade 10 to 11 - atomicorp error

    Hello @Peter Debik , Thank you, this is something that I think about, the thing is that today Plesk do not send any warning so ... I will close this and if Warning will appear again I will comment them in Sources. Regards Artur
  5. A

    Resolved Debian Upgrade 10 to 11 - atomicorp error

    Hello, After successful upgrading Debian from 10 to 11, I started receiving below error to solve manually about atomicorp - the tricky part is that we use Comodo before and after upgrade, never use Atomicorp. Any tips how to stop this atomicorp error message ? Error...
  6. A

    Resolved Password protection breaks static files access (404 error)

    Hello, We have set Plesk to update only with safe updates and now I confirm that after updateting to v...51 protected folders stop process files properly and show 404 err plus starts receiving System Updates error for pum is called with arguments: ['--list', '--repo-info', '--json'] with...
Back
Top