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

  1. PDXMember

    Question Is there a way to expand on a 500 error?

    I am attempting to troubleshoot a script import for Joomla to import from Wordpress to Joomla. When doing this, I am getting a 500 error in the logs, but it is only descriptive enough to indicate the script name. Is there a way to expand this some more so I can see what the cause of the 500...
  2. PDXMember

    Issue Let's Encrypt nameserver certificate creation failure

    No, but I think this might be the issue. <html> <head><title>301 Moved Permanently</title></head> <body bgcolor="white"> <center><h1>301 Moved Permanently</h1></center> <hr><center>nginx</center> </body> </html> Digging now for where to change this in Plesk. I think it is redirecting , but...
  3. PDXMember

    Issue Let's Encrypt nameserver certificate creation failure

    Any other ideas anyone?
  4. PDXMember

    Issue Let's Encrypt nameserver certificate creation failure

    I guess I should point out - the main site that I am hosting is my blog which is running Wordpress. :) The ns1.mydomain.com is the main URL for the Plesk installation.
  5. PDXMember

    Issue Let's Encrypt nameserver certificate creation failure

    I am getting the following error when trying to secure Plesk Onyx 17.5.3 Update #6: Error: Execution letsencrypt-hostname.sh has failed with exit code 1, stdout: , stderr: [2017-05-28 21:55:23] ERR [extension/letsencrypt] Execution of...
See more
Back
Top