Skip to content

Unable to set up Node 18 using self-hosted runners #933

Closed
@prateekg17

Description

@prateekg17

Description:
Unable to set up Node 18 using self-hosted runners, we get a timeout while trying to download Node 18.19.0 from
github.com is set up for egress for the self-hosted runner

Action version:
v3

Platform:

  • Ubuntu

Runner type:

  • Self-hosted

Tools version:
node version = v18.19.0

Repro steps:

  • Use self-hosted runner with a Linux machine which has the configuration [self-hosted, linux, X64]
  • Configure github.com as egress for the self-hosted runner to allow it connect with github for Node dependencies.
  • Define a workflow which makes use of self-hosted runner, checks out the code and then uses the set up node action
  • We are using the basic action i.e.
    image

Expected behavior:
Node is set up and we are able to progres further.

Actual behavior:
We receive a timeout error after retrying for 3 times. The following error is received:

Acquiring 18.19.0 - x64 from https://github.com/actions/node-versions/releases/download/18.19.0-7042590257/node-18.19.0-linux-x64.tar.gz
##[debug]Downloading https://github.com/actions/node-versions/releases/download/18.19.0-7042590257/node-18.19.0-linux-x64.tar.gz
##[debug]Destination /_work/selfhosted-dev-runner-*************_temp/************************
##[debug]set auth
Request timeout: /github-production-release-asset-2e65be/255649393/c5b966e9-33ce-4377-ba6e-ceae6db76f90?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=***********************%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20240105T123409Z&X-Amz-Expires=300&X-Amz-Signature=*********************************&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=**************&response-content-disposition=attachment%3B%20filename%3Dnode-18.19.0-linux-x64.tar.gz&response-content-type=application%2Foctet-stream
Waiting 13 seconds before trying again

Falling back to download directly from Node
Error: Client network socket disconnected before secure TLS connection was established

It might be a trivial issue but I'm unable to figure out what might be restricting the runner to download it if egress is already set up. Any help is appreciated.

Metadata

Metadata

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions