Report this

What is the reason for this report?

Cannot access a port remotely but it works locally

Posted on November 7, 2015

I want to access to 9000 port remotely. This is the result for “sudo netstat -ntulp”

Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 127.0.0.1:27017 0.0.0.0:* LISTEN 986/mongod
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 982/sshd
tcp6 0 0 :::9000 :::* LISTEN 4978/docker-proxy tcp6 0 0 :::12201 :::* LISTEN 4960/docker-proxy tcp6 0 0 :::22 :::* LISTEN 982/sshd
udp6 0 0 :::12201 :::* 4970/docker-proxy

So the 9000 port should be accessible remotely. It works locally (both http://localhost:9000 and http://[ip-address]:9000) but when I try to connect remotely (http://[ip-address]:9000) it doesn’t work. Also ufw is disabled.

Can anyone help?



This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

I’m having the same problem, wondering if you remember what you did to solve this problem?

Trying to set up Grafana in Ubuntu, and when I run the same command I get

/var/log/grafana# sudo netstat -ntulp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      1636/sshd
tcp6       0      0 :::22                   :::*                    LISTEN      1636/sshd
tcp6       0      0 :::3000                 :::*                    LISTEN      2964/grafana-server

Glad to hear it was a result of your own network configuration, and the problem is resolved.

Same here…

tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      1498/sshd       
tcp6       0      0 :::8080                 :::*                    LISTEN      9268/node       
tcp6       0      0 :::22                   :::*                    LISTEN      1498/sshd  

but cant access 8080 at all. Even if I bind it to 0.0.0.0

it only works when I start it in docker and expose the ports… then somehow I am able to connect to node running in docker. Anyone has idea what this could be?

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

Get started for free

Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

*This promotional offer applies to new accounts only.