Making WordPress.org

Opened 8 weeks ago

Last modified 6 weeks ago

#8134 new defect (bug)

IPv6 connection to api.wordpress.org is unreachable

Reported by: natanhp's profile natanhp Owned by:
Milestone: Priority: normal
Component: API Keywords: reporter-feedback
Cc:

Description

I'm experiencing a connection problem when using wp-env. It appears to be caused by an inability to access api.wordpress.org over IPv6.

daedalus@ngoumah ~ [1]> ping -6 api.wordpress.org
ping: connect: Network is unreachable

I had previously opened a Github issue in the Gutenberg repository, and the conclusion was that the issue is not within Gutenberg itself: https://github.com/WordPress/gutenberg/issues/72894

Change History (4)

#1 @dd32
8 weeks ago

  • Keywords reporter-feedback added

Hi @natanhp,

Can you please provide a traceroute to WordPress.org such that we can see where the issue lies? It's likely in a random provider somewhere between yourself and WordPress.org.

Something like this should work: mtr --report-wide -b -6 api.wordpress.org
You may wish to redact your IP in the first entry of that report, please only redact the final segments of the IP, such that we can do a reverse trace if required.

#2 follow-up: @natanhp
8 weeks ago

It is unreachable

daedalus@ngoumah ~ [1]> mtr --report-wide -b -6 api.wordpress.org
mtr: udp socket connect failed: Network is unreachable

#3 in reply to: ↑ 2 ; follow-up: @dd32
8 weeks ago

Replying to natanhp:

It is unreachable

daedalus@ngoumah ~ [1]> mtr --report-wide -b -6 api.wordpress.org
mtr: udp socket connect failed: Network is unreachable

Thank you. Based on that your local computers network stack is broken, as the problem exists before your network router.

https://bbs.archlinux.org/viewtopic.php?id=259467 lists similar errors.

You can determine if it's DNS or IP Routing by trying by IP rather than hostname, if that fails, something is broken in your IP routes. It may be caused by VPN usage or other privacy extensions.. but that's outside of my expertise..

Eg by IP: mtr --report-wide -n -6 2607:f978:5:8002::c68f:a4fb

It may also be something that's worth bringing up with the WordPress Core team, that the API communications may need to fallback to IPv4 in event of the IPv6 communication being broken.. I can't see an existing ticket there. Similar to the HTTPS -> HTTP fallback.

#4 in reply to: ↑ 3 @natanhp
6 weeks ago

Replying to dd32:

Replying to natanhp:

It is unreachable

daedalus@ngoumah ~ [1]> mtr --report-wide -b -6 api.wordpress.org
mtr: udp socket connect failed: Network is unreachable

Thank you. Based on that your local computers network stack is broken, as the problem exists before your network router.

https://bbs.archlinux.org/viewtopic.php?id=259467 lists similar errors.

You can determine if it's DNS or IP Routing by trying by IP rather than hostname, if that fails, something is broken in your IP routes. It may be caused by VPN usage or other privacy extensions.. but that's outside of my expertise..

Eg by IP: mtr --report-wide -n -6 2607:f978:5:8002::c68f:a4fb

It may also be something that's worth bringing up with the WordPress Core team, that the API communications may need to fallback to IPv4 in event of the IPv6 communication being broken.. I can't see an existing ticket there. Similar to the HTTPS -> HTTP fallback.

I got the same result by doint it with the IP

daedalus@ngoumah ~ [1]> mtr --report-wide -n -6 2607:f978:5:8002::c68f:a4fb
mtr: udp socket connect failed: Network is unreachable

I think this issue is from my internet provider. I agree about the fallback to IPv4 plan, since apparently not all countries are ready for IPv6.

Note: See TracTickets for help on using tickets.