← Back to issue list

Unable to use snaps in an IPV6 only setup

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1782246
Type
issue
State
open
Author
~geoffmcc
Labels
—
Created
Updated
Closed
—

Current evaluation

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.

Suggested action: close stale

Reason: The report is 2967 days old with 0 comments, no labels, and no maintainer interaction, and it is fundamentally a request for IPv6 on the snap store (dashboard.snapcraft.io) — server-side infrastructure outside this client repo's scope, with the error coming from snapd's `snap login` rather than snapcraft code. The specific IPv4 endpoint in the error is long outdated, so the original report is no longer actionable as written. Confidence is moderate because I could not verify current store IPv6 status (tool lookups failed).

Impact: 30 Quick Win: 18.0 Staleness: 95 Complexity: 40 Confidence: 45 Support Request: 55

Issue body

I'm not sure if this is really the right place for this as it is not really a bug, rather a lack of ipv6 support, but I was unable to find an email address or anything to reach out to inquire. Vultr's $2.50 plan now only includes ipv6 and I now find unable to use snaps due to what I assume is lack of ipv6 support on snapcraft.io. I get the below error when trying to login via sudo snap login error: cannot get snap access permission from store: Post https://dashboard.snapcraft.io/dev/api/acl/: dial tcp 91.189.92.17:443: connect: network is unreachable (see "snap login --help") Now that there is a provider out there, probably others only dealing in ipv6 (without additional charge) could we possibly get snaps working in ipv6 only environments?

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 30
Quick Win: 18.0
Staleness: 95
Complexity: 40
Confidence: 45
Support Request: 55
close stale 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.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 30
Confidence: 85
Support Request: 90
close stale Feature request for IPv6 support on snapcraft.io. Open for 8 years with zero maintainer comments or labels. Reporter notes connection failures due to IPv4-only store endpoints and asks for IPv6-only environment compatibility.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 60
Confidence: 90
Support Request: 85
needs triage User reports inability to use snaps on IPv6-only networks due to snapcraft.io resolving to IPv4. No maintainer response or labels after ~8 years.
qwen3.6-35b-a3b-mtp-q6
Staleness: 98
Complexity: 40
Confidence: 85
Support Request: 80
close stale Request to add IPv6 support for snapcraft.io and the Snap store, as IPv4-only endpoints prevent usage in IPv6-only environments. Untriaged and inactive for ~8 years.
qwen3.6-35b-a3b-mtp-q6
Staleness: 98
Complexity: 20
Confidence: 70
Support Request: 85
close stale Request for IPv6 support for snapcraft.io endpoints, which currently resolve to IPv4 addresses, blocking usage in IPv6-only environments. Unaddressed for nearly 8 years with no maintainer response.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#1857006 snapcraft updates don't download in an IPv6 + NAT64 environment snapcraft (launchpad) open 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.
73%