Installation fails if behind proxy

Open
#863 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
node.js
Domain
build-system, networking

Research direction

Start by tracing the npm install path that downloads the Qode archive from the GitHub releases URL and inspect how node-fetch handles proxy connections. Reproduce the failure on a proxied Linux environment, then verify that installation can retrieve the archive successfully through the proxy.

Written by the indexing model from the issue text.

Description

Describe the bug
Installation couldn't reach required remote file if connection is proxied

To Reproduce
Steps to reproduce the behavior:

  1. run npm install step of the installation process on a PC that connects to Internet via proxy

Expected behavior
Success

Screenshots

Error while setting up Qode:  FetchError: request to https://github.com/nodegui/qode/releases/download/v2.1.1/qode-linux-x64-v2.1.1.tar.gz failed, reason: connect ECONNREFUSED 140.82.121.3:443
    at ClientRequest.<anonymous> (/apps/nodegui-starter/node_modules/node-fetch/lib/index.js:1461:11)
    at ClientRequest.emit (events.js:400:28)
    at TLSSocket.socketErrorListener (_http_client.js:475:9)
    at TLSSocket.emit (events.js:400:28)
    at emitErrorNT (internal/streams/destroy.js:106:8)
    at emitErrorCloseNT (internal/streams/destroy.js:74:3)
    at processTicksAndRejections (internal/process/task_queues.js:82:21) {
  type: 'system',
  errno: 'ECONNREFUSED',
  code: 'ECONNREFUSED'
}

Desktop (please complete the following information):

  • OS: [e.g. Mac, Linux, Win] Linux
  • latest
  • OS Version Debian 9

Additional context
Add any other context about the problem here.
node-fetch can not connect thru proxy. There are tons of feature requests but no reaction

Dominant language
C++
Stars
9.2k
Forks
315
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nodegui/nodegui

All issues in nodegui/nodegui

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.