mirror of
https://github.com/nektos/act.git
synced 2026-04-26 01:15:51 +03:00
[GH-ISSUE #1878] ::error:: self signed certificate in certificate chain #910
Labels
No labels
area/action
area/cli
area/docs
area/image
area/runner
area/workflow
backlog
confirmed/not-planned
kind/bug
kind/discussion
kind/external
kind/feature-request
kind/question
meta/duplicate
meta/invalid
meta/need-more-info
meta/resolved
meta/wontfix
meta/workaround
needs-work
pull-request
review/not-planned
size/M
size/XL
size/XXL
stale
stale-exempt
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/act#910
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @merlinpaypal on GitHub (Jun 23, 2023).
Original GitHub issue: https://github.com/nektos/act/issues/1878
Bug report info
Command used with act
Describe issue
Erroring out with
::error::self signed certificate in certificate chainon a fairly simple step ofactions/setup-node@v3.I've turned off any VPN that I was using and I still get this same issue. I also disabled setting
NODE_EXTRA_CA_CERTS. Though I wouldn't expect that to affect this runner either.Link to GitHub repository
https://github.com/paypal/paypal-messaging-components/blob/develop/.github/workflows/core.yml
Workflow content
Relevant log output
Additional information
.actrc file
@github-actions[bot] commented on GitHub (Dec 21, 2023):
Issue is stale and will be closed in 14 days unless there is new activity
@dingo-d commented on GitHub (Feb 22, 2024):
I have the same thing
bug report output:
The problem is that I am running
acton a company laptop that inspects the TLS connections in the corporate network, so original certificates are replaced by the company ones.How do I add the company CA to my root CA that will be passed to
act?The bizzare thing is, when I exec into the container created by act
I can run the composer just fine 🤷🏼♂️
I tried running the command
act -j phpcs --container-architecture linux/amd64 --container-options "-v /etc/ssl/certs:/etc/ssl/certs:ro"but I'm still getting the same error.@jonmajorc commented on GitHub (Apr 12, 2024):
I know the issue is stale, but am hoping one of you found a solution to your problem and wouldn't mind posting back here! I am also on a company laptop and suspect the same issue.
@dingo-d commented on GitHub (Apr 15, 2024):
I had to ping my IT department to allow certain URLs, there was no other way.
@mileserickson commented on GitHub (Aug 7, 2024):
I'm experiencing the same issue on a corporate machine that has Netskope.
Has anyone found a workaround?
@ChristopherHX commented on GitHub (Aug 7, 2024):
@mileserickson node is ignoring the system cert store
I suggest to add env
NODE_EXTRA_CA_CERTSto point to your cert bundle filecan be done via
--envas well, if you put it into your repo dir depends on chevkoit beeing the first doing network stuffso
act --env NODE_EXTRA_CA_CERTS=/Users/miles/work/github.com/Tractor-Supply-EA/athena-servers/certs.pemThere is some env to skip tls validation in node as well, don't rember it as it is unsecure.
Tbh. you should create your own docker image with all the certs and that env and use --pull=false to use it
@GeorgeGkinis commented on GitHub (Nov 22, 2024):
Thanks to @ChristopherHX I was able to run (insecurely) using:
@kyluca commented on GitHub (Sep 24, 2025):
Ran into the same issue as above.
Took a while to figure out but the workaround I'm currently using is:
actto use that in place ofubuntu-latestDockerfile
Prepare the build context
Build the image
Use it with act