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

  1. C

    Upgrade fails on Plesk Onyx Version 17.8.11 Update #7

    Hello again, upgrader_config_current_timestamp contained value: 20140511180000 I changed it to 20180301000200, because there's Onyx 17.8.11 on the host. The last past of your KB worries me "a bit". Especially when I saw the "New installation of product(s) should be performed on clean servers...
  2. C

    Upgrade fails on Plesk Onyx Version 17.8.11 Update #7

    Hi there, the same error repeated today. It stated with a nice mail from Plesk telling us "Plesk update failed" during the night. Sure enough, in /var/log/plesk/install/plesk_17.8.11_installation.log there is this error again: ERROR 1146 (42S02) at line 1: Table 'psa.WordpressInstances'...
  3. C

    Upgrade fails on Plesk Onyx Version 17.8.11 Update #7

    I think I've found & fixed the problem. "apt-get upgrade" showed a possible update of various plesk-* packages: *** The following packages will be upgraded: plesk-repair-kit plesk-service-node-utilities plesk-skins psa-locale-base-en-us 4 upgraded, 0 newly installed, 0 to remove and 0 not...
  4. C

    Upgrade fails on Plesk Onyx Version 17.8.11 Update #7

    Sadly no - that's the first thing I tried and it didn't help. That suggestion is on the link I posted as well and then it didn't help either. I wanted to paste that output showing everything is fine, but now I get a warning about an extra table: *** Checking the Plesk database using the native...
  5. C

    Upgrade fails on Plesk Onyx Version 17.8.11 Update #7

    Hi there, we have a problem with the last Plesk upgrade. First time the upgrade failed because of a missing WordpressInstance table. No idea why it was missing, but we did find this link and created the table, that now looks like: MariaDB [psa]> SHOW COLUMNS FROM WordpressInstances...
Back
Top