GitHub Action self-hosted runner fails configuration for private repository #25567
-
I’m trying to setup a GitHub action self-hosted runner on a GCP VM running windows. I’m able to get up to the configuration step. When I run the config script I see the following: Note: when I try and enter the repo and token manually that also fails. I suspect this is because the repository I’m trying to target is private, but this is the first self-hosted runner I have tried to setup so I’m unsure. I did run this in a powershell instance with admin privileges. |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments
-
I’m not having the same problem with private repositories, FYI - but I did have trouble until I did it all in a single line command that’s given when clicking the add-runner button. |
Beta Was this translation helpful? Give feedback.
-
Hey, appreciate the info. I ran the commands from the “Add new runner” dialog in order, in powershell without closing and reopening the command line window. I tried this running powershell in admin, and I tried it without also. So I’m not sure if this is the solution. |
Beta Was this translation helpful? Give feedback.
-
I simply kept trying the exact same way, and a few hours later it managed to print “Connected to Github successfully” and asked me to enter a name for the runner. However it then printed “The SSL connection could not be established, see inner exception.” I tried a few more times and it then succeeded. *shrugs* it is a beta I suppose … |
Beta Was this translation helpful? Give feedback.
-
Hi, I am on Ubuntu 16.04. This solved it for me:
Use the certs folder in front of .configure in env SSL_CERT_DIR=
You should see:
Good luck! |
Beta Was this translation helpful? Give feedback.
I simply kept trying the exact same way, and a few hours later it managed to print “Connected to Github successfully” and asked me to enter a name for the runner.
However it then printed
“The SSL connection could not be established, see inner exception.”
I tried a few more times and it then succeeded.
*shrugs* it is a beta I suppose …