EDIT: this page explains all: https://news.ycombinator.com/item?id=4761102<p>Accessing https://news.ycombinator.com/ from any browser on my local network returns either a 503 error or a blank page. Of course, I can access the site through a proxy (hello).<p>Curl looks a little strange:<p><pre><code> $ curl -I https://news.ycombinator.com/
HTTP/1.1 501 Not Implemented
Server: nginx
Date: Tue, 30 Apr 2013 09:49:55 GMT
Content-Type: text/html
Content-Length: 174
Connection: close
</code></pre>
I can ping it fine:<p><pre><code> $ ping -c 4 news.ycombinator.com
PING news.ycombinator.com (184.172.10.74) 56(84) bytes of data.
64 bytes from 184.172.10.74-static.reverse.softlayer.com (184.172.10.74): icmp_seq=1 ttl=50 time=152 ms
64 bytes from 184.172.10.74-static.reverse.softlayer.com (184.172.10.74): icmp_seq=2 ttl=50 time=152 ms
64 bytes from 184.172.10.74-static.reverse.softlayer.com (184.172.10.74): icmp_seq=3 ttl=50 time=144 ms
64 bytes from 184.172.10.74-static.reverse.softlayer.com (184.172.10.74): icmp_seq=4 ttl=50 time=144 ms
--- news.ycombinator.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 144.188/148.436/152.573/3.952 ms
</code></pre>
I'm reaching the limits of my network debugging talent. What can I do next?
I can access HN just fine, but I get the same result from curl:<p><pre><code> $ curl -I https://news.ycombinator.com/ -k
HTTP/1.1 501 Not Implemented
Server: nginx
Date: Tue, 30 Apr 2013 09:59:39 GMT
Content-Type: text/html
Content-Length: 174
Connection: close
</code></pre>
You could try doing custom HTTP requests via telnet:<p><pre><code> $ telnet news.ycombinator.com 80
Trying 184.172.10.74...
Connected to news.ycombinator.com.
Escape character is '^]'.
GET /
<html>
<head><title>301 Moved Permanently</title></head>
<body bgcolor="white">
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx</center>
</body>
</html>
Connection closed by foreign host.
</code></pre>
Since HN redirect everything to HTTPS it doesn't tell you much, but it can tell you for example whether a connection to port 80 is going through.<p>Edit: You have to type the "GET /" <return> part, in case that wasn't clear. The rest is server response.
You could try what is detailed here:<p><a href="https://news.ycombinator.com/item?id=4761102" rel="nofollow">https://news.ycombinator.com/item?id=4761102</a>