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

  1. V

    Resolved 403 error on one wordpress site but not in others

    At first I didn't search for it as it is still a bit intimidating, but I finally did and came to see it was a problem caused by the all in one security plugin. I disabled it and deleted all related directives in the .htaccess file and I was able to use the login page again. Thanks a lot
  2. V

    Resolved 403 error on one wordpress site but not in others

    Can someone help me here please?
  3. V

    Resolved 403 error on one wordpress site but not in others

    Hey, thanks for your reply. It seems I'm not quite there yet because the site is accessible in the frontend and it is only when trying to access the login page that the error appears, preventing me from accessing the backend. I should have said that before ;) Nonetheless, as suggested in the...
  4. V

    Resolved 403 error on one wordpress site but not in others

    Hi, I'm having an issue in which I cannot access the login page in one of my wordpress sites but I can access others without any problem. The message comes from plesk, not wp: I may have changed some setting in this particular site but I cannot seem to find what that is. As I'm a total...
See more
Back
Top