github actions/checkout@v3 got 403 error

[tangyouze]

Select Topic Area

Question

Body

I'm running self host actions runner at alibaba cloud hong kong. And it runs good for about half year, and I got following error from about 2 hours ago.

And I execute from many machines from aliyun cloud hong kong, and get 403 error

curl -vvv -L https://api.github.com/repos/actions/checkout/tarball/f43a0e5ff2bd294095638e18286ca9a3d1956744

Is it because the IP's are banned? or I need to setup some token to avoid this issue?

[mekpin]

yes my github runner on ali cloud also fail to wget to (https://api.github.com/repos)

it causes to break my ci/cd workflow when tried to download action from github action marketplace

[Dr-ManhTung]

No

[caic99]

Same here, with my ali cloud instance on Virginia. Could someone take a look?

[andyziye]

Also the same with runner in Singapore.

[qiuxiafei]

Same problem with runners in Hongkong alicloud.

[tianshuo78520a]

I have also encountered this problem. Can someone help me solve it?

[QuantumGhost]

Same here. Our runner is hosted on Aliyun Hong Kong.

I have also tried using a personal access token for requesting API, and still got 403 Forbidden.

[jessehui]

Same here. Self-hosted runner with Hong Kong server. Keep getting 403 error.

Github action logs:

Try wget directly:

[aikin-vip]

same here

[zhongjiajie]

same here in Ali cloud at Thailand

[delatbabel]

Seems to be related to this: https://github.com/orgs/community/discussions/65227

It's affecting our alicloud servers in Hong Kong, Tokyo and Shenzhen.

[delatbabel]

I have logged a support ticket with Github. I'm guessing that nobody else other than me and github support can see the ticket but here is the URL for reference: https://support.github.com/ticket/personal/0/2312134

Others (especially those with commercial / paid for plans on github) may prefer to log their own support tickets.

[zhongjiajie]

thank for connect those two related issue, it helps a lots to know the detail

[tangyouze]

Follow the document, https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/using-a-proxy-server-with-self-hosted-runners

I use a proxy to do the work around, so fix it currently.

echo """
http_proxy=http://xxxxxx:[email protected]:xxxx
https_proxy=http://xxxxxx:[email protected]:xxxx
no_proxy=aliyuncs.com,xxxxx,xxxx
""" >> .env
./run.sh

[tianshuo78520a]

Can everyone use it normally now? I still have a problem here

[delatbabel]

I just verified that it's still failing for me.

I have also advised alicloud support. There won't be anything that they can do to fix it but at least they can contact github support.

[tianshuo78520a]

I will wait with you！

[delatbabel]

I got a contact back from github support, it has been fixed and I have verified that it's working for me now.

[caic99]

@delatbabel Thanks!
It works for me now after retrying.

[nielifeng]

I tested it and it's back to normal

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