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

Question Possible to use the Apache tomcat in plesk server?

Hello,

Install Tomcat:
Code:
apt install tomcat10
(available in Debian 12 and 13)

or unpack the official tarball to /opt and create your own systemd service with a dedicated user.

Bind the connector in server.xml to localhost only (address="127.0.0.1", port 8080).
Keep the AJP connector disabled (Ghostcat, CVE-2020-1938).

In Plesk under Domain → Apache & nginx Settings → “Additional Apache directives”, add: ProxyPass / http://127.0.0.1:8080/ and ProxyPassReverse / http://127.0.0.1:8080/.

Use /app/ for a sub-path. On nginx-only setups, use a location block with proxy_pass in “Additional nginx directives”.

Put WAR files into
Code:
/var/lib/tomcat10/webapps

and start with

Code:
systemctl enable --now tomcat10

Alternative without touching the OS: install the Plesk “Docker” extension, run a Tomcat image, and attach it to the domain via the extension’s proxy rule. This is better isolated and survives system upgrades more easily.

Limitations: Tomcat does not run as the Plesk subscription user, so there is no customer isolation, no resource limits, and no panel visibility. It suits your own applications better than shared hosting.

Regards
Tessa
 
Back
Top