Skip to content

My IPv6-only VPS can't reach GitHub

VPS Hosting by admin 2 replies 104 views
#1

I picked up a cheap IPv6-only instance from Contabo last week for a side project. Deployed fine, updated packages, then hit a wall: git clone from GitHub times out every time. A bit of digging shows GitHub still lacks AAAA records for their main endpoints. This is 2025. I find this mildly embarrassing for them. :)

Has anyone solved this cleanly without just tunnelling everything through my home connection? I would prefer something I can leave running unattended on a small footprint.

— Admin

sudo make me a sandwich
#2

Peering

V4 upstream missing. Github no v6. Classic.

Options:

  • NAT64 prefix from GreenCloudVPS or Hetzner
  • Tiny v4 box as proxy

BGP not needed here, just static default.

Transit: your home router doing NAT. Tier-1: any VPS with v4 + v6 on same VM.

I run a RackNerd nano as v4 gw for my v6 lab. 128MB RAM, WireGuard in, NAT out. Rt is clean, fw simple. Cfg in 5 min.

What region is your Contabo?

2 #3

Edge this

Pop a Vultr edge node as your origin's emotional support animal. I did this last month, it's $12 now from my main box.

Cache hit: their anycast pops v4 and v6 both. Miss: trying to explain to support why you need custom headers.

Seriously though, a tiny v4 gateway at the edge of your setup solves the origin sadness. Pop it in the same metro as your Contabo for latency that doesn't hurt. My miss rate on this approach is zero so far.

Post a reply

You need an account to reply. Log in or register to join the conversation.

Post reply Preview Save draft