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

  1. L

    503 ERROR for just few users

    Thanks for your help! Before reading your reply we tried another procedure, that is working at the moment... anyway we are worried that some automatical plesk update or even a simple operation like the creation of a new domain, could bring the situation back to start. This is the list of our...
  2. L

    503 ERROR for just few users

    Hi everyone, we're facing a really bad problem with our dedicated server wiht Plesk11 (updated to the last version) + php fastgi installed. Many of our users see quite often a 503 Error message and can't see many images, that are phisically present on the server and that are visible my the...
  3. L

    Problem with domain in apache

    The script transvhost.pl moves the files from a wrong directory to the right one if I got it right. But what we need is apache to see the plesk configuration for every domain.
  4. L

    Problem with domain in apache

    Hi, we have a problem with a domain not loaded. Here's the step we took so far: 1. Installed lighttpd 2. Installed Plesk 3. Learnt that Plesk doesn't support lighttpd conf files. 4. Uninstalled lighttpd 5. Installed Apache Now the problem is that plesk doesn't seem to see the domain...
Back
Top