• Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is 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.

About Plesk integration with Apache

lyallex

New Pleskian
over the past 4 years I have developed a way of packaging a web application written in Java and deployed to Tomcat as a single, translocatable tar ball
I simply run a script to tar up the application along with all required resources including images, database, working server configuration, currently used JDK etc that
encapuslates the current state of the application. I can transfer the tarball to a new server, unarchive it, polpulate the
database set JAVA_HOME and start Tomcat on port 80 and it just works. It takes about an hour to install the entire application on a new server.
I use Tomcat as the front end server, no Apache httpd required. This application has been running faultlessly for nearly 4 years earning money and rarely falling over.
Currently I have the application running on a CentOS server with Apache httpd turned off running Plesk 8.0. I use Plesk to configure and manage email addresses. This has been serving me well for nearly 4 years.
Recently I had to move the application to a server running Plesk 12 and I can't get Plesk to give me access when Apache is turned off. I configured Apache to listen on port 81
but i still can't access Plesk. Why should this be.
 
Back
Top