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

  1. L

    Question No telnet no yum

    Hi! I've know this convo dates back a while now.. but I'm trying to install telnet and I get this error message.. any clues? thx Errors during downloading metadata for repository 'mariadb': - Curl error (28): Timeout was reached for...
  2. L

    Issue mail server not properly configured - leading to block

    Here's the result from spamhaus... so I understand about the server name HELO not being properly setup.. that's will be taken care of.. The issue I have is with the IPV4 record.. this is not an IP that originates from OVH, but one that has been created in Plesk.. but this address doesn't see...
  3. L

    Issue mail server not properly configured - leading to block

    Yeap, that seems to be an issue.. now the problem I have is that the ip addresss that the helo points to is an address I have in plesk, but no on my server host (ovh) .. how do I change this so that the server uses the "real" server ip address? thx
  4. L

    Issue mail server not properly configured - leading to block

    Hello! I am going nuts on this issue.. I've had a mail server for a couple of years now without any issue.. last week I've added a new domain that needed mail services as well.. since then I've been blacklisted in spamhaus... Now, the part that I'm pulling my hair over... I wanted to dispute the...
See more
Back
Top