Node.js website unavaliable

[TimDaub]

Version

No response

Platform

No response

Subsystem

No response

What steps will reproduce the bug?

• go to: https://nodejs.org/api/
• click on "Assertion testing"
• https://nodejs.org/api/assert.html shows a 404

How often does it reproduce? Is there a required condition?

always

What is the expected behavior? Why is that the expected behavior?

shows the docs page

What do you see instead?

404 error

Additional information

No response

[Mokona5901]

i can't even install node me

[tniessen]

@ovflowd This sounds like it could be due to nodejs/nodejs.org#4991?

[ovflowd]

@tniessen seems to be working for me. Both on CloudFlare and non-CloudFlare. But this page was broken a few hours ago indeed.

I think we can close this for now and keep monitoring.

[tniessen]

@TimDaub Is this still an issue, even after a hard refresh?

[himself65]

This also causes all binary releases to be unavailable for all GitHub CI. please fix this ASAP

[himself65]

related nodejs/nodejs.org#5149

[ovflowd]

@himself65 please mind your tone 😅 we're working on the clock for the last 3-4 hours non-stop.

The issue is something on CloudFlare side, due to cache invalidation issues, mixed with our server becoming unresponsive because of the sheer amount of requests coming in and the clients also caching these 404s.

So it's a mix of a lot of things, and right now we're working on all angles but we're sadly outmanned.

[ovflowd]

Also, the issue doesn't affect all binaries neither all releases. It is a spotty issue that changes from time to time.

[himself65]

please mind your tone 😅 we're working on the clock for the last 3-4 hours non-stop.

The issue is something on CloudFlare side, due to cache invalidation issues, mixed with our server becoming unresponsive because of the sheer amount of requests coming in and the clients also caching these 404s.

So it's a mix of a lot of things, and right now we're working on all angles but we're sadly outmanned.

Sorry for the rudeness.

[TimDaub]

@TimDaub Is this still an issue, even after a hard refresh?

seems to work for me again, thx