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

  1. E

    Resolved Domain with set to PHP v7.3.* in some cases using vendor PHP 7.0 from OS? [Ubuntu 16.04]

    phpversion() shows 7.3 Everything is OK right now. I had to run composer dump-autoload to generate optimized autoload files on production environment. A little strange because i think my dev machine overwrite some 'incomplette' of this files when I ran 1st request in Laravel...
  2. E

    Resolved Domain with set to PHP v7.3.* in some cases using vendor PHP 7.0 from OS? [Ubuntu 16.04]

    Strange, that's why I decided to ask. Mostly this error made me think this way: in that file we have trailing comma in function call (after parameters), it's look exactly: this verification: php Trailing comma test says syntax is valid from php v7.3. Is it change settings in Plesk web...
  3. E

    Resolved Domain with set to PHP v7.3.* in some cases using vendor PHP 7.0 from OS? [Ubuntu 16.04]

    I'm trying update my old application (upgrade framework version from Laravel v5.4 to v8.* [Laravel v.8 require PHP 7.3]) So far domain was set to php v7.2.34, after upgrade and upload code, I change domain php version to 7.3.27 in Plesk. Application works.. alomost, because sometimes I'm...
See more
Back
Top