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

  1. W

    Resolved Nginx Config Issue

    Hello, Had an issue today where Nginx was stopped and starting the service failed due to being unable to bind to port 80. After trying numerous things, found the issue was in nginx.conf #user nginx; worker_processes 1; #error_log /var/log/nginx/error.log; #error_log...
  2. W

    Resolved Plesk update issue

    Hello, I am trying to run an update to Plesk on a Cloudlinx system, however getting the following issue: gpg-pubkey-4520afa9-50ab914c gpg(Atomicorp (Atomicorp Official Signing Key) <[email protected]>) gpg-pubkey-1bb943db-511147a9 gpg(MariaDB Package Signing Key...
  3. W

    Plesk 12, Centos 7 and Percona

    Thanks for your reply, think I may of worded the question badly. I don't want to use MariaDB, I want to use Percona, I have already replaced MariaDB with Percona, however now YUM is now throwing up these errors, is there any way around this or do I have to have MariaDB only now for Plesk?
  4. W

    Plesk 12, Centos 7 and Percona

    Hello, I know that MariaDB is now the default for CentOS 7, have just done my first install of Plesk on 7, normally using CentOS 6. Anyway I prefer to use Percona if possible, however how do I get around this issue or are we now forced to only use MariaDB now? ** Found 2 pre-existing rpmdb...
See more
Back
Top