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

  1. P

    Resolved My Plesk interface is totally broken, can't connect to plesk

    WELL "plesk repair all" put correctly plesk, I gave access, thank you !!
  2. P

    Resolved My Plesk interface is totally broken, can't connect to plesk

    Never tried, in fact I did not rent the server at first. I just continued the work of the previous person and I have no other access than the Plesk interface. But as the update totally broke Plesk and I can not connect anymore it's really **** I tried to repair with ur commands, but there is a...
  3. P

    Resolved My Plesk interface is totally broken, can't connect to plesk

    How can I restart the server ? (clean history and cache did not give anything)
  4. P

    Resolved My Plesk interface is totally broken, can't connect to plesk

    Hello, I updated Plesk from my interface, but once the installation was finished, my interface was totally broken (see screenshot). So I do not have access to anything because I can not even connect to it anymore. How to do ?
  5. P

    Issue My website hosted with Plesk is unreachable

    Hello, I think it's probably a DNS problem. When I try to go to my site (www.setis-sarl.fr), I have the following error: ERR_NAME_NOT_RESOLVED. I searched the Internet and checked the DNS setting of the domain and I do not see any error ... (Sorry for my english) Do you have any solutions to...
Back
Top