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

  1. J

    Resolved PHP sessions don't work because Plesk's PHP is used for one script, the server PHP for another.

    Yup, I just arrived to post this very same response. Cheers.
  2. J

    Resolved PHP sessions don't work because Plesk's PHP is used for one script, the server PHP for another.

    There's nothing like being patronized by an expert without an answer. I'm not calling different domains, or subdomains, or switching between SSL/non-SSL, or anything at all like what you suggested. Had you taken the time to run the test, you'd have seen that for yourself (assuming, of course...
  3. J

    Resolved PHP sessions don't work because Plesk's PHP is used for one script, the server PHP for another.

    I'm a fan of using URI paths to control websites. It's neat and clean, but after upgrading to Plesk 12.5 with PHP 7 it stopped working. So, rather than using example.com?action1=&action2=, I use example.com/action1/action2. What happens is this. Any normal PHP files (e.g...
See more
Back
Top