Repository navigation
/dist/ returns 500 or is very slow #5302
Description
URL:
https://nodejs.org/dist/latest-v20.x/node-v20.0.0.tar.xz
Browser Name:
wget
Browser Version:
n/a
Operating System:
n/a
How to reproduce the issue:
$ wget https://nodejs.org/dist/latest-v19.x/node-v19.9.0.tar.xz
--2023-04-20 13:08:51-- https://nodejs.org/dist/latest-v19.x/node-v19.9.0.tar.xz
Resolving nodejs.org (nodejs.org)... 104.20.23.46, 104.20.22.46, 2606:4700:10::6814:172e, ...
Connecting to nodejs.org (nodejs.org)|104.20.23.46|:443... connected.
HTTP request sent, awaiting response... 500 Internal Server Error
2023-04-20 13:08:52 ERROR 500: Internal Server Error.
$ wget https://nodejs.org/dist/latest-v20.x/node-v20.0.0.tar.xz
--2023-04-20 13:09:00-- https://nodejs.org/dist/latest-v20.x/node-v20.0.0.tar.xz
Resolving nodejs.org (nodejs.org)... 104.20.23.46, 104.20.22.46, 2606:4700:10::6814:162e, ...
Connecting to nodejs.org (nodejs.org)|104.20.23.46|:443... connected.
HTTP request sent, awaiting response... 500 Internal Server Error
2023-04-20 13:09:04 ERROR 500: Internal Server Error
Sometimes it starts downloading but at a veeerrrryyyy sloooow raaatttteeee, like 8k/s, or stalls completely.
Interestingly, https://status.nodejs.org/ is green but yeah, but no.
Activity
ovflowd commentedon Apr 21, 2023
Hey there 👋 this is a recurring issue. Here are some details: #4495 and details about the latest incident here.
We're working on numerous efforts to alleviate the current infrastructure, such as moving the website to a third-party provider (Vercel).
There are some details about why this happens on these links.
We apologise for any inconvenience 😅
Closing this for now as duplicated and as there's no action besides of what we're working already on.
bnoordhuis commentedon May 5, 2023
@ovflowd I hit this again today. If you want something actionable, https://status.nodejs.org/ should reflect the current flakiness; it's all green now.
ovflowd commentedon May 5, 2023
Sorry, we won't update the status page because one or two persons are hitting an occasional error that happens rarely. We're working behind the doors on actionable, but the flakiness level is irrelevant enough to be an actual concern.
bnoordhuis commentedon Jun 28, 2023
@ovflowd it's late June now and I'm still hitting this regularly.
ovflowd commentedon Jun 28, 2023
bnoordhuis commentedon Jun 28, 2023
ovflowd commentedon Jun 28, 2023
ovflowd commentedon Jun 28, 2023
ovflowd commentedon Jun 28, 2023
bnoordhuis commentedon Jul 7, 2023
As a bit of user feedback, I don't think the average visitor can be expected to understand that those pinned issues are about the 5xx errors he or she is seeing. Their titles are way too oblique; they read like developer todo lists, not operational status reports.
My suggestion: pin an issue with an explicit title, like "5xx errors / download problems".
Sure, but then you just close those as duplicates.
Oh, only for the last 13 years or so.
bmuenzenmeyer commentedon Jul 7, 2023
it costs us nearly nothing to pin an issue. I am going to do so on #4495
will also edit that issue body with https://nodejs.org/en/blog/announcements/node-js-march-17-incident
ovflowd commentedon Jul 7, 2023
Thanks @bmuenzenmeyer appreciate that!
ovflowd commentedon Jul 11, 2023
FYI @bmuenzenmeyer we pinned the issue 🙇 thanks for your patience on this matter 🙏