This isn’t hard to do. Internap would be more than happy to allocate you an IPv6 block.
Thanks for the laughs 😀
Yes, I do agree it’s about time the WordPress infrastructure supported IPv6. But, no, it’s not a trivial task (if you know anything at all about network engineering and systems administration)… and access to an IPv6 address block has absolutely nothing to do with the challenges of going IPv6.
Moderator
Yui
(@fierevere)
永子
IPv6 only host should have outgoing IPv4 connectivity via a common shared address across other nodes in same hoster network.
There can be problems with too many requests from one source address., however.
Alternatively you can use HTTP-proxy directives in wp-config.php
define(WP_PROXY_HOST, 'localhost'); // address
define(WP_PROXY_PORT, 3128); // port
define(WP_PROXY_USERNAME, 'username'); // auth username if needed
define(WP_PROXY_PASSWORD, 'password'); // auth password
@fierevere There are entire regions, ISPs, and cloud environments where IPv6 is the only available option. This is no longer a niche problem. By refusing to support IPv6, WordPress is actively excluding users and breaking functionality for legitimate use cases.
The technical barrier is minimal. I’ve set up IPv6 for many companies over the years. It’s literally as simple as configuring the load balancer and web servers to listen on v6. If Automattic chooses to use IPv4 internally, that’s fine. But there’s no valid excuse for not making IPv6 available externally on public-facing services.
If this is truly beyond Automattic’s internal capabilities, there are companies like Cloudflare or Akamai who have been offering dual-stack support for years. Offloading it to them is trivial.
According to this ticket: https://meta.trac.wordpress.org/ticket/3090 WordPress has had more than eight years to get this done.
Please stop delaying and prioritize IPv6 support.
Moderator
Yui
(@fierevere)
永子
It is not something to be decided or discussed on support forums, I’ve shown you workaround and pointed at fact that IPv4-less servers are almost a not-existent thing.
However, i see you have already found proper place, a Meta Trac and made a ticket which obviously been a duplicate of existing one
https://meta.trac.wordpress.org/ticket/3090
As you can see it is not a thing to be done fast, but i guess, most of us hope that sooner or later it will be implemented.
I will mark this topic as resolved as there is nothing within the scope of the support forum
We’ll work on this, sorry it hasn’t happened yet.
Please see the Meta Trac ticket for the latest updates. v6 connectivity is now enabled for the most important WordPress.org services.
