Can't access Tomcat using IP address

Question

I'm running a Tomcat 5.5 instance (port 8089) on Windows 7.

The server runs correctly if I open http://localhost:8089/ but it gives me an error (Connection refused) on http://192.168.1.100:8089/

I thought it was a firewall issue, so I disabled it, but I still have no luck.

score 28 · Answer 1 · answered Jan 13 '12 at 11:45

28

You need allow ip based access for tomcat in server.xml, by default its disabled. Open server.xml search for "

<Connector port="8080" protocol="HTTP/1.1" 
           connectionTimeout="20000" 
           URIEncoding="UTF-8"
           redirectPort="8443" />

Here add a new attribute useIPVHosts="true" so it looks like this,

<Connector port="8080" protocol="HTTP/1.1" 
           connectionTimeout="20000" 
           URIEncoding="UTF-8"
           redirectPort="8443"
           useIPVHosts="true" />

Now restart tomcat, it should work

answered Jan 13 '12 at 11:45

Anto Binish Kaspar

1,322
1
14
20

3

with tomcat7, for me to have it working (I mean allowing access from the outside with IP address), I have to also add `resolveHosts="true"` in at the end of the sever.xml file – ptocquin Jan 27 '16 at 13:47
Well. Works It. – Bipul Roy Aug 26 '18 at 15:13
My tomcat is in localhost, and a docker container wants to connect it. For the container, tomcat's IP address is 192.168.0.1:8080, but even after updating the above file, the connection is refused. – Prasannjeet Singh Dec 12 '19 at 15:59

score 23 · Accepted Answer · edited May 20 '15 at 10:15

23

You need to make Tomcat listen to 192.168.1.100 address also.

If you want it to listen to all interfaces (IP-s) just remove "address=" from Connector string in your configuration file and restart Tomcat.

Or just use your IP to listen to that address address=192.168.1.100 in the Connector string

edited May 20 '15 at 10:15

MrTux

32,350
30
109
146

answered Jun 05 '11 at 22:01

McKracken

680
8
17

What if you do not have the address configured? – lalo Mar 01 '19 at 16:47

Ankit Gupta · Answer 3 · 2018-02-08T06:47:02.777

If you are not able to access tomcat from remote, there might be reason that taken port is not open in your machine. Suppose you have taken 8081 port.

On Your windows machine:

Open Control panel-> windows Firewall-> Advance setting->Inbound Rules

Create a new rule: mention Port

Configure your port and then shutdown and start your tomcat and it will be accessible from remote as well.

That port issue majorly comes in AWS machines.

If it is still not working then please check with your administrator that selected port is open for public access or not, if not then open it.

score 16 · Answer 4 · answered Jun 25 '15 at 20:55

If you are trying to access your web app which is running on apache tomcat server, it might be working perfect while you are trying to use it on http://localhost:8080/ , it will not work same if you are trying to access it on your mobile device browser for ex. chrome using http://192.168.x.x:8080/ so if you want to access via ip address on your remote/mobile device , do following settings

Open server.xml file.

Change

<Connector connectionTimeout="20000" port="8080"protocol="HTTP/1.1" redirectPort="8443"/>

to.

    <Connector connectionTimeout="20000" port="8080" protocol="HTTP/1.1" redirectPort="8443" address="0.0.0.0" />

Save the file
Stop and restart the server
Now access on your mobile device using ip address http://192.168.1.X:8080/

You are good to go.

This saved my day. – Carlos López Marí Jul 23 '19 at 12:52 — Carlos López Marí, Jul 23 '19 at 12:52

score 11 · Answer 5 · answered Jun 06 '11 at 01:27

11

New versions of application servers removed the ability of binding to your entire network interface and limited it just to the local interface (localhost). The reason being was for security. From what I know, Tomcat and JBoss implement the same security measures.

If you want to bind it to another IP you can explicitly set it in your connector string:

Tomcat: address="192.168.1.100"
JBoss: you pass in a -b 192.168.1.100 as a command line.

Just remember that binding 0.0.0.0 allows anyone access to your box to access that server. It will bind to all addresses. If that is what you want, then use 0.0.0.0, if it isn't then specify the address you would like to explicitly bind instead.

Just make sure you understand the consequences binding to all addresses (0.0.0.0)

answered Jun 06 '11 at 01:27

Mohamed Mansour

39,445
10
116
90

sure, no problem, it's just a development server – francesco Jun 06 '11 at 06:47
where is the address="0.0.0.0" specified? command line? xml file ?? – WestCoastProjects May 30 '14 at 03:59
1

ok I found it in the server.xml. But 0.0.0.0 is not binding all ports as expected "http-nio-0.0.0.0-8080" – WestCoastProjects May 30 '14 at 04:03

score 3 · Answer 6 · answered Feb 11 '20 at 06:03

No solution mentioned above was solved my problem. My problem was different.

First check is your port is disabled in firewall. Go to Control Panel -> Windows Firewall -> Advance Settings -> Inbound Rules and see any port is blocked.

A sample image is below:

If so then you can unblock the port by following steps:

Step 1:

Here you can see that the port is blocked.

Step 2: Allow the connection -> Apply -> Ok.

That's solved my blocked problem. Happy coding :) :)

score 1 · Answer 7 · answered Jan 28 '16 at 20:47

1

Firewalls are often the problem in these situations. Personally, the Mcafee enterprise firewall was causing this issue even for requests within the network.

Disable your firewalls or add a rule for tomcat and see if this helps.

answered Jan 28 '16 at 20:47

zeroRooter

100
1
6

score 0 · Answer 8 · answered Apr 09 '13 at 11:06

0

Check your windows-firewall feature in control panel. Outbound and inbound port should allow port 8089. (or write a new rule for this- Right hand side, actions - new rules.) it worked for me!

answered Apr 09 '13 at 11:06

Suresh Kumar

1

score 0 · Answer 9 · answered Sep 08 '16 at 14:50

I was also facing same problem on Amazon windows EC2 instance ( Windows Server 2012 R2 ) Then I figured out , it was local windows firewall preventing it . I opened port 80 ( defined port for website ) using windows Firewall with Advance Security .

It resolved the issue .

score 0 · Answer 10 · edited Feb 25 '17 at 15:04

0

Very strange because the firewall caused the issue.

edited Feb 25 '17 at 15:04

Blauharley

4,186
6
28
47

answered Feb 25 '17 at 13:50

amit

1

score 0 · Answer 11 · answered May 07 '20 at 06:14

Windows Firewall cause issue after uninstalling Oracle JDK and installing OpenJDK on Windows Server 2008 R2.

Tomcat 7 and Tomcat 8 not access on other machine after this.

Follow below path to add new rule

 --> Windows Firewall with Advanced Security on Local Computer
 --> Inbound Rule 
 -->Add New Rule 
      with specific port you have required for Tomcat application.

score 0 · Answer 12 · answered Jan 15 '21 at 08:54

Thanks for all answers. For me it was a different issue. I had to set my wireless network to "private". I only need tomcat for network internal use. For some reason although firewall rule was set to allow for all, it does not allow access from within the same network if set to public.

Changing settings in server.xml were not needed in this usecase.

score 0 · Answer 13 · answered May 09 '23 at 13:50

0

To be accessible via IP (1.2.3.4) and hostname (localhost), I changed the Engine line in server.xml to

    <Engine name="Catalina" defaultHost="localhost" Host="1.2.3.4">

using Apache Tomcat/9.0.58 (Ubuntu).

answered May 09 '23 at 13:50

Dominik Kern

146
8

Can't access Tomcat using IP address

13 Answers13

Linked