Page was served from Nginx on ReactOS | Hacker News Reader

Page was served from Nginx on ReactOS

reactos.aaron.cc

79 pointstimeoperator49 comments

Is that why it's not working?

I can see the page just fine, pretty cool!

Most likely the HN Hug of Death® had gone into effect. It's capable of incapacitating any sort of system without load balancing as soon as that system is linked from the front of Hacker News.

When did the Slashdot effect get renamed to Hug of Death? Anyway, 'tis broken for me too.

There must be quite a few hits on your website when HN links it. nginx out of the box can handle quite a lot of connections, assuming that it isn't trying serve something too complicated on each one.

I believe the phrase originated from Reddit many years ago, where the audience isn't fully familiar with the phrase's previous incarnation.

Since then it has been reappropriated widely on HN and Imgur and any place where people gather and unwittingly cause a denial of service with the best of intentions.

Thank you. I can't say I've been keeping up with my memes n that. The damn kids must have grown up or something!

I have to say, it is quite fun watching words, phrases and ideas being made up on the fly at a prolific rate these days. I can still remember reading about memes in a Richard Dawkins book and a few years later the concept was coerced wholesale by the internets. I still remember thinking "what the fuck is a roflcopter" and then suddenly achieving enlightenment. My granddaughters were born with thumbs that can doom scroll.

Nowadays are properly weird and will continue to get weirder. Despite that it will also continue to be normal.

> I can still remember reading about memes in a Richard Dawkins book and a few years later the concept was coerced wholesale by the internets.

You and I both! It's fascinating.

A communal denial of service

Dare i say, a cDoS

> When did the Slashdot effect get renamed to Hug of Death?

Probably around then time when reddit really started to take off, so I'd guess early 2010s.

If you’re just serving static HTML, HN should not be a problem. It’s only if you’re running code (and database queries) for every request that your server might go down in flames.

This might not work the same for a fresh port on an alternative system. For example: I have no idea how many open connections reactos could handle on the kernel-side with a standard config.

My blog was hugged once. Static webpage served with golang's net/http. Not more than 2% cpu load (single core), 20-30 requests/second. The problem was the default number of file descriptors. Once bumped that, all went well for the next few hours.

Hasn't collapsed, you just need to access it through HTTP instead of HTTPS.

> without load balancing

HN itself runs on one average sized server. This looks like a blog serving static content which should never go down if you put something like CF in front of it.

  It's capable of incapacitating any sort of system without load balancing as soon as that system is linked from the front of Hacker News.

Not the case. I've had a static site at #1 happily hum along on an AWS small.

It seems to be because HN is forcing HTTPS, it works when using HTTP.

Try this: http://reactos.aaron.cc/

Doesn't work for me either

HTTP seems to work for me.

Here's the screenshot of the full page: https://i.imgur.com/sqTTF7X.png

Now it's working for me too, must've been the good old HOD. Thank you anyway, much appreciated

Perhaps it was served?

But not for me.

That http link worked for me. Thank you.

I’m the author of the page. It’s now reachable via HTTPS (again).

I think this is what happened:

