• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved TOMCAT URL

Pedro Reinoso

Basic Pleskian
Hello,

We want to implement a TOMCAT in our dedicated server and we are having problems when installing the TOMCAT on Server in CentOS 7.

The issue we have is with the URL i have read some post that specify that the URL is as follow:

http://IP_ADDRESS:9080

when we browse to the address above, we got this error:

This 10.160.4.4 page can’t be found
No webpage was found for the web address: http://10.160.4.4:9080/
HTTP ERROR 404

Any different approach or help?

Thanks,
 
Hi @UFHH01

Thank you for your response, i have done what you recommended me, all was fine,

# netstat -plant|grep 9080
tcp6 0 0 :::9080 :::* LISTEN

but if i try browse:
10.160.4.4:9080 <-- Local IP
Public_IP:9080 <-- Nothing
HOSTNAME:8080 <-- NOTHING
1270.0.0.1:9080 <-- Nothing
 
Hi Pedro Reinoso,

I meant doesn't make any difference
First of all, pls. note that using a local IP, or "localhost" is pretty useless, when you try to open such IPs with your browser at home. I already mentioned:
your used IP resolves to nowhere: => Reverse DNS Lookup for 10.160.4.4
... which should point you to the fact, that internal IPs and localhost can't be reached over the world wide web, only over your private network.

Public_IP:9080 <-- Nothing
HOSTNAME:8080 <-- NOTHING
Sorry, we are unable to investigate the issue, if you desire to anonymize the public IP or the FQDN.
We could only suggest to check your firewall settings and possible iptables bans.
 
Back
Top