Nodejs.org: Nodejs.org down

Created on 30 Aug 2020  路  4Comments  路  Source: nodejs/nodejs.org

I noticed this as our Travis CI builds keep failing since a few minutes.

Location: Germany

[-] Installing Node 12.16.1...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0*   Trying 104.20.22.46...
* TCP_NODELAY set
* Connected to nodejs.org (104.20.22.46) port 80 (#0)
> GET /dist/v12.16.1/node-v12.16.1-linux-x64.tar.gz HTTP/1.1
> Host: nodejs.org
> User-Agent: curl/7.52.1
> Accept: */*
> 
< HTTP/1.1 301 Moved Permanently
< Date: Sun, 30 Aug 2020 11:42:32 GMT
< Transfer-Encoding: chunked
< Connection: keep-alive
< Cache-Control: max-age=3600
< Expires: Sun, 30 Aug 2020 12:42:32 GMT
< Location: https://nodejs.org/dist/v12.16.1/node-v12.16.1-linux-x64.tar.gz
< cf-request-id: 04e0c629f70000f47849122200000001
< Server: cloudflare
< CF-RAY: 5cae3fbcba71f478-IAD
< 
* Ignoring the response-body
{ [5 bytes data]
* Curl_http_done: called premature == 0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
* Connection #0 to host nodejs.org left intact
* Issue another request to this URL: 'https://nodejs.org/dist/v12.16.1/node-v12.16.1-linux-x64.tar.gz'
*   Trying 104.20.22.46...
* TCP_NODELAY set
* Connected to nodejs.org (104.20.22.46) port 443 (#1)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
} [5 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
* TLSv1.2 (IN), TLS handshake, Server hello (2):
{ [100 bytes data]
* TLSv1.2 (IN), TLS handshake, Certificate (11):
{ [4897 bytes data]
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
{ [589 bytes data]
* TLSv1.2 (IN), TLS handshake, Server finished (14):
{ [4 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
} [70 bytes data]
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
} [1 bytes data]
* TLSv1.2 (OUT), TLS handshake, Finished (20):
} [16 bytes data]
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
{ [1 bytes data]
* TLSv1.2 (IN), TLS handshake, Finished (20):
{ [16 bytes data]
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server accepted to use h2
* Server certificate:
*  subject: OU=Domain Control Validated; OU=PositiveSSL Wildcard; CN=*.nodejs.org
*  start date: Oct 21 00:00:00 2019 GMT
*  expire date: Jan 18 23:59:59 2022 GMT
*  subjectAltName: host "nodejs.org" matched cert's "nodejs.org"
*  issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA
*  SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
} [5 bytes data]
* Using Stream ID: 1 (easy handle 0x55b0431d2ea0)
} [5 bytes data]
> GET /dist/v12.16.1/node-v12.16.1-linux-x64.tar.gz HTTP/1.1
> Host: nodejs.org
> User-Agent: curl/7.52.1
> Accept: */*
> 
{ [5 bytes data]
* Connection state changed (MAX_CONCURRENT_STREAMS updated)!
} [5 bytes data]
  0     0    0     0    0     0      0      0 --:--:--  0:00:15 --:--:--     0< HTTP/2 522 
< date: Sun, 30 Aug 2020 11:42:48 GMT
< content-type: text/html
< set-cookie: __cfduid=df29112b5a2d2e3063b6bcf4ce4037c201598787752; expires=Tue, 29-Sep-20 11:42:32 GMT; path=/; domain=.nodejs.org; HttpOnly; SameSite=Lax
< cache-control: no-store, no-cache
< cf-cache-status: EXPIRED
< cf-request-id: 04e0c62a4b000074cbbc264200000001
< expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
< server: cloudflare
< cf-ray: 5cae3fbd4e4a74cb-IAD
< 
{ [207 bytes data]
100   207    0   207    0     0     13      0 --:--:--  0:00:15 --:--:--    46* Curl_http_done: called premature == 0
100   207    0   207    0     0     13      0 --:--:--  0:00:15 --:--:--    59
* Connection #1 to host nodejs.org left intact

Most helpful comment

All 4 comments

I just checked and it's not down for me. Would you be able to try again using another device?

I'm seeing downloads from nodejs.org also fail with 522 errors (via multiple GitHub Actions)

Anyone still seeing any issues? Looks like the Cloudflare incident is resolved now on their end.

/cc @nodejs/build for visibility

Was this page helpful?
0 / 5 - 0 ratings

Related issues

Drieger picture Drieger  路  3Comments

Aissaoui-Ahmed picture Aissaoui-Ahmed  路  3Comments

celyes picture celyes  路  5Comments

interglobalmedia picture interglobalmedia  路  3Comments

julianduque picture julianduque  路  4Comments