Cannot reach any github.io page via IPv6

Came here to add my vote for IPv6 here as well. I’ve been designing my networks with v6 first and this is yet another major barrier.

Thanks!

7 Likes

Yes. It is about time. I got the same “we value your input” reply 3 years ago. Please act now.

And please add _full_ IPv6 support, not just for your webservers. We need IPv6 for Mail and everything else as well. Currently, github is pretty much useless for me.

6 Likes

I honestly cannot believe that common online developer tools like GitHub and Launchpad did not already support IPv6 connections years ago. Boggles the mind. C’mon, GitHub - get your act together!

7 Likes

I’ve resorted to proxying github traffic through TOR (which supports IPv6)  in order to reach github from my IPv6 only hosts. 😞

git config --global http.proxy 'socks5://127.0.0.1:9100'
4 Likes

Like many that are commenting here, it wasn’t until a search was done that we have found out why our IPv6 systems cannot connect to GitHub.  Please allow access to IPv6, which has been around for many years and is quite ubiquitous now. More and more hosting companies are charging us extra to use their precious, few IPv4 addresses and are giving away IPv6 addresses like a howitzer hitting a pinata.

5 Likes

Just discovered for myself that GitHub does not support IPv6.

Guys, I’m sorry and I don’t want being rude, but in 2019 this is just facepalm.

9 Likes

Here is my solution/workaround. It requires:

  1. a server/vps (a bridge) with IPv4 connectivity and a couple of IPv6 addresses, ideally a /64

  2. install gpr (https://github.com/elgs/gproxy) on the bridge

  3. create gpr.json on the bridge server as follows:


{  
"github.com" : {  
"dstPort" : 443,  
"localPort" : 443,  
"localAddr" : "[2001:1111:1111:1111:0000:0000:0000:0001]",  
"dstAddr" : "github.com"  
},  
"codeload.github.com" : {  
"dstPort" : 443,  
"localPort" : 443,  
"localAddr" : "[2001:1111:1111:1111:0000:0000:0000:0002]",  
"dstAddr" : "codeload.github.com"  
}  
}

  1. run gpr gpr.json on the bridge;

  2. on the IPv6 only servers, append the following lines to /etc/hosts

github.com 2001:1111:1111:1111:0000:0000:0000:0001

codeload.github.com 2001:1111:1111:1111:0000:0000:0000:0002

And you are ready to rock and roll.

1 Like

Instead of using precious TOR resources, better setup a NAT64 gateway in your network.

But other than that I totally agree I can’t believe github doesn’t support it already. How are the developers supposed to develop for the new protocol and make the change happen if they’re hold back?

2 Likes

This has been bugging me for years since all my FreeBSD jails are IPv6 only and it’s a pain to maintain NAT64 just for the purpose of downloading some software hosted on GitHub. It’s 2019 now and still no improvement on GitHub’s end. I cannot understand that of all platforms GitHub must be one of those who seemingly completely ignore this topic.

3 Likes

I’d also like to repeat the others in this thread - GitHub Pages should support IPv6!

I’ve recently migrated a static site to GitHub pages. I’ve had to drop IPv6 support as part of that migration. :frowning:

In the meantime I am going to keep a look out for alternative providers… Maybe GitLab Pages will support IPv6 soon? https://gitlab.com/gitlab-com/gl-infra/infrastructure/issues/645

3 Likes

Just a note that if you are using a link local IPv6 address within fe80::/10 for your proxy (ex: from an IPv6 only buildbot so that it can reach luddite IPv4 only services such as github or your buildbot master), you need to add the interface name to the localAddr IPv6 addresses.  Such as [fe80::2:3:5:8%enp1s0].

1 Like

For what it is worth, Apple is requiring apps that are submitted to the app store support ipv6 only networks0, and I know Github doesn’t have an app, but it shows that major companies are taking ipv6 seriously.

1 Like

Dual stack which functions normally and all I get is connection timed out when trying to download from github.

Oh well, hope whoever’s sticking with github to migrateto gitlab soon!

Any update on this?  This is quite embarrassing for Github as we enter 2020.

6 Likes

Just want to note that “doesn’t currently support IPv6” is an answer to the question but not really a solution on the modern Internet, and that’s probably especially true for folks who (would like to) use Github.

1 Like

They’re only really requiring you not to hardcode v4 addresses and let DNS64/NAT64 work. (I’ve heard some mobile carriers use NAT64 now…)

They’re not actually requiring everything to actually be accessible directly over v6.

GitHub does have an official app now: https://github.com/mobile

GitHub, including Pages, doesn’t currently support IPv6. (Though you can test if your end of the connection does using a tool like https://test-ipv6.com/ )

How about now?

Except for Github not having IPv6 and not having flying cars, we’re in the future.

1 Like

November 2020 … Any update ?

2 Likes

What could be the reason to insist on a protocol from September 1981 in 2020 and ignoring the state-of-the-art protocol (that is almost 22 years old!) for a major site? I have no clue.

However, there is GitLab and they support IPv6. Moving projects from GitHub to GitLab seems to be an easier method than manipulating network traffic (chaning DNS queries, proxying…) and is more universal (on some sites you might not have the possibility to do those network manipulations).

2 Likes

It is the end of 2020. About 30% of the Internet is now on IPv6, so it is a reasonably significant amount.

Adding IPv6 support is relatively trivial, if you can’t do dual stack then a simple reverse proxy will work (or a CDN).

1 Like