AMO does not support IPv6 anymore, only IPv4
Categories
(Cloud Services :: Operations: AMO, task)
Tracking
(Not tracked)
People
(Reporter: rctgamer3, Assigned: wezhou)
Details
Title. I know it used to work over a year ago, but no idea what happened. AMO, and services.addons.mozilla.org is completely unavailable on a IPv6-only setup. I do occasionally do IPv6-only site-checks and found this odd. I have no idea how many users this would affect, but I think there's a tiny portion of Firefox users out there that, due to IPv4 exhaustion, cannot view AMO nor download add-ons at all, if their ISP doesn't NAT them to let them use the IPv4 internet. Critical (incomplete) server list not supporting IPV6/not having AAAA records: blocklists.settings.services.mozilla.com services.addons.mozilla.org addons.cdn.mozilla.net addons.mozilla.org Shouldn't AMO be future-proof? :)
|
||
Comment 1•7 years ago
|
||
I do believe we should support IPV6 (and we have in the past) but there are limitations within AWS we would need work around. Currently AWS ELB does not support IPV6 in Default VPC however their newer product ALB does. We would either need to wait till ELB supports IPV6 or switch to ALB. Our main concerns with ALB is cost and we would need to look into that more if we decide to go through that route. For now I am lowering the priority and we will look into it further some time in the future.
|
|
||
Updated•7 years ago
|
|
||
Comment 2•7 years ago
|
||
See also https://github.com/mozilla/addons/issues/454
|
|
||
Comment 3•4 years ago
|
||
:wezhou see https://github.com/mozilla/addons/issues/1175 are there any updates on this related to available support in AWS for ipv6?
Unfortunately no. AFAIK, AWS ELB in a VPC doesn't support IPv6 at this point.
We may eventually have to migrate to ALB given that AWS hasn't taken actions to support IPv6 for ELB in a VPC. However, like mentioned earlier, cost associated with ALB would be a factor for us to consider when prioritizing work.
If I might offer a user story to take the initial reporter's supposition into reality:
I have spoken with some users that recently experienced a failed IPv4 route while an IPv6 route was still viable. Today this means many websites are still reachable and one can still do a great deal of real work. I maintain a network in house that is IPv6-only that is similarly quite usable. I can often go hours before running into a "We can't connect to the server at..."
Last night I reinstalled the OS on one of my desktops in this network. It is a Linux machine and the distro ships with Firefox already installed. I started happily browsing to some of my favorite sites, only to find quite a few ad servers are also reachable over IPv6. Apparently one of them served me some malware as my CPU went immediately to 100% and stayed there.
Ah, right, I still need to install uBlock Origin. I brought up the Add-ons tab, tried the search, and it failed. (I can't get uBO from upstream at github.com either, but that's hardly your fault.)
--
The above is an actual scenario I encountered. Let us take a look at a small variant that, while I have not directly encountered in my usage patterns, is still rather plausible.
Suppose the OS I have just installed does not ship with Firefox. I remember a friend told me to go to getfirefox.com. Easy to remember!
Nope, that's an error.
Undeterred, I head over to mozilla.org. OK, looking good so far. I find the download page, click on "Just Download the Browser"
"Almost there..."
Another error message.
--
So there we have it: the user has now hit frustration, installed Chrome, visited the Chrome Web Store, installed uBlock Origin, and is on their merry way. (Yes, I tested this all works on my IPv6-only network as well).
I hope I have illustrated that this is no longer a matter of being "future-proof" but a very real impact that is best addressed sooner rather than later.
AFAIK, AWS ELB in a VPC doesn't support IPv6 at this point.
There's been a regression in my user story. (www.)mozilla.org is now unreachable over IPv6 as well. This means when I click on the "What's new" link in my distro installed firefox-esr package I get the "Hmm. We're having trouble finding that site." message.
The tenth anniversary of World IPv6 Launch is coming up on 2022-06-06. I hope Mozilla can get a handle on these regressions and get back on the modern Internet.
Oh, it gets better. Online help is completely inaccessible from IPv6-only.
Help -> Get Help
We can't connect to the server at support.mozilla.org.
Description
•