-
Notifications
You must be signed in to change notification settings - Fork 109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Error "fetch failed" when using proxy #814
Comments
Hey @lindeberg thanks for reporting this. If you disable the OpenSSF scorecards does the fetch still fail? |
We experience this issue as well using proxy. Rolling back to actions/[email protected] works. It seems like issue is introduced when upgrading to node 20. |
confirming @gadzet's remak. Note the culprit of this issue as 2 blocked URL's on our firewall:
after a whitelist, we could use |
We are facing the same issue and I can confirm that downgrading from v4 -> v3 solves it. Our runner is behind a proxy. Doing the same requests with curl works just fine. |
Describe the bug
Error "fetch failed" when using proxy on a self-hosted runner with a proxy with least privelege network access, and these domains are allowed:
2024-08-16T06:36:11.3271510Z Dependency review did not detect any denied packages 2024-08-16T06:36:31.3476555Z ##[error]fetch failed
To Reproduce
Steps to reproduce the behavior:
Expected behavior
It should be all good!
Screenshots
Action version
v4.3.4
The text was updated successfully, but these errors were encountered: