npm install network errors with build.snapcraft.io proxy configuration

Metadata

Project: snapcraft (launchpad)
Number: #1886861
Type: issue
State: open
Author: ~benfrancis
Labels: —
Created: 2020-07-08 06:15 PM UTC
Updated: 2020-09-22 10:46 AM UTC
Closed: —

Current evaluation

npm install fails with getaddrinfo ENOTFOUND github.com due to build.snapcraft.io proxy config; reporter has a workaround via proxy env vars. ~6 years old, zero comments, and the affected build service has since been decommissioned.

Suggested action: close stale

Reason: The issue targets build.snapcraft.io's build-server proxy configuration, a service that has since been decommissioned (remote builds moved to GitHub Actions), so the reported ENOTFOUND proxy failure is no longer reproducible. It has had zero comments or maintainer interaction for ~6 years, and the reporter already documented a working workaround (ELECTRON_GET_USE_PROXY/GLOBAL_AGENT_HTTP(S)_PROXY) in the issue body. The fix would have been server-side infrastructure, not a change in this codebase.

Impact: 15 Quick Win: 9.0 Staleness: 95 Complexity: 40 Confidence: 75 Support Request: 35

Issue body

Note: I originally discovered this issue last year and it got fixed upstream with electron-packager (https://forum.snapcraft.io/t/getaddrinfo-enotfound-github-com-builds-failing-on-snapcraft-io-due-to-network-problems/14164/6) but the problem seems to have returned. My snapcraft.yaml (https://github.com/krellian/kiosk/blob/master/snap/snapcraft.yaml) runs `npm install` in override-build, which includes installing the electron-packager npm package. That installation process tries to fetch resources from github.com:443 and fails due to the network proxy configuration being used on build.snapcraft.io RequestError: getaddrinfo ENOTFOUND github.com github.com:443 Full build log here: https://build.snapcraft.io/user/krellian/kiosk/1034152 I was able to work around this issue by adding the following to my snapcraft.yaml but it would be great if this could be fixed. I suspect it's probably an upstream bug again, but perhaps there's something that could be changed about the build server configuration to reduce these types of errors? if [ -n "$http_proxy" ]; then export ELECTRON_GET_USE_PROXY=1 export GLOBAL_AGENT_HTTP_PROXY="${http_proxy}" export GLOBAL_AGENT_HTTPS_PROXY="${http_proxy}" fi

Evaluation history

Date	Model	Scores	Action	Summary
2026-09-01 06:37 AM UTC	qwen/qwen3.8-27b	Impact: 15 Quick Win: 9.0 Staleness: 95 Complexity: 40 Confidence: 75 Support Request: 35	close stale	npm install fails with getaddrinfo ENOTFOUND github.com due to build.snapcraft.io proxy config; reporter has a workaround via proxy env vars. ~6 years old, zero comments, and the affected build service has since been decommissioned.
2026-07-23 11:36 AM UTC	qwen/qwen3.6-35b-a3b	Staleness: 95 Complexity: 30 Confidence: 70 Support Request: 20	needs triage	External contributor reports npm install failing on build.snapcraft.io due to proxy configuration. The issue lacks labels, has zero maintainer comments, and has been inactive for nearly six years.
2026-07-22 01:24 PM UTC	qwen/qwen3.6-35b-a3b	Staleness: 95 Complexity: 20 Confidence: 85 Support Request: 20	close stale	npm install fails on build.snapcraft.io due to proxy configuration blocking GitHub access. Unlabeled, no maintainer comments, and inactive for over 5 years.
2026-07-09 12:40 PM UTC	qwen3.6-35b-a3b-mtp-q6	Staleness: 95 Complexity: 30 Confidence: 85 Support Request: 45	close stale	Reports npm install failures on build.snapcraft.io due to proxy configuration for electron-packager. Provides a workaround. No maintainer response or labels after over six years of inactivity.
2026-06-20 04:18 AM UTC	qwen3.6-35b-a3b-mtp-q6	Staleness: 98 Complexity: 25 Confidence: 90 Support Request: 65	close stale	npm install fails on build.snapcraft.io due to missing proxy configuration for GitHub fetches. Recurred after a prior upstream fix. Open, inactive for over five years, zero comments. Awaits triage and build server update or upstream resolution.

Update history

No update history recorded yet.

Related issues

No related issues found above the similarity threshold.