snapcraft updates don't download in an IPv6 + NAT64 environment
Metadata
Current evaluation
Snap installer/refresh hardcodes IPv4 (dial tcp 91.189.92.20:443) and fails on IPv6-only + NAT64 networks where api.snapcraft.io is reachable only via synthesized IPv6. No maintainer response, no labels, no comments; open ~6.7 years.
Suggested action: needs triage
Reason: The issue has zero comments, no labels, and no maintainer interaction in ~6.7 years, so it has never been triaged. It is a genuine bug report (reproducible 'network is unreachable' error with a clear IPv6/NAT64 environment), not a support question, but the fix likely lives in snapd's network stack rather than this repo, and no evidence was found of a fix or related work, so a human should confirm ownership before any close decision.
Impact:
40
Quick Win:
16.0
Staleness:
95
Complexity:
60
Confidence:
55
Support Request:
10
Issue body
A common environment is IPv6 only with compatibility to IPv4 networks provided by NAT64, which includes the Mythic Beasts Raspberry Pi cloud and various IPv6 only VM offerings. In this environment IPv4 only services (e.g. api.snapcraft.io) have IPv6 addresses synthesized to allow connectivity. e.g.
$ telnet api.snapcraft.io 443
Trying 2a00:1098:0:80:1000:3a:5bbd:5c26...
Connected to api.snapcraft.io.
The snap installer appears to ignore this connectivity option and insist on using IPv4 which won't work and doesn't fallback (or better yet, start with) native IPv6.
$ sudo snap install canonical-livepatch
error: cannot install "canonical-livepatch": persistent network error: Post
https://api.snapcraft.io/v2/snaps/refresh: dial tcp 91.189.92.20:443: connect: network is unreachable
IPv6 + NAT64 is the required to be supported for iOS applications.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
40
Quick Win:
16.0
Staleness:
95
Complexity:
60
Confidence:
55
Support Request:
10
|
needs triage | Snap installer/refresh hardcodes IPv4 (dial tcp 91.189.92.20:443) and fails on IPv6-only + NAT64 networks where api.snapcraft.io is reachable only via synthesized IPv6. No maintainer response, no labels, no comments; open ~6.7 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
40
Confidence:
85
Support Request:
10
|
close stale | Issue reports snapcraft installer failing in IPv6+NAT64 environments by ignoring IPv6 and attempting direct IPv4 connections. Unaddressed for over 6 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
45
Confidence:
90
Support Request:
15
|
close stale | Snapcraft fails to connect via IPv6/NAT64, hardcoding IPv4 and causing network errors. Unlabeled, zero comments, inactive for over six years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
65
Confidence:
85
Support Request:
10
|
close stale | Snapcraft fails to install or update in IPv6-only/NAT64 environments due to IPv4 preference and lack of IPv6 fallback. Unlabelled, no maintainer response, inactive for ~6.5 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
40
Confidence:
70
Support Request:
15
|
needs triage | Snap client forces IPv4 and fails in IPv6+NAT64 environments. Lacks maintainer response, labels, or assignees after over six years of inactivity. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1782246 Unable to use snaps in an IPV6 only setup | snapcraft (launchpad) | open | Request for IPv6 support so snaps work in IPv6-only environments; snap login fails dialing an IPv4 store endpoint (91.189.92.17). 8 years old, no labels, zero comments, no maintainer interaction. |