Question
Why would port 80 come up closed from a digitalocean VPS but not from the web?
If I am on a computer at home, I can go to http://164.92.121.50
And if from a windows or linux computer at home I do
C:\blah>nmap -p80 164.92.121.50
or
$nmap -p80 164.92.121.50
Then it shows as open
And I can do wget 164.92.121.50
However, if I try from a DigitalOcean VPS
It doesn’t work
> root@ubuntu-s-1vcpu-1gb-lon1-01:~# wget 164.92.121.50
> --2022-09-12 05:03:03-- http://164.92.121.50/
> Connecting to 164.92.121.50:80... ^C
>
>
> root@ubuntu-s-1vcpu-1gb-lon1-01:~# nmap -p80 164.92.121.50
> Starting Nmap 7.80 ( https://nmap.org ) at 2022-09-12 05:03 UTC
> Nmap scan report for 164.92.121.50
> Host is up (0.14s latency).
>
> PORT STATE SERVICE
> 80/tcp filtered http
>
> Nmap done: 1 IP address (1 host up) scanned in 1.77 seconds
> root@ubuntu-s-1vcpu-1gb-lon1-01:~#
> `
```
Submit an answer
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.
Sorry, turned out that from my home computer I could access it, but everybody else couldn’t. I had a firewall rule on the VPS that only my IP could access port 80.
I was checking the firewall before but I was only checking the firewall on the VPS I was checking from! I should have checked the firewall on the server itself!
Hello @userdo
You can also double-check if there are no Firewall rules in place that can cause such behaviour.
Regards
Hi @userdo,
Are you sure the port from the DigitalOcean Droplet is not closed and thus not allowing you to reach other ports on different machines?
I see this as the only explanation.