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

  1. G

    Question HTTP ERROR 500, Plesk dashboard cannot be accessed

    I am using a plesk server via vultr. I am currently unable to access the Plesk dashboard as I am getting HTTP ERROR 500 and I see the message 500 Plesk\Exception\Database as shown in the attachment. I can't even log in via root, and I've tried connecting to the Plesk server via SSH, but...
  2. G

    Resolved I can't Access my Plesk server

    I tried again and solved it. The IP address I knew was wrong, I moved it from banned to trusted and I was able to access it. I really appreciate it.
  3. G

    Resolved I can't Access my Plesk server

    Thank you for taking the time to answer my question. I tried to access Plesk from a phone that is not connected to my Wifi, I was able to access it from my phone. Then I looked at the list to block IP addresses, but my IP address wasn't in IP Address Banning. What should I do?
  4. G

    Resolved I can't Access my Plesk server

    I am using plesk through vultr. However, I am unable to access the plesk server by visiting the following URL. https://158.247.214.220:8443/로그인 And wordpress is not connecting to plesk. 1. i get this message whenever i try to connect to plesk and my 3 domain addresses. Unable to connect to...
See more
Back
Top