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

  1. G

    Question WAF (ModSecurity)

    We had a heck of a time with the Comodo rules the other day. If you use WooCommerce, there's a problem that caused every other page load to give 403 Forbidden for us until I shut it off. The report below is from 2024 and it still isn't fixed, so as has been said, they're not maintaining it...
  2. G

    Forwarded to devs Problem: package plesk-php74-imagick-3.7.0-0redhat.8.220415.1034.x86_64 requires libMagickCore-6.Q16.so.6()(64bit), but none of the providers can be i

    It removes the Plesk version of the dependencies but installs the correct version of ImgaMagick-libs and everything seems happy. It's a clean system, though, so I haven't been able to test ImageMagick afterwards yet. My updates are automatic and I don't know YUM/DNF well enough to set up these...
  3. G

    Forwarded to devs Problem: package plesk-php74-imagick-3.7.0-0redhat.8.220415.1034.x86_64 requires libMagickCore-6.Q16.so.6()(64bit), but none of the providers can be i

    FYI, running update with --allowerasing fixes it, until the next auto-update of Plesk reverts it back. I'll add the exclude and periodically retry without it. yum update --allowerasing
Back
Top