-
Notifications
You must be signed in to change notification settings - Fork 46
Missing ipv6 connectivity #90
Comments
Original comment by gasimed (Bitbucket: gasimed, GitHub: Unknown): Yes, i checked them, and all mirrors were either down or had no ipv6. I rechecked right now. To install a package from an alternative mirror: So someone finding this ticket, will be able to install pypi package, like I did. Maybe you can add a hint to https://pypi.python.org/mirrors? |
As IPv4 addresses become more contested, this is starting to become a problem for my use - I now have to build environments on ipv4-connected hosts and ship them to ipv6 ones, or maintain an RFC1918 network. Is there any progress on the CDN end? |
Fastly just announced Beta HTTP/2 and IPv6 today, we will follow up for |
From https://www.fastly.com/release-notes/q1-2016-q2-2016 :
It would be nice for pypi to enroll in this IPv6 program! |
we have already submitted requests for IPv6 program and are waiting on a response. |
Excellent news, thanks! |
ipv6 is go :) |
Yeay! Thanks! |
Not sure if anyone will see this, but it appears that ipv6 is not working again. My office ISP leases us an IPv6 address, which is completely unable to access pypi (or any pip packages). Has something changed recently? By the looks of this, the issue should have been resolved quite some time ago. Thanks in advance! |
@leiforion If this is a general issue with your ISP you should contact them. If other services work with IPv6, then it's probably an issue with Fastly, you can use their debug website and send them a support request: https://www.fastly-debug.com/ |
Originally reported by: gasimed (Bitbucket: gasimed, GitHub: Unknown)
pypi.python.org is missing ipv6 connectivity, which make pip unusable for ipv6-only hosts.
While getting ipv6 connectivity should have the highest priority to fix this problem, ipv6 mirrors could be published on
https://pypi.python.org/mirrors
as a workaround. At least the missing ipv6 mirrors should be documentated on this site.
The text was updated successfully, but these errors were encountered: