41

Inside the system, running on virtual machine, I can access the running server at 127.0.0.1:5000.

Although the 'remote' address of the vm is 192.168.56.101 (ping and ssh work fine), I cannot access the server with 192.168.50.101:5000 neither from the virtual machine nor from the local one.

I guess there's something preventing remote connections.

Here's /etc/network/interfaces:

auto eth1
iface eth1 inet static
address 192.168.56.101
netmask 255.255.255.0

ufw is inactive.

How do I fix this problem?

Jorge Castro
  • 73,717

3 Answers3

57

First of all - make sure that your HTTP server is listening on 192.168.50.101:5000 or everywhere (0.0.0.0:5000) by checking the output of:

netstat -tupln | grep ':5000'

If it isn't, consult Flask's documentation to bind to an address other than localhost.

If it is, allow the traffic using iptables:

iptables -I INPUT -p tcp --dport 5000 -j ACCEPT

From Flask's documentation:

Externally Visible Server If you run the server you will notice that the server is only accessible from your own computer, not from any other in the network. This is the default because in debugging mode a user of the application can execute arbitrary Python code on your computer.

If you have debug disabled or trust the users on your network, you can make the server publicly available simply by changing the call of the run() method to look like this:

app.run(host='0.0.0.0')
11

The best way to do it

flask run --host=0.0.0.0
Hassaan
  • 251
6

I've just had the same issue. To solve it, i updated the way to run the application :

 app.run(debug=True,host='0.0.0.0')

Using host=0.0.0.0 let me access my app through my local network.

To access your flask app all you need to do is in your browser type in:

[your devices ip address]:5000

ie:

192.168.1.255:5000

3kstc
  • 349
Alex andre
  • 61
  • 1
  • 1