-
Hi all, When executing the image build with packer for Ubuntu 22, I get the following error when it tries to download the runner bin: ubuntu@ip-10-21-108-145:~$ curl -o test -f "https://github.com/actions/runner/releases/download/v2.321.0/actions-runner-linux-x64-2.321.0.tar.gz" I then created an instance in AWS and logged into that. I confirmed that it can reach github by nslookup. Non-authoritative answer: I then tried the following curl flags since I thought it might be certificate related: That also didnt help. Below the returns untu@ip-10-21-108-145:~$ curl -o test -fL "https://github.com/actions/runner/releases/download/v2.321.0/actions-runner-linux-x64-2.321.0.tar.gz" curl failed to verify the legitimacy of the server and therefore could not I tried the same command on my ubuntu22 machine in my office behind a corp firewall. There it is no issue to download the bin with the same command I checked the OpenSSL and curl versions on both machine and they are the same 123@123~/.ssh $ openssl version I dont understand why there is a 403 in AWS but not from my office and how to authenticate where with what if that is the issue. It might be a long shot, but did anyone had the same issue or has an idea what I can do, so that the packer build works in my AWS account? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
I figured it out.. it was a change in our company firewall approach in where I have to specifically whitelist every domain I want to access from our EC2 instances. I thought I got all of them but did not realize that the DL call to github.com redirects to objects.githubusercontent.com. After whitelisting that domain too, it works just fine. I figured this out after checking the verbose responses with the -v curl flag. Leaving this here for any other GHES user that might have the same issue. |
Beta Was this translation helpful? Give feedback.
I figured it out.. it was a change in our company firewall approach in where I have to specifically whitelist every domain I want to access from our EC2 instances. I thought I got all of them but did not realize that the DL call to github.com redirects to objects.githubusercontent.com.
After whitelisting that domain too, it works just fine. I figured this out after checking the verbose responses with the -v curl flag.
Leaving this here for any other GHES user that might have the same issue.