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

  1. J

    Issue Update fails: Can not bind a socket to address on port 715

    Hello! I believe you need to update your hosts file so it points the hostname to the private, internal IP address. You say your public/external ip is 123.123.123.123, but what is the internal address? I think the hosts file should look like : <<private/internal IP>> s3.mysite.net John
  2. J

    Issue [PPPM-8101] Scheduled backup fails on 17.8.11

    Hello! Running Plesk Onyx v17.8.11_build1708180301.19 os_Debian 9.0. Have scheduled weekly full backup with daily incrementals. Manual full backup runs without error. After rebooting the server, the first scheduled backup will run without error, but subsequent scheduled backups fail with the...
  3. J

    Plesk 12.0.18 MU#62

    Does not install correctly on Win 2012 R2 server. Sometimes it finished without error, but immediately tries to install again. Nothing is ever updated. Normally finished with an error : [2015-09-01 03:27:16.469432] Unexpected 'class boost::filesystem::filesystem_error' caught...
  4. J

    AWS AMI's for Plesk 12

    This article http://kb.odin.com/en/122222 talks about Plesk 12 AMI's for Amazon EC2. It even provides an AWS Marketplace link. However, these AMI's are nowhere to found on AWS. Have they been removed? Will they be returned? The current AMI's are EC2-classic only and don't support...
See more
Back
Top