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

  1. P

    Issue Domain Backup Error

    i become an email with this: Domain: DOMAIN.de Plesk Einstiegspunkt: MYPLESKURL.de Beim geplanten Backupvorgang ist der folgende Fehler aufgetreten: Failed to parse task log. Reason: Failed to read data from stream Task log: What can i do? i cant find anything about this error
  2. P

    Resolved SpamAssassin daily update cron exited with return code 4

    Me to. I use Ubuntu 18.04
  3. P

    Resolved SpamAssassin daily update cron exited with return code 4

    When it will be fixed? Every day I become this email with the same error...
  4. P

    Issue error message / email security app / configuration check:

    Have I to register my domain ip on uribl.com?
  5. P

    Issue error message / email security app / configuration check:

    No it's not mine. Nobody registered for me.
  6. P

    Issue error message / email security app / configuration check:

    I don't know what do to. My provider is strato.de. I have a vServer with Ubuntu Linux. I have a stratoserver.net domain that can't be edited... What can I do
  7. P

    Issue error message / email security app / configuration check:

    how can i fix this? i dont know what to do, i need help. I dont understand the failure
  8. P

    Issue error message / email security app / configuration check:

    i have the same error. when i type host -tTXT 2.0.0.127.multi.uribl.com i got: Host 2.0.0.127.multi.uribl.com not found: 3(NXDOMAIN) what can i do ?
  9. P

    Resolved SpamAssassin daily update cron exited with return code 4

    This work not for me
  10. P

    Resolved SpamAssassin daily update cron exited with return code 4

    I have the same issue: run-parts: /etc/cron.daily/60sa-update exited with return code 4
See more
Back
Top