In order to begin a Minecraft instance, the launcher needs to be able download the jar files. Single stack IPv6 hosts cannot download those files from AWS since s3.amazonaws.com is not reachable over IPv6. However Amazon now supports IPv6 on S3 instances, since August 2016 (see blog post at https://aws.amazon.com/blogs/aws/now-available-ipv6-support-for-amazon-s3/), but the customer has to switch an IPv6 enabled endpoint like https://BUCKET.s3.dualstack.REGION.amazonaws.com or https://s3.dualstack.REGION.amazonaws.com/BUCKET
Related issues
relates to
Comments
migrated
migrated
Hello, we've invested a bit of time in this and come to the conclusion that we won't be supporting IPv6 in the foreseeable future. We have balanced being backward compatible with older operating systems, the time needed to validate that the new protocol works, as well as the benefits that this gives.
Minecraft is still seeing IPv6 issues (see MC-232009 and JDK-8272996). Until we reach a point where all our games, launchers, dependencies and supported operating systems fully work with IPv6 we won't be turning it on for any of our endpoints. For the time being, we won't be fixing this.
ziggurism
Is there a reason why this is not prioritized? You only need to change
For example https://s3.amazonaws.com/Minecraft.Download/launcher/launcher.pack.lzma
Needs to be https://s3.dualstack.us-east-1.amazonaws.com/Minecraft.Download/launcher/launcher.pack.lzma (verified - is functional)
This enables IPv6 downloads for all OS wich prefer IPv6 over IPv4. If there is no IPv6 available/enabled then the OS will use IPv4. So there should be only an impact if the IPv6 implementation is not correct/broken. But every downloader should automatically switch over to IPv4.