Why doesn't HTTPS://hackerne.ws/ work?

1 points by notwedtm ↗ HN
I know it's a redirect URL, but it's the one that I've used forever and I'm curious as to why the redirect only works on HTTP and not TLS?

2 comments

[ 141 ms ] story [ 289 ms ] thread
Port 443/HTTPS unreachable.

curl -I hackerne.ws HTTP/1.1 301 Moved Permanently Server: nginx Date: Thu, 14 Oct 2021 22:01:08 GMT Content-Type: text/html; charset=UTF-8 Connection: keep-alive Location: https://news.ycombinator.com/ Strict-Transport-Security: max-age=0;

curl -I https://hackerne.ws curl: (7) Failed to connect to hackerne.ws port 443 after 5562 ms: Connection refused

openssl s_client -port 443 -host hackerne.ws 139796544140672:error:0200206F:system library:connect:Connection refused:crypto/bio/b_sock2.c:110: 139796544140672:error:2008A067:BIO routines:BIO_connect:connect error:crypto/bio/b_sock2.c:111: connect:errno=111 sudo nmap -sS hackerne.ws Starting Nmap 7.92 ( https://nmap.org ) at 2021-10-14 17:05 -05 Nmap scan report for hackerne.ws (75.126.104.242) Host is up (0.14s latency). rDNS record for 75.126.104.242: f2.68.7e4b.ip4.static.sl-reverse.com Not shown: 997 closed tcp ports (reset) PORT STATE SERVICE 19/tcp filtered chargen 22/tcp filtered ssh 80/tcp open http

Sorry, I should have been more clear. I realize the port isn't open. I'm wondering what design decision led to this, and why it's continued when it's a trivial fix.