Snapcraft Resync GeoIP database
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Snap Store Server |
New
|
Undecided
|
Unassigned |
Bug Description
I am unable to access Slack downloads from the Snap Store due to geo-restrictions. Although I am located in an accepted country (Australia), my IP subnet range is incorrectly detected as being from a non-acceptable country. My ISP acquired the subnet range last quarter and has updated the GeoIP API providers with the correct information for my subnet, but Snapcraft needs to resync with their GeoIP provider for the correct, up-to-date information.
Steps to Reproduce:
1. Attempt to download a snap (e.g., Slack) from Australia with specific ip (able to provide subnet range on request)
2. Observe the download failure.
```sudo snap install slack
error: snap "slack" not found```
3. Accessing API link for example (https:/
4. Repeat the same steps above on a VPN connected to Australia, the issue does not occur.
5. Further reproduce steps in the forum post https:/
Expected Result:
The snap should download without any issues, correctly identifying the user's geographical location.
Actual Result:
The download fails, showing a "not found" error, indicating issues with the GeoIP data being used by Snapcraft.
Additional Details:
- After a lengthy discussion with the network engineers at my ISP, we've determined that the IPv4 subnet acquired last quarter has had some IP location issues. However, they've contacted all major GeoIP API providers (IP2Location, Maxmind, IPGeolocation.io, etc.) to update their master lists. Now, services using these providers, such as Snapcraft, need to resync to the latest GeoIP information.
- Based on the forum post https:/
- I created a forum post discussing my own issue: https:/
Suggested Fix:
Resync Snapcraft's GeoIP database with their GeoIP provider to ensure it has the latest information, including the newly allocated IP subnets.
Thanks
Hi Justin,
Sorry about the trouble this has been causing. I've moved this to the snapstore-server project. It looks like there is an internal bug related to auto-releasing geoip data. I've asked in that ticket if they can help.
By the way, if you haven't seen this page you may find it helpful: http:// geoip.ubuntu. com/lookup