• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Search results

  1. W

    Issue WordPress core upgrade failed

    I can replicate the following issue on 4 different servers CentOS 7/8 based with Plesk Obsidian Version 18.0.38 Update #1 + the latest WordPress toolkit 1. all updates to WordPress 5.8 to 5.8.1 are not being performed. After you click the update button, the system shows the update is installed...
  2. W

    Resolved Mailman not functional after server reboot

    We are running Plesk Onyx (#24) on CentOS 7.4 and each time after we reboot the server Mailman stops working. Messages sent to mailing lists are sent but never received. Uninstalling/Reinstalling Mailman via Plesk solves the issue and immediately after reinstall all the previously sent messages...
  3. W

    Resolved Emails not readable on Microsoft Outlook after MU #14

    Hi there, Immediately after we installed MU #14 for Plesk Onyx all the clients we host on that specific machine and use Microsoft Outlook (regardless of its version) to read their emails are reporting that messages are not readable by the email software. The output is similar to the attached...
  4. W

    Issue WordPress Toolkit (cached data)

    I've just realised that after each action performed in WordPress Toolkit (update core/plugin/theme), data is saved under /var/www/vhosts/domain.name/.wp-cli Practically each plugin/core/theme version is saved in there, for each update action. Shouldn't this cached data be removed after the...
  5. W

    SpamAssassin update from 3.3.1 to 3.4.1

    Hi there, I am just wondering if there is any possibility to update the SpamAssassin package which comes with Plesk 12 from 3.3.1 (obsolete version built in 2010) to the latest one which at the moment is 3.4.1? Many thanks for your answers or thoughts.
  6. W

    PHP 7.0 ->7.0.1 update via MU kills all WP websites

    After updating Plesk from 12.5.30 #15 to #18 (which also updated PHP 7.0 to 7.0.1), all the WordPress websites hosted on the server are displaying a 500 error. The logs are similar in all the situations 2016-01-05 10:42:20 Error 86.124.185.88 Premature end of script headers: index.php Apache...
  7. W

    WordPress Toolkit issues after upgrade to 12.5.30

    The "Check Security" procedure displays that all the WordPress instances are not secured (marked with a red exclamation sign) even if they were all secured before. After you click a "not secured" installation, the system displays that actually everything OK and marks that specific installation...
  8. W

    Cannot access Backup Manager (Tools & Settings or any Subscription)

    Good evening, After a successful upgrade from 11.5.30 to 12.0.8 the Backup Manager cannot be accessed anymore. The system replies with: Internal error: Failed to parse response. Reason: Failed to read data from stream Process output: Message Failed to parse response. Reason: Failed to...
  9. W

    Failed update from 11.0.9 to 11.5.30

    Tried to update Plesk from 11.0.9 update #60 to the latest stable version, which is 11.5.30. The process collapses shortly after the start, with the attached error log. Probably the most important lines are at the end. Does anybody know how to solve this issue? Thank you in advance for...
Back
Top