Unauthenticated clone of a public repo intermittently returns 401 (prompts for Username) from CI workers #206581
🏷️ Discussion TypeBug BodyOur CI workers (Docker containers) clone the public repo This started to occur intermittently since ~ 11 CET 02.09.2026. Our CI workers are EU based. Please let us know if the issue is known and if there are currently any workarounds available. GIT_CURL_VERBOSE shows the anonymous advertisement succeeding: and the follow-up POST on the same connection being rejected: Environment:
|
Replies: 15 comments 13 replies
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
|
We are experiencing the same issue beginning around 09:26 UTC today. Adding the following line resolved the issue for us: No credentials or other pipeline changes were needed. |
|
Same issue here |
|
Another possible fix seems to be to use "actions/checkout" instead of "git clone" |
|
Also same, for us configuring git to use http/1.1 works around it |
|
We're also observing some |
|
@nebuk89 Do you have any known active issues with your European servers? |
|
Hey everyone! 👋 Thank you for raising this. We have shared this with our internal teams to investigate - if we have any updates we will post here and in appropriate discussions ✨ |
|
In case if you need more traces. Here is one from ancient With HTTP/1.1 |
|
I have made an interesting observation - this exact problem occurs with gnutls, but not with openssl (for example on arch linux) |
|
Seeing the same intermittent failures on EU-based CI runners. Switching to HTTP/1.1 seems to reduce the issue, but it doesn’t feel like a reliable long-term workaround. |
|
FTR, I stumbled on this when trying to build zephyr which clones modules as part of the build. Chatting with AI gave the hint to try HTTP/1.1 (which works), further investigation then led me to this discussion. |
|
I just encountered this issue when trying to update Homebrew on Ubuntu 24.04 in EU |
|
TrueNAS users are affected too (both community and enterprise I guess), see https://forums.truenas.com/t/truenas-apps-catalog-fails-to-sync-git-http-2-returns-401-http-1-1-works/67742 |

Hey everyone! 👋 Thank you for raising this. We have shared this with our internal teams to investigate - if we have any updates we will post here and in appropriate discussions ✨