Live data from Hacker News

Page was served from Nginx on ReactOS

reactos.aaron.cc

31–40 of 52 posts

Re: Page was served from Nginx on ReactOS

#31

Earlier quoted context omitted.

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

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. :)

Re: Page was served from Nginx on ReactOS

#32
post #16

Earlier quoted context omitted.

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

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.

Re: Page was served from Nginx on ReactOS

#33
post #12
post #8

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.

Re: Page was served from Nginx on ReactOS

#34
post #4

Is that why it's not working?

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.

  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.

Re: Page was served from Nginx on ReactOS

#35
post #5

Earlier quoted context omitted.

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.

A communal denial of service

Dare i say, a cDoS

Re: Page was served from Nginx on ReactOS

#36
post #8

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)?

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

Re: Page was served from Nginx on ReactOS

#39
post #6
post #4

Earlier quoted context omitted.

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.

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.

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.
Post reply on HN