Message Boards

Tomcat running but i can't access through the server ip (server_ip:8080)

Ferran Bernal, modified 3 Years ago.

Tomcat running but i can't access through the server ip (server_ip:8080)

New Member Posts: 5 Join Date: 6/20/14 Recent Posts

I´m setting up a Liferay environment on an ubuntu machine with centOS.

In summary, the steps have been, install JDK, install Liferay, add JAVA_HOME to the setenv.sh file and start the tomcat. All these steps have gone well, and the logs end as follows:

03-Nov-2020 10:39:42.243 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in [76,207] milliseconds

But when I try to access the server's IP through port 8080 (which is the default that my Liferay has), it doesn't work.I'm getting the following error in my browser.

This site can’t be reached

[SERVER_IP] took too long to respond.

Try:

ERR_CONNECTION_TIMED_OUT

Am I missing some step in the process? 
Thank you in advance.

 

thumbnail
Olaf Kock, modified 3 Years ago.

RE: Tomcat running but i can't access through the server ip (server_ip:8080

Liferay Legend Posts: 6403 Join Date: 9/23/08 Recent Posts

Did you try any of the suggestions given? Which IP are you trying to access?

You can alternatively also try http://localhost:8080 from the computer that Liferay is running on.
You should make sure that the computer that Liferay is running on doesn't have a firewall.

Also: "An Ubuntu machine with CentOS" doesn't really make sense. Let's just say you're running Liferay on Linux, and you're trying to access it from a Windows machine. Assuming also that the Windows machine is on the same network.

If your Linux installation is within a VM: That requires setup of the network for the VM so that you can reach it from the host or another VM. We'd need to know that setup as well, in case you are running this configuration

Ferran Bernal, modified 3 Years ago.

RE: Tomcat running but i can't access through the server ip (server_ip:8080

New Member Posts: 5 Join Date: 6/20/14 Recent Posts

Hi Olaf,

Thanks for your quick response, it was a problem with CentOS firewall.

It seems in the version 7 it works a bit different than in the version 6 which I am more used to work with.

Thanks again,

Ferran