-
Select Topic AreaQuestion BodyI'm using phllips-labs/terraform-aws-github-runner to create self-hosted runners on EC2 instances. The user-script runs fine until I get to the Authentication step when running the config script, it just hangs:
I've seen the
When I Does anyone have any ideas as to why it might be hanging or how I should proceed? UpdateI got more information from the
cloud-init-outp.log also says the user-data script failed:
|
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 11 replies
-
My bet is that your EC2 SG denies outgoing connections. |
Beta Was this translation helpful? Give feedback.
-
I realized now that authentication doesn't seem to be the issue. I assume these lines mean the registration and authentication of the runner was successful:
|
Beta Was this translation helpful? Give feedback.
-
I am having the exact same issue, did you come up with a resolution here? |
Beta Was this translation helpful? Give feedback.
-
I just found the answer and tested. The issue seems to be with IPv6. I removed the IPv6 assignment from the runner as it was starting up and everything ran fine. I created subnets without IPv6 (setting Side note: originally, |
Beta Was this translation helpful? Give feedback.
-
Have the same but on a metal box from hetzner. any ideas how to solve? |
Beta Was this translation helpful? Give feedback.
-
Following up with the answer by @jkruse14, the issue is somehow related to the IPv6 configuration. I had this problem in a bare-metal provider, so I couldn't use the My take on this was finally to disable the IPv6 traffic in the machine itself, using
After a restart on the github runner service, it was able to connect normally and fulfill the session connection establishment. |
Beta Was this translation helpful? Give feedback.
I just found the answer and tested. The issue seems to be with IPv6. I removed the IPv6 assignment from the runner as it was starting up and everything ran fine.
I created subnets without IPv6 (setting
assign_ipv6_address_on_creation
tofalse
) and the issue was then resolved and authentication took place.Side note: originally,
amazon-linux-extras
just hung during the start up when trying to install docker. This resolved that issue as well.