actions/setup-node@v1 timing out?


Seeing the same - it affects around 50% of my actions. (So some work, some don’t - and when re-running, the same ones don’t seem to fail)

Experiencing similar issues in multiple repos:

1 Like

Also happening to me:

Issue for us as well starting around 10 hours ago. 

Screen Shot 2019-10-23 at 16.10.31.png

even worse can’t see my logs

Hi everyone! Thanks for raising visibility here. I’ve alerted our engineers internally and they’re investigating. I’ll follow up here once I hear more from them, though we can’t make any promises for when this will be resolved.


Is the action failing or is the download from timing out?

At this time most downloads of node via are timing out or otherwise failing on all my machines, not just in Actions

Also see which may provide notice of mitigation earlier than we can

1 Like

Hello again! Our engineers let us know this should now be resolved. If anyone else is seeing this again, an updated set of screenshots and URLs to the affected workflow runs in public repositories would help us investigate further!

1 Like

The issues are back :frowning:

I am seeing setup-node@v1 running for more than 7-10 mins without success. It just hangs there. 

Same. 12 min+ still going strong.

Same for us. Issue is back…


I’m running into the same issue. Here’s an example:

The problem seems to be an outage on Node.js’s website. See and

I think it’s related to nodejs download url, not github actions.

Here is the code used by setup-node action:

1 Like

This seems to be happening again:

Run actions/setup-node@v1
    node-version: 13.x
    always-auth: false
<head><title>522 Origin Connection Time-out</title></head>
<body bgcolor="white">
<center><h1>522 Origin Connection Time-out</h1></center>

Edit: Might be a cloudflare issue:

Update - We have identified an issue with a transit provider which is causing 5xx class HTTP errors, such as HTTP 522, 502, 503.

This is affecting all data centers that make use of this transit provider and we are working on implementing mitigations to alleviate this issue.
Aug 30, 11:57 UTC