GitHub Community
-
Select Topic AreaBug BodyWithout any relevant change recently wget -d https://github.com/cli/cli/archive/refs/tags/v2.33.0.tar.gz
DEBUG output created by Wget 1.21.4 on linux-gnu.
Reading HSTS entries from /home/users/jan/.wget-hsts
URI encoding = ‘UTF-8’
Converted file name 'v2.33.0.tar.gz' (UTF-8) -> 'v2.33.0.tar.gz' (UTF-8)
--2023-08-28 22:25:52-- https://github.com/cli/cli/archive/refs/tags/v2.33.0.tar.gz
Resolving github.com (github.com)... 140.82.121.4
Caching github.com => 140.82.121.4
Connecting to github.com (github.com)|140.82.121.4|:443... connected.
Created socket 3.
Releasing 0x000000000516c350 (new refcount 1).
Initiating SSL handshake.
Handshake successful; connected socket 3 to SSL handle 0x000000000513d910
certificate:
subject: CN=github.com,O=GitHub\\, Inc.,L=San Francisco,ST=California,C=US
issuer: CN=DigiCert TLS Hybrid ECC SHA384 2020 CA1,O=DigiCert Inc,C=US
X509 certificate successfully verified and matches host github.com
---request begin---
GET /cli/cli/archive/refs/tags/v2.33.0.tar.gz HTTP/1.1
Host: github.com
User-Agent: Wget/1.21.4
Accept: */*
Accept-Encoding: identity
Connection: Keep-Alive
---request end---
HTTP request sent, awaiting response...
---response begin---
HTTP/1.1 302 Found
Server: github.com
Date: Mon, 28 Aug 2023 20:25:52 GMT
Content-Type: text/html; charset=utf-8
Vary: X-PJAX, X-PJAX-Container, Turbo-Visit, Turbo-Frame, Accept-Encoding, Accept, X-Requested-With
Location: https://codeload.github.com/cli/cli/tar.gz/refs/tags/v2.33.0
Cache-Control: max-age=0, private
Strict-Transport-Security: max-age=31536000; includeSubdomains; preload
X-Frame-Options: deny
X-Content-Type-Options: nosniff
X-XSS-Protection: 0
Referrer-Policy: no-referrer-when-downgrade
Content-Security-Policy: default-src 'none'; base-uri 'self'; child-src github.com/assets-cdn/worker/ gist.github.com/assets-cdn/worker/; connect-src 'self' uploads.github.com objects-origin.githubusercontent.com www.githubstatus.com collector.github.com raw.githubusercontent.com api.github.com github-cloud.s3.amazonaws.com github-production-repository-file-5c1aeb.s3.amazonaws.com github-production-upload-manifest-file-7fdce7.s3.amazonaws.com github-production-user-asset-6210df.s3.amazonaws.com cdn.optimizely.com logx.optimizely.com/v1/events *.actions.githubusercontent.com productionresultssa0.blob.core.windows.net/ productionresultssa1.blob.core.windows.net/ productionresultssa2.blob.core.windows.net/ productionresultssa3.blob.core.windows.net/ productionresultssa4.blob.core.windows.net/ productionresultssa5.blob.core.windows.net/ productionresultssa6.blob.core.windows.net/ productionresultssa7.blob.core.windows.net/ productionresultssa8.blob.core.windows.net/ productionresultssa9.blob.core.windows.net/ wss://*.actions.githubusercontent.com github-production-repository-image-32fea6.s3.amazonaws.com github-production-release-asset-2e65be.s3.amazonaws.com insights.github.com wss://alive.github.com; font-src github.githubassets.com; form-action 'self' github.com gist.github.com objects-origin.githubusercontent.com; frame-ancestors 'none'; frame-src viewscreen.githubusercontent.com notebooks.githubusercontent.com; img-src 'self' data: github.githubassets.com media.githubusercontent.com camo.githubusercontent.com identicons.github.com avatars.githubusercontent.com github-cloud.s3.amazonaws.com objects.githubusercontent.com objects-origin.githubusercontent.com secured-user-images.githubusercontent.com/ user-images.githubusercontent.com/ private-user-images.githubusercontent.com opengraph.githubassets.com github-production-user-asset-6210df.s3.amazonaws.com customer-stories-feed.github.com spotlights-feed.github.com *.githubusercontent.com; manifest-src 'self'; media-src github.com user-images.githubusercontent.com/ secured-user-images.githubusercontent.com/ private-user-images.githubusercontent.com; script-src github.githubassets.com; style-src 'unsafe-inline' github.githubassets.com; upgrade-insecure-requests; worker-src github.com/assets-cdn/worker/ gist.github.com/assets-cdn/worker/
Content-Length: 0
X-GitHub-Request-Id: 98BA:74A7:48233D3:48C8BCC:64ED02D0
---response end---
302 Found
Registered socket 3 for persistent reuse.
Parsed Strict-Transport-Security max-age = 31536000, includeSubDomains = true
Updated HSTS host: github.com:443 (max-age: 31536000, includeSubdomains: true)
URI content encoding = ‘utf-8’
Location: https://codeload.github.com/cli/cli/tar.gz/refs/tags/v2.33.0 [following]
] done.
URI content encoding = None
Converted file name 'v2.33.0.tar.gz' (UTF-8) -> 'v2.33.0.tar.gz' (UTF-8)
--2023-08-28 22:25:52-- https://codeload.github.com/cli/cli/tar.gz/refs/tags/v2.33.0
Resolving codeload.github.com (codeload.github.com)... 140.82.121.10
Caching codeload.github.com => 140.82.121.10
Connecting to codeload.github.com (codeload.github.com)|140.82.121.10|:443... connected.
Created socket 4.
Releasing 0x0000000005054740 (new refcount 1).
Initiating SSL handshake.
Handshake successful; connected socket 4 to SSL handle 0x00000000050d3130
certificate:
subject: CN=*.git.luolix.top,O=GitHub\\, Inc.,L=San Francisco,ST=California,C=US
issuer: CN=DigiCert TLS Hybrid ECC SHA384 2020 CA1,O=DigiCert Inc,C=US
X509 certificate successfully verified and matches host codeload.github.com
---request begin---
GET /cli/cli/tar.gz/refs/tags/v2.33.0 HTTP/1.1
Host: codeload.github.com
User-Agent: Wget/1.21.4
Accept: */*
Accept-Encoding: identity
Connection: Keep-Alive
---request end---
HTTP request sent, awaiting response...
---response begin---
HTTP/1.1 403 Forbidden
Cache-Control: no-cache
Content-Type: text/html; charset=utf-8
Strict-Transport-Security: max-age=31536000
X-Content-Type-Options: nosniff
X-Frame-Options: deny
X-XSS-Protection: 0
Content-Security-Policy: default-src 'none'; style-src 'unsafe-inline'
connection: close
---response end---
403 Forbidden
Parsed Strict-Transport-Security max-age = 31536000, includeSubDomains = false
Updated HSTS host: codeload.github.com:443 (max-age: 31536000, includeSubdomains: false)
URI content encoding = ‘utf-8’
Closed 4/SSL 0x00000000050d3130
2023-08-28 22:25:53 ERROR 403: Forbidden. |
Beta Was this translation helpful? Give feedback.
Replies: 7 comments 19 replies
-
|
Same for me but with a different version: GNU Wget 1.20.3 built on linux-gnu. |
Beta Was this translation helpful? Give feedback.
-
|
Ack. Noticed failed downloads about two hours before the first post. |
Beta Was this translation helpful? Give feedback.
-
|
I also started having that issue a couple of hours ago. |
Beta Was this translation helpful? Give feedback.
-
|
this resolved it for me on non-dockerized |
Beta Was this translation helpful? Give feedback.
-
|
It seems that the bug only affects Linux. |
Beta Was this translation helpful? Give feedback.
-
|
Actually it seems to work with any explicit |
Beta Was this translation helpful? Give feedback.
-
|
In turn seems to be related to ciphers configured for if (opt.secure_protocol == secure_protocol_auto)
ciphers_string = "HIGH:!aNULL:!RC4:!MD5:!SRP:!PSK";which does not work with default |
Beta Was this translation helpful? Give feedback.
-
|
Anyone have a solution to this without modifying the wget command? I have a At the moment I am able to fix it by adding TLSv1 as default security protocol in wget config file:
But I'm not sure if this is the best approach. |
Beta Was this translation helpful? Give feedback.
-
|
Hey, I'm one of the engineers on the Git Protocols team, which is responsible for the service, codeload, that serves archives. We blocked a scraper which was causing some performance impact earlier and it appears our pattern wasn't specific enough, so it accidentally flagged more clients than we wanted. We've restricted the pattern to be more specific so it shouldn't impact other parties, and things should be back to normal. My apologies for the problems; we'll try to avoid this kind of problem again in the future. |
Beta Was this translation helpful? Give feedback.
-
|
this change failed our self-host GitHub action runner, and I think some other users with Ali cloud as their infra suffer for this too, see https://github.com/orgs/community/discussions/65227#discussioncomment-6852121 could you do not ban Ali cloud anymore? |
Beta Was this translation helpful? Give feedback.
-
|
@bk2204 this is still failing across all Alicloud IP addresses. |
Beta Was this translation helpful? Give feedback.
-
|
@bk2204 this is still failing across all Alicloud IP addresses. |
Beta Was this translation helpful? Give feedback.
-
|
I contacted Alicloud and they had no good solution. It seems that the problem lies with github |
Beta Was this translation helpful? Give feedback.
-
|
thanks @bk2204 for the heads up. do you guys have any plan to whitelist alicloud ip back? |
Beta Was this translation helpful? Give feedback.
-
|
Hi, We are still having the same problem, started in the last 8 hours so maybe different to what was reported above. It affects multiple servers and I have tried using the --secure-protocol workarounds mentioned above to no effect. It's affecting all of our servers in SE Asia and E Asia data centres including Tokyo, Singapore and Hong Kong. It's not affecting a similar server in Sydney nor is it affecting our desktop devices in Vietnam. Any chance of a resolution?
|
Beta Was this translation helpful? Give feedback.
-
|
@bk2204 hi BK i think this problem also affect many instances under ali cloud https://github.com/orgs/community/discussions/65335 theres another thread discussing it if you have any workaround please do tell |
Beta Was this translation helpful? Give feedback.
-
|
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 |
Beta Was this translation helpful? Give feedback.
-
|
@delatbabel I can not see the ticket, please give me mention me if have any process of this, thanks |
Beta Was this translation helpful? Give feedback.
-
|
@delatbabel did you get a solution from support? I have a similar issue on self-hosted runners. Strangely, I can get a wget from the runner machine but not from the action when it is executing. |
Beta Was this translation helpful? Give feedback.
-
|
@adinriv yes it's working for us now on Alicloud. Initially it was affecting all machines on Alicloud but now that's working OK. It sounds like you have a different problem, because for us every action on the runner machine was being blocked, but now that's not the case. |
Beta Was this translation helpful? Give feedback.
-
|
This is heavily impacting our production process as we are currently affected by the blockage. How can we solve this issue? |
Beta Was this translation helpful? Give feedback.
-
|
I got a contact back from github support, it has been fixed and I have verified that it's working for me now. |
Beta Was this translation helpful? Give feedback.
Hey,
I'm one of the engineers on the Git Protocols team, which is responsible for the service, codeload, that serves archives. We blocked a scraper which was causing some performance impact earlier and it appears our pattern wasn't specific enough, so it accidentally flagged more clients than we wanted.
We've restricted the pattern to be more specific so it shouldn't impact other parties, and things should be back to normal. My apologies for the problems; we'll try to avoid this kind of problem again in the future.