IPv6 support for cloning Git repositories #10539
Replies: 223 comments 565 replies
-
|
I am unable to understand what in 2022 still holds full IPv6 support for a platform like GitHub. |
Beta Was this translation helpful? Give feedback.
-
|
New ISPs in my country are IPv6-only because there is no new IPv4 space to be provided to them. They do have a over-shared IPv4 address by CGNAT but due to the oversharing, it is unstable and not rare to be offline. For these companies, the internet access is stable only in IPv6. Thinking about the server-side, some cloud providers are making extra charges for IPv4 addresses (e.g.: Vultr.com) so most of the servers in my company are IPv6-only. Cloning github repositories is very cumbersome due to the lack of IPv6 support and this issue affects me and my team mates on a daily basis. The math is simple: there are 4.88 billion internet users in the world but the IPv4 space only provides 4 billion addresses. It's over: IPv4 is obsolete and is provided in a legacy mode. Current applications and services must be IPv6 enabled otherwise it should be seen as obsolete. For that matter, Github.com is an obsolete service because it relies on obsolete technology as IPv4. |
Beta Was this translation helpful? Give feedback.
-
|
I really tried to use github in a IPv6 Only Network and I was not successful. Is there any plan on the github's roadmap to fully adopt IPv6? |
Beta Was this translation helpful? Give feedback.
-
|
If GitHub can't get v6 on GitHub.com soon, maybe at least an ipv6.github.com proxy for SSH git cloning? |
Beta Was this translation helpful? Give feedback.
-
|
IPv6 is the actual internet protocol, while IPv4 is a legacy protocol. Please, priorize this request. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
My private ci is forced to go full IPv6 only, and this requires me to have one IPv4 gateway to access github. This in turn means I keep running into rate limits all the time. For now I've worked around this with an access token, but that's not sustainable. Any ipv6 support would be much appreciated. |
Beta Was this translation helpful? Give feedback.
-
|
Is GitHub deprecated or why there is still no IPv6 support? We are talking about a over 20 year old technology and the standard for about 5 years. |
Beta Was this translation helpful? Give feedback.
-
|
Probably because people that manage the technical team still didn't realize what this mean and didn't prioritize it enough. Well, then why hasn't all that been done beforehand and being carried out gradually that we can some progress on it ? Are there people working dedicated to make that happen ? After companies like Google, Facebook, Netflix, Akamai, Cloudflare have made it 100% I don't see any other strong arguments for companies use complexity as a reason to delay it further. Hope someone from GitHub's team is reading it. |
Beta Was this translation helpful? Give feedback.
-
|
I vaguely remember that years ago (pre-MS, pre-pandemic) somewhere Github engineers held a talk (or maybe it was a blog posting?) which more less said that IPv6 is in the makes, but less trivial than one might think. I just can't find that talk or slides or so anymore. I also vaguely remember that they mentioned What I though have found is that there is an ipv6 label in Github's blog — it though only lists one posting so far, which talks about Github Pages now having IPv6 support. There even once was But yeah, another Github user here with (on purpose) trying to run hosts IPv6 only and the first (and so far only) hard stumbling block was not being able to clone Git repos from Github. 🤌 I wonder if I should use Gitlab.com for these repos, because they do have an AAAA record for their main site: |
Beta Was this translation helpful? Give feedback.
-
|
It's 2022, World IPv6 Launch Day was 10 years ago. Yet, GitHub still doesn't have IPv6 support. The IPv4 address space is exhausted for years now, and ISPs are using techniques such as CGNAT to still be able to give their customers access to the legacy IPv4 internet, with the instability of these techniques as the cost. Why doesn't GitHub provide native IPv6 support? And, more importantly, is IPv6 support for GitHub on the roadmap? |
Beta Was this translation helpful? Give feedback.
-
|
CC rust-lang/cargo#10711 this causes real issues for open source software users. This is an absurd conversation in 2022. |
Beta Was this translation helpful? Give feedback.
-
|
This is $MS. This company was and will be ever a enemy of open source or new technologies that comes not from $MS. They did nothing that helps the community. $MS is only interested in earning money and gives a shit on your needs |
Beta Was this translation helpful? Give feedback.
-
|
How can you not have ipv6? Some cloud providers charge extra for ipv4! |
Beta Was this translation helpful? Give feedback.
-
|
Would any Github/Microsoft representative tell us in which year, century or millenium will they support IPV6? We have public cloud environments where we are with IPV6 only already... Although, based on recent experience with Azure, I think their public cloud environment is also like with 10 years behind Google and Amazon's public cloud anyway. Why would they bother for Github? |
Beta Was this translation helpful? Give feedback.
-
|
Just adding another real-world use case where this is a major blocker. My ISP recently moved my connection to CGNAT, so I lost my public IPv4 address. I successfully migrated my self-hosted infrastructure to IPv6, and it is perfectly working. However, my CI/CD pipelines broke because GitHub Webhooks do not support IPv6. I'm getting failed to connect to host errors even though the endpoint is accessible. It is frustrating to be forced to use third-party tunneling solutions (like Cloudflare Tunnel) just to bridge this gap, when a direct IPv6 connection should be the standard by now. +1 for IPv6 support on Webhooks. |
Beta Was this translation helpful? Give feedback.
-
|
2026, GitHub still doesn't support IPV6. |
Beta Was this translation helpful? Give feedback.
-
|
Just found this: Just add the following entries to /etc/hosts: |
Beta Was this translation helpful? Give feedback.
-
|
Does anyone actually have an idea WHY THE FUCK ipv6 is still not supported in 2026? |
Beta Was this translation helpful? Give feedback.
-
|
In 2026, I encountered an issue when attempting to clone a repository on an AWS IPv6-only instance. I was unable to configure the DNS resolver until I discovered that I now need to begin the process from an IPv4 network instance and reconfigure everything. I am therefore concerned about GitHub’s decision not to support IPv6 or native proxies. I do not wish to use third-party IPv4 to IPv6 proxies. |
Beta Was this translation helpful? Give feedback.
-
|
A.D. 2126: virtually all of the Internet traffic is IPv6; even the most stubborn corporations have long since moved on from the ancient protocol. However, not many know that in a remote location in the Phrygian mountains, in the ancient monastery of St. Natius, the priestesses of the heretic cult of gyt'üb, are still keeping the sacred flame of IPv4 burning. Visitors are sometimes admitted into the sanctuary, but they are required to shed their hextets and only speak through a NAT64 translator. |
Beta Was this translation helpful? Give feedback.
-
|
Czech Republic even launched a countdown to end of Ipv4: https://konecipv4.cz/en/ |
Beta Was this translation helpful? Give feedback.
-
|
That's my only gripe, at least WARN that ipv6 is not supported. That's the
real kicker, look at how many people are still bumping this shit every day
! SATYA?
…On Mon, Jan 12, 2026 at 9:35 AM Jörn Bethune ***@***.***> wrote:
And if you as an ISP providing service to .cz citizens don't give IPv6
access will be totally clear that you don't give a working service.
In my experience, you don't get clear error messages when you try to
connect from an IPv6-only network to github. Unless browsers improve their
error messages, it is unlikely that the ISP will be blamed for lack of IPv6
support. Most relevant web sites will probably continue to support IPv4 for
many more years.
—
Reply to this email directly, view it on GitHub
<#10539 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BTWTLRZ3GWDQZ5A33DARCYL4GNFEFAVCNFSM5MYNB6L2U5DIOJSWCZC7NNSXTOSENFZWG5LTONUW63SDN5WW2ZLOOQ5TCNJUG4ZDMOJT>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
Roy Cohen
Founder, Creating Relations
|
Beta Was this translation helpful? Give feedback.
-
|
Well I guess it's clear that GitHub doesn't care about implementing IPv6. Now it's kind of your decision accept and keep using or look for other alternatives. I know that a lot of open source libraries keep using GitHub, But in case you want to use IPv6 for your repositories, you need to do something. I already saw some open source projects in Codeberg or Gitlab, maybe it is a start of a movement. |
Beta Was this translation helpful? Give feedback.
-
|
How on earth ? This is one of the most important and largest organizations on the planet. What the fuck is wrong here ?! |
Beta Was this translation helpful? Give feedback.
-
|
I was having issues with ipv4 and imagine my surprise that one of the largest tech focused websites has no ipv6. For anyone that wants some kind of solution to this https://nat64.net/ |
Beta Was this translation helpful? Give feedback.
-
|
I moved too to my own ForgeJo instance, I’m still manually migrating my repos but I really like it, and my instance is IPv6 only 😉
|
Beta Was this translation helpful? Give feedback.
-
|
IPv4 shall not pass 🫡🫡🫡 |
Beta Was this translation helpful? Give feedback.
-
|
Guys, GitHub is a global technology company, unfortunately they haven't had time to implement IPv6 yet because it's new. The idea started relatively recently (1994), it was created recently (1998), and officially released a few months ago (2012). We're only in 2026, I don't understand why you're criticizing it. IPv4 still has plenty of addresses in the world (more irony here), ISPs aren't using NAT to put dozens of users behind a single valid IP (yes, more irony), so we don't need IPv6 yet (the final irony). |
Beta Was this translation helpful? Give feedback.
-
|
found out about it because no provisioning was possible for my ipv6 only hosts. Ask Copilot maybe? Or better Claude? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I'm surprised I didn't find an existing discussion with this topic. Some services like github-releases.githubusercontent.com or user pages do support IPv6, however the webpage (github.com) itself, including cloning of git repositories, does not work.
Is there a public roadmap on enabling IPv6 for GitHubs very core business, distributing Git repositories? If I'm wrong and there is already IPv6 support, please guide me.
The same issues exists for api.github.com and thereby making CLIs unusable on IPv6 only connections.
EDIT: I left this topic on "Subscribe" to receive notifications if GitHub ever responds, after 3 years I lost hope and will unsubscribe now. I'm sure I'll get the news somewhere else - if IPv6 on Github it ever happens.
Beta Was this translation helpful? Give feedback.
All reactions