mirror of
https://github.com/actions/runner.git
synced 2025-12-10 20:36:49 +00:00
bd77ccf34e
* Use 16 to run RunnerService.js
* Execute hashfiles using node16
* Run downloadCert.js using node16
* Run makeWebRequest.js using node16
* Run macos-run-invoker.js using node16
* Run hashFiles.js using node16
* Update tests to use node16
* Update documentation to recommend node16
* Duplicate macos service js fix for 16
* Add PR link
* Revert ADR node change
* Merge node12/16 retainment IFs
* Try both node12 and node16
* Close if
* Revert "Update tests to use node16"
This reverts commit bbca7b9f1c.
* Fix condition
* Unfurl if condition
* Allow user to force a node version
* Format update template
* Comment env var
* Rename vars
* Fix naming
* Fix rename
* Set node ver override if job message has it
* Format executionContext
* Can only receive 'forceNode12' or nothing from FF
No specific node version from server
Co-authored-by: Ferenc Hammerl <hammerl.ferenc@gmail.com>
31 lines
1.0 KiB
Markdown
31 lines
1.0 KiB
Markdown
# Node.js Connection Check
|
|
|
|
## What is this check for?
|
|
|
|
Make sure the built-in node.js has access to GitHub.com or GitHub Enterprise Server.
|
|
|
|
The runner carries its own copy of node.js executable under `<runner_root>/externals/node16/`.
|
|
|
|
All javascript base Actions will get executed by the built-in `node` at `<runner_root>/externals/node16/`.
|
|
|
|
> Not the `node` from `$PATH`
|
|
|
|
## What is checked?
|
|
|
|
- Make HTTPS GET to https://api.github.com or https://myGHES.com/api/v3 using node.js, make sure it gets 200 response code.
|
|
|
|
## How to fix the issue?
|
|
|
|
### 1. Check the common network issue
|
|
|
|
> Please check the [network doc](./network.md)
|
|
|
|
### 2. SSL certificate related issue
|
|
|
|
If you are seeing `Https request failed due to SSL cert issue` in the log, it means the `node.js` can't connect to the GitHub server due to SSL handshake failure.
|
|
> Please check the [SSL cert doc](./sslcert.md)
|
|
|
|
## Still not working?
|
|
|
|
Contact GitHub customer service or log an issue at https://github.com/actions/runner if you think it's a runner issue.
|