I experimented with HTTPS on Sunday and actually got it up and running by patching msafd.dll (see https://jira.reactos.org/browse/CORE-14486 and https://github.com/reactos/reactos/pull/4086).

While the page was running on HTTPS, @timeoperator must have posted this (without me realizing it). Shortly after, the site was down due to the HN Hug of Death®. However, at the time, I thought it had something to do with my recent HTTPS change, so I rolled it back. As a result, the HTTPS link posted here stopped working.

In addition, I wanted to be smart and added a Strict-Transport-Security header:

  add_header Strict-Transport-Security 'max-age=31536000; includeSubDomains; preload' always;

So people who had accessed the HTTPS version (while it was active for a few hours) would never see the non-HTTPS version again.

I didn’t expect it to get so much attention, so next time I attempt something like this, I’ll perform proper load tests, have a dev deployment in place, and check access logs more often!

Seems to have collapsed, but archive.org has a snapshot.

https://web.archive.org/web/20220811232234/https://reactos.a...

Hasn't collapsed, you just need to access it through HTTP instead of HTTPS.

Nope, server is accepting connections but isn't sending anything in response to requests:

  $ curl -v http://reactos.aaron.cc/
  *   Trying 136.244.80.24:80...
  * Connected to reactos.aaron.cc (136.244.80.24) port 80 (#0)
  > GET / HTTP/1.1
  > Host: reactos.aaron.cc
  > User-Agent: curl/7.79.1
  > Accept: */*
  >

(no response within 60 seconds)

Over the last few months we've seen so many "Page served from..." and most of them are just DOA.

Why can't people put a little effort and host those pages on their hardware/software of choice but at least put them behind some CDN (at least for static resources)?

Because when people do serve them from behind a CDN people rush to the comments to lambast them for not serving every request from the system in question.

Which, I mean, I think is fair tbqh.

This.

Part of the challenge for me was to avoid any proxies and and have all requests go directly to the ReactOS system.

I’m totally aware that this doesn’t make any sense in a real-world scenario.

Maybe it wasn't meant for HN, but actually for someone's blog that only gets a few hundred hits a day if it's a very successful blog. Going out on a limb here.

This is HN’s fault this time: it’s forcing HTTPS which the site doesn’t support.

Try this, and it’ll work: http://reactos.aaron.cc/

Surely in this day and age one would set up https, that too on a website related page

Just for this there would be no point.

Possibly SSL is not something that's quite that easy to set up on ReactOS yet?

Probably doesn't have a letsencrypt client.

Maybe there's no SSL/TLS library that works on it at all.

Maybe someone can put Forth into it. :)

Hi, I’m the author of the page.

> Probably doesn't have a letsencrypt client.

Right, Certbot doesn’t work because of an issue with Python, however, it’s easy to generate the certificates elsewhere and inject them into the virtual machine.

> Maybe there's no SSL/TLS library that works on it at all.

There is, but the OS needs to be patched to fix a socket issue (see https://github.com/reactos/reactos/pull/4086 which was never merged because of side effects). The patch does seem to work for my use case and I had actually the site running on HTTPS, but a few hours later it become unresponsive. I didn’t realize that this was probably just due to the HN DOS. I will give HTTPS another shot later today.

There was an attempt:

https://reactos.org/forum/viewtopic.php?f=4&p=146310

It literally says on that static page of no security consequence that they tried to set it up, but it couldn’t negotiate a handshake without stalling.

That doesn't work for me either.

Half the time it's the links says https and the server only does http.

I think people who make these pages neither anticipate nor aim for getting to the front page of HN or other large audience. This us why they don't spend time setting up.Cloudflare and such.

Then somebody posts a link, which, against all odds, gets enough upvotes, et voilà, their hardware is melting under the load

Exactly! I had only posted the link on www.reddit.com/r/reactos and didn’t expect it to get attention from a wider audience :-) Also, I deliberately avoided CDNs and caches to see if the source system can handle the load. I know that this woudn’t make any sense in real-world scenario, but for this project, this was part of the fun.

because the intent of the post is exactly to show that it can be served, not that it can handle a huge amount of traffic HN causes.

The HTTP version works fine for me, HTTPS got connection reset.

ReactOS is cool, but like any other hobby OS, it's not cool before it escapes the VM and works on real hw.

HTTPS is fixed now.

When I read this, my first thought was that by the time it made it to the front page it already has crashed then I clicked on it and yes indeed.

Yeah, but not necessarily ReactOS’s fault! The machine it’s running on doesn’t have much power as I didn’t expect it to get much attention really. Also see my notes regarding the HTTPS link that was temporarily broken: https://news.ycombinator.com/item?id=32480404

Do not forget to join /r/reactos subreddit, if you are interested in ReactOS project

Missed opportunity that it isn't serving a React.js page.

Reply on news.ycombinator.com