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

  1. T

    Resolved Error updating from 18.0.44 to 18.0.51 on ubuntu 20

    Hello - I am receiving the same: W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: Index of /PMM_0.1.11 focal InRelease: The following signatures couldn't be verified because the public key is not...
  2. T

    Resolved Plesk Monitoring = An unexpected error occurred

    After updating Plesk to the latest version - all is working again. Thank you, Troy
  3. T

    Resolved Plesk Monitoring = An unexpected error occurred

    Thank you - I had seen the "update-ca-certificates" and tried this - but no joy. The command returned: # update-ca-certificates Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... done. And the problem persists. I see your...
  4. T

    Resolved Plesk Monitoring = An unexpected error occurred

    Description: Ubuntu 20.04.6 LTS Release: 20.04 Outbound 443 confirmed working (not on Fail2Ban or in iptables) And I'm still getting the "An unexpected error occurred" There is nothing in panel.log or syslog that refers to this or to api.monitoring360.io Open to suggestions - Many...
See more
Back
Top