• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

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