Cannot reach any page via IPv6

For the last couple of hours I’ve been searching for a reason, why all * sites (and * would result in a ERR_Connection_Reset in all my browsers (Vivaldi, Opera, Firefox, Edge, IE, though Firefox and Edge would sometimes work). After writing down my experiences at I discovered that it’s an issue with IPv6.

Now I just want to know, if this issue is on my end, or if it’s a problem with Githubs servers. Does anyone know anything about this?


GitHub, including Pages, doesn’t currently support IPv6. (Though you can test if your end of the connection does using a tool like


@lee-dohm wrote:

GitHub, including Pages, doesn’t currently support IPv6. (Though you can test if your end of the connection does using a tool like

Do you know if it will ever support IPV6?


Hi @haydenoa,

We’re always working to improve GitHub, and we consider every suggestion we receive. I’ve logged your request internally. Though I can’t guarantee anything or share a timeline for this, I can tell you that it’s been shared with the appropriate teams for consideration.



Thank you! I appreache it.

It is 2018 and it wasn’t considered to enable ipv6 support till now? Am i missing something here?


Does GitHub have a roadmap for when will support access over IPv6** -only** networks?


It would be great if there’s IPv6 support.

With a native IPv6 only connection, non IPv6 breaks homebrew too.

Don’t you just toggle a switch to enable IPv6 on Amazon? :slight_smile:


IPv6 support would be great, so we can build github-depending software in ipv6-only containers, saving us the hassle to maintain ipv4 support for those containers that we don’t need for our organisation internal services. FYI, all major linux distributions including repository access already work without problem on ipv6-only networks.


I’d like to add my support to the request for github and wikia to enable IPv6 support.

There’s really no obvious barrier to doing this. Git software can easily support IPv6. Adding IPv6 to web servers is a well known, well trodd, well understood path.

Turns out that lack of IPv6 support on github is proving to be a gating issue preventing a number of environments from dumping support for antiquated IPv4, inflicting unnecessary expense and inconvenience on those environments.

FWIW, Atlassian BitBucket fully supports IPv6, so please consider this in your competitive landscape.



I also think GitHub should support IPv6.   There is a lot of interest in using the platform in the IETF, the lack of IPv6 support is a problem for this.

Could someone explain why it isn’t currently supported.




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.



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.


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!


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://'

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.


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.


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 ( on the bridge

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

"" : {  
"dstPort" : 443,  
"localPort" : 443,  
"localAddr" : "[2001:1111:1111:1111:0000:0000:0000:0001]",  
"dstAddr" : ""  
"" : {  
"dstPort" : 443,  
"localPort" : 443,  
"localAddr" : "[2001:1111:1111:1111:0000:0000:0000:0002]",  
"dstAddr" : ""  

  1. run gpr gpr.json on the bridge;

  2. on the IPv6 only servers, append the following lines to /etc/hosts 2001:1111:1111:1111:0000:0000:0000:0001 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?

1 Like

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.