 | 1 | initial version |
I get the same result on my machine:
$ curl http://94.15.100.134/
curl: (7) Failed to connect to 94.15.100.134 port 80: Connection refused
$ curl http://127.0.0.1
curl: (7) Failed to connect to 127.0.0.1 port 80: Connection refused
The latter is because I don't have an HTTP server running on my machine; unless you have an HTTP server running on your machine, you should expect that telnet localhost 80 will return "Connection refused".
Are you certain that that 94.15.100.134 has an HTTP server listening on port 80? If I run Wireshark while running curl http://94.15.100.134, it shows the initial SYN trying to connect to 94.15.100.134, followed by a RST coming back from 94.15.100.134, which is not a sign that 94.15.100.134 has an HTTP server. The same thing happens if I capture on lo0 and try to fetch from 127.0.0.1, so the RST might be a sign that nobody's listening on that port.
| | 2 | No.2 Revision |
I get the same result on my machine:
$ curl http://94.15.100.134/
curl: (7) Failed to connect to 94.15.100.134 port 80: Connection refused
$ curl http://127.0.0.1
curl: (7) Failed to connect to 127.0.0.1 port 80: Connection refused
The latter is because I don't have an HTTP server running on my machine; unless you have an HTTP server running on your machine, you should expect that telnet localhost 80 will return "Connection refused".
Are you certain that that 94.15.100.134 has an HTTP server listening on port 80? If I run Wireshark while running curl http://94.15.100.134, it shows the initial SYN trying to connect to 94.15.100.134, followed by a RST coming back from 94.15.100.134, which is not a sign that 94.15.100.134 has an HTTP server. The same thing happens if I capture on lo0 and try to fetch from 127.0.0.1, so the RST might be a sign that nobody's listening on that port.
Copyright Wireshark Foundation, 2017-2023 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.