• 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 problem with port number, very urgent, please help!

R

raybristol

Guest
Our website just online today, we use jsp to do the payment section, however we just found out a problem, two questions:

1. I use plesk to deploy a war file, after i deploy it, i can view it using 9080 port number, for example: http://www.spottheball.tv:9080/payment/input.html
however, people cannot access to it with port number 9080, but I can (maybe bacuse the firwall of the live server only allow registered ip to access this port?)

2. however, people can view it with default port, ttp://www.spottheball.tv/payment/input.html , but this is not immediately availiable to user, it became immediately after a while I deployed the war file!

I wonder why this is happening ? what's i having this strange problem with port number?

please help, really urgent, our site just go live!
 
Back
Top