[wp-meta] [Making WordPress.org] #3090: WordPress.org API not accessible over IPv6

[Making WordPress.org]

#3090: WordPress.org API not accessible over IPv6
-------------------------+-------------------------
 Reporter:  deaky        |       Owner:  (none)
     Type:  enhancement  |      Status:  closed
 Priority:  high         |   Milestone:
Component:  API          |  Resolution:  maybelater
 Keywords:               |
-------------------------+-------------------------

Comment (by deanhills):

 I've been spending literally HOURS and HOURS trying to figure out why my
 IPV6 VPS cannot connect with WordPress.org.  I created WordPress with
 Debian 10 and all of my permissions are set up correct.  I was able to
 successfully create WordPress on Debian 10 but only from FileZilla SFTP.
 Debian 10 could not reach WordPress.org to fetch the software.  Then when
 I Googled the issue no one responded with the real issue, which is
 WordPress.org is not really interested (or ready yet) to deal with IPv6 as
 IPv6.  It wants those with IPv6 to translate the IP back to IPv4.  If
 everyone else is working with IPv6 as IPv6, why is WordPress going against
 the current?

 If WordPress cannot support IPv6, can you at least add this as one of the
 possible reasons to the WP Dashboard when you say - Your site cannot reach
 WordPress.org at 198.143.164.251 and Curl Error?  You cover all options of
 why wordpress.org cannot be reached, except the most important one.  As
 yet, WP doesn't support IPv6 as IPv6.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/3090#comment:21>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org