For the last couple of hours I've been searching for a reason, why all *.github.io sites (and *.wikia.com) 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 https://gist.github.com/Saphareas/4e57cf0273f7fa044e2d05991cbe9672 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?
Solved! Solved! Go to Solution.
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/)
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.
Mark helpful posts with Accept as Solution to help other users locate important info. Don't forget to give Kudos for great content!
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.
It would be great if there's IPv6 support.
With a native IPv6 only connection, non IPv6 api.github.com breaks homebrew too.
Don't you just toggle a switch to enable IPv6 on Amazon? :)
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.