GitHub's lack of IPv6...

miniopt · February 21

I got a small IPv6 only VPS from DeluxHost just to run an IRC bouncer. Wanted to get a TLS cert for the subdomain that I'll be using with acme.sh, as usual, but I found out painfully that in 2026 GitHub still doesn't support IPv6 so it's impossible to clone any repo.

Not sure what to do since I need to use the DNS-01 challenge and all the ACME clients that support it are hosted on GitHub. Is there an alternative or some way to access GitHub via IPv6 I'm not aware of?

plumberg · February 21

Cloudfare warp

serveradministrator · February 21

Manually upload the whole acme.sh folder to your VPS

AlteredParadox · February 21

https://danwin1210.de/github-ipv6-proxy.php - this dude runs a proxy and has config/info on how to make your own, have that bookmarked but haven't ever done much with it. He specifically calls out that traffic is effectively being decrypted and re-encrypted through his server tho, so take that for what it's worth.

miniopt · February 21

@serveradministrator said:
Manually upload the whole acme.sh folder to your VPS

That works but unfortunately acme.sh still won't be able to auto-update.

@AlteredParadox said:
https://danwin1210.de/github-ipv6-proxy.php - this dude runs a proxy and has config/info on how to make your own, have that bookmarked but haven't ever done much with it. He specifically calls out that traffic is effectively being decrypted and re-encrypted through his server tho, so take that for what it's worth.

Yeah, I've heard about this but the de and re-encryption doesn't sound great.

oloke · February 21

Hi @miniopt

You can use a public NAT64+DNS64 service.

It's as simple as changing your DNS servers to the ones listed there. Your IPv6 traffic will go from your address but IPv4 will be tunneled via the server of NAT64 provider (nat64.net in my case):

root@srv:~# curl ipinfo.io
{
  "ip": "46.235.231.114",
  "hostname": "nat64.dyndns.dk",
  "city": "Amsterdam",
  "region": "North Holland",
  "country": "NL",
  "loc": "52.3740,4.8897",
  "org": "AS44684 Mythic Beasts Ltd",
  "postal": "1012",
  "timezone": "Europe/Amsterdam",
  "readme": "https://ipinfo.io/missingauth"
}

root@srv:~# curl v6.ipinfo.io
{
  "ip": "2a0f:85c1:xx:xx::1",
  "city": "Frankfurt am Main",
  "region": "Hesse",
  "country": "DE",
  "loc": "50.1137,8.7119",
  "org": "AS200950 Lyratris Limited",
  "postal": "60314",
  "timezone": "Europe/Berlin",
  "readme": "https://ipinfo.io/missingauth"
}

Some providers like skhron.eu ( @tentor ) deploy that automatically to prevent customer frustration with Github connectivity on IPv6-only VPSes:
https://skhron.com.ua/knowledgebase/17/DNS64-plus-NAT64.html

maws · February 21

@miniopt said: Yeah, I've heard about this but the de and re-encryption doesn't sound great.

The de/re is only if you do not edit hosts file. If you change host file they can proxy the traffic without looking at it and it simply work

If you use tey Temporary hostname end in .de instead, to prevent mismatch TLS cert they reencrypt.

jsg · February 21

Just put github on @yoursunny's hall of shame list. That'll teach github!

default · February 22

@jsg said:
Just put github on @yoursunny's hall of shame list. That'll teach github!

Whether or not will teach Github, it should still be in @yoursunny list of shame.

plumberg · February 22

@oloke said:
Hi @miniopt

You can use a public NAT64+DNS64 service.

It's as simple as changing your DNS servers to the ones listed there. Your IPv6 traffic will go from your address but IPv4 will be tunneled via the server of NAT64 provider (nat64.net in my case):
root@srv:~# curl ipinfo.io
{
  "ip": "46.235.231.114",
  "hostname": "nat64.dyndns.dk",
  "city": "Amsterdam",
  "region": "North Holland",
  "country": "NL",
  "loc": "52.3740,4.8897",
  "org": "AS44684 Mythic Beasts Ltd",
  "postal": "1012",
  "timezone": "Europe/Amsterdam",
  "readme": "https://ipinfo.io/missingauth"
}
root@srv:~# curl v6.ipinfo.io
{
  "ip": "2a0f:85c1:xx:xx::1",
  "city": "Frankfurt am Main",
  "region": "Hesse",
  "country": "DE",
  "loc": "50.1137,8.7119",
  "org": "AS200950 Lyratris Limited",
  "postal": "60314",
  "timezone": "Europe/Berlin",
  "readme": "https://ipinfo.io/missingauth"
}
Some providers like skhron.eu ( @tentor ) deploy that automatically to prevent customer frustration with Github connectivity on IPv6-only VPSes:
https://skhron.com.ua/knowledgebase/17/DNS64-plus-NAT64.html

Do you provide any other services?

JohnFilch123 · February 22

NAT64 will help you.

TrK · February 22

You can use this https://gh.bakchod.net/ it's just another proxy.

alfatarsos · February 25

nat64.net will not work adequately with Github, from my experience. We had significant complaints with this at C-Servers before we changed the platform.

You will need a NAT64 service that is done from a whole BGP announcement and not from isolated IPs from Hetzner. At the present moment, the only NAT64 service working with Github from my testing is level66.network, which is generally reliable with the occasional packetloss.

A more solid option will definetly be Github proxies, by far.

darkmaster · February 25

https://danwin1210.de/github-ipv6-proxy.php

raindog308 · February 25

I mean, even ColoCrossing has IPv6.

I really don't get this about GitHub. If they were a small startup or something...but even then it's not like they're provisioning hosting accounts or having to do day-to-day admin of IPv6.

Microsoft could put an infrastructure team together, figure out what's needed, and roll it out in...I'll be generous...30 days if they really wanted to.

Is there something complicated about GitHub that I'm not seeing?

Xrmaddness · February 25

@raindog308 said:
I mean, even ColoCrossing has IPv6.

xue · February 25

WARP 各大一键脚本

FSCARMEN :
- 首次运行 wget -N https://gitlab.com/fscarmen/warp/-/raw/main/menu.sh && bash menu.sh
- 日常维护 warp

P3TERX :
- 首次运行 bash <(curl -fsSL git.io/warp.sh) menu
- 日常维护 bash warp.sh

WARP-GO :
- 首次运行 wget -N https://raw.githubusercontent.com/fscarmen/warp/main/warp-go.sh && bash warp-go.sh
- 日常维护 warp-go

MISAKA :
- 首次运行 wget -N https://gitlab.com/Misaka-blog/warp-script/-/raw/main/warp.sh && bash warp.sh
- 日常维护 bash warp.sh

开启效果

无 - IPv4 不支持 | IPv6 支持 | ~1Gbps | 无解锁

You can try it

matt_martin · February 25

One option is to set up an IPv4 proxy or a lightweight tunnel directly on your VPS. This would allow your server to reach IPv4-only services like the repository host. You can also clone the necessary client on another machine and transfer the files manually.

matt_martin · February 25

One option is to set up an IPv4 proxy or a lightweight tunnel directly on your VPS. This would allow your server to reach IPv4-only services like the repository host. You can also clone the necessary client on another machine and transfer the files manually.

suyadi92 · February 25

Use codeberg

Howdy, Stranger!

Categories

In this Discussion

GitHub's lack of IPv6...

Comments

Howdy, Stranger!

Quick Links

Categories

In this Discussion

GitHub's lack of IPv6...

Comments