41–50 of 52 posts
Earlier quoted context omitted.
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
Here's the screenshot of the full page: https://i.imgur.com/sqTTF7X.png
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.
> 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.
Is that why it's not working?
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;
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!
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.
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.
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.
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.