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

domain

  1. W

    Resolved Rest api breaking change with 18.0.18 #4 ??

    Hello, I'm using Plesk rest api for years to create domains. Now, i cannot set anymore php_handler_id, www_root or shell. Maybe also some others things i didn't notice yet. Domain is created, but those values are not set. On 18.0.18 #3, is still working, with same json { "name"...
  2. kristobal1969

    Resolved Error messages with let's Encrypt when 1 serveur for main domain and another serveur for subdomain or mails

    Hello, I receive each day a message from Plesk telling that the domain is not secured though it is (on all domain and subdomains). in this exaple ngpark.fr and www.ngpark.fr are on the server with ip 217.160.0.52. They have their own certificate on that server (i do not manage this server). but...
  3. Fahad009

    Resolved Plesk DNS not responding externally – Registrar says nameserver did not respond (Windows Server)

    Hello everyone, I’m running Plesk on Windows Server and using Plesk to manage DNS for my domain. My domain registrar is WebHostBD, and I have configured my own nameserver: ns1.mydomain.com → 203.76.124.70 (my server public IP) However, when I try to set this at the registrar, I get the...
Back
Top