• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • 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.

Tomcat 8

oKin

New Pleskian
I have Plesk 12.0.18 and i had a working Tomcat 7.
But for my Project i need Tomcat 8 thats why i installed it and now Plesk can not more start Tomcat.

How can i change Plesk to start Tomcat 8 and not Tomcat 7.

Fehler: Unable to make action: Unable to manage service by tomcatmng: tomcatmng: Service /etc/init.d/tomcat7 failed to restart
('--start', 'tomcat')
 
In the process of becoming PCI complient, we we informed of the following CVE, any plans to upgrade Tomcat?
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-3190

Certain AJP protocol connector implementations in Apache Tomcat 7.0.0 through 7.0.20, 6.0.0 through 6.0.33, 5.5.0 through 5.5.33, and possibly other versions allow remote attackers to spoof AJP requests, bypass authentication, and obtain sensitive information by causing the connector to interpret a request body as a new request.
 
Back
Top