Dear @marcan42, it is only a minor issue in comparison to the great challanges in your great project @AsahiLinux. https://asahilinux.org/ does not support #IPv6 because it has no AAAA-records. Fastly supports it, so it should be a matter of minutes:https://docs.fastly.com/en/guides/ipv6-support …
-
I consider them using magic since they can’t just flip a switch to enable IPv6 at all. There might be selfbotched webservers and maybe logging/monitoring without IPv6 support at all.
The specific SNI mappings presumably have to be enabled for specific Fastly endpoints, so even if a random endpoint still routes you to the right backend via their infra, it won't serve the right cert, and thus won't work with HTTPS.
-
-
Yep, tried it. IPv6 should be 2a04:4e42::133 (at least from my location). However, the cert served over this IP is only valid for different tastes of "github". So, unless using another CDN in front, there doesn't seem to be a way right now.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.