• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Plesk and Tomcat SSL

FlorianHanke

New Pleskian
Hi!
I am new to this forum but I have a huge problem that needs to be fixed today:
We have the Plesk Panel12.x for Linux running on a root server.
Additionally, we are providing a Webservice on the /var/lib/tomcat6 tomcat on axis2.
Everything worked fine so far using http and port 8080, but if we want to configure tomcat to be reachable on https via any port (preferably 8443, but any other port would work too).
If we set the tomcat port to 8443, the sw-cp-server answers http GET requests for the axis2 admin app, on port 8080 a server called Apache-Coyote/1.1 answers.

Any recommendations/input is very welcome!
 
Back
Top