Skip to content

Node.js website unavaliable #47120

Description

@TimDaub

Version

No response

Platform

No response

Subsystem

No response

What steps will reproduce the bug?

Screenshot 2023-03-16 at 12 32 19

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

Activity

  1. Mokona59 commented on Mar 16, 2023

    @Mokona59

    i can't even install node me

  2. tniessen commented on Mar 16, 2023

    @tniessen
    Member

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

  3. added
    docIssues and PRs related to Node.js documentation.
    on Mar 16, 2023
  4. ovflowd commented on Mar 16, 2023

    @ovflowd
    Member

    @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.

  5. tniessen commented on Mar 16, 2023

    @tniessen
    Member

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

  6. himself65 commented on Mar 16, 2023

    @himself65
    Member

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

  7. changed the title [-]nodejs docs are broken[/-] [+]Node.js website unavaliable[/+] on Mar 16, 2023
  8. himself65 commented on Mar 16, 2023

    @himself65
    Member
  9. ovflowd commented on Mar 16, 2023

    @ovflowd
    Member

    @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.

  10. ovflowd commented on Mar 16, 2023

    @ovflowd
    Member

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

  11. himself65 commented on Mar 16, 2023

    @himself65
    Member

    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.

  12. TimDaub commented on Mar 16, 2023

    @TimDaub
    Author

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

    seems to work for me again, thx

  13. TheZoker commented on Mar 16, 2023

    @TheZoker
  14. jspasiuk commented on Mar 16, 2023

    @jspasiuk

    Same issue here, also with node docker images :/

  15. tniessen commented on Mar 16, 2023

    @tniessen
    Member

    Please see nodejs/nodejs.org#5149 (comment). Depending on your physical location and depending on which particular file you are attempting to access, you might see unexpected 404 status codes. We expect this to be resolved as we manually purge the cache for popular URLs, which takes a few minutes. The remaining URLs should be resolved within a few hours.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    docIssues and PRs related to Node.js documentation.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions