STF build failed behind proxy while proxy settings are made !

[denis99999]

Under Linux when I build STF without proxy it successes but when I try to build STF behind a proxy, the build fails on zeromq building because the proxy is bypassed and so I get a ECONNREFUSED error which is normal (see below logs for details) , but what I don't understand is why my proxy settings at any level (npm, yarn, git, bash, ...) are not taken into account during this part of the build, so for those who successed a recent STF building behind a proxy, did you meet this issue and what solution did you find to solve it (I did not find the solution on internet!)?

...
warning sinon > [email protected]: This package is unmaintained. Use @sinonjs/formatio instead
warning sinon > [email protected]: This package has been deprecated in favour of @sinonjs/samsam
warning sinon > formatio > [email protected]: This package has been deprecated in favour of @sinonjs/samsam
warning socket.io-client > socket.io-parser > [email protected]: Please use the native JSON object instead of JSON 3
warning then-jade > [email protected]: Jade has been renamed to pug, please install the latest version of pug instead of jade
warning then-jade > jade > [email protected]: Please update to at least constantinople 3.1.1
warning then-jade > jade > [email protected]: Deprecated, use jstransformer
warning then-jade > regenerator > defs > alter > [email protected]: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
warning webpack > watchpack > watchpack-chokidar2 > [email protected]: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
warning webpack > [email protected]: This is probably built in to whatever tool you're using. If you still need it... idk
warning webpack-dev-server > [email protected]: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
warning webpack-dev-server > sockjs > [email protected]: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
[3/5] Fetching packages...
[4/5] Linking dependencies...
[5/5] Building fresh packages...
[1/10] ⠈ @julusian/jpeg-turbo
[-/10] ⠈ waiting...
[-/10] ⠈ waiting...
[6/10] ⠈ zeromq
error /home/debian/GITHUB/DENIS99999/stf/node_modules/zeromq: Command failed.
Exit code: 1
Command: node-gyp-build || npm run build:libzmq
Arguments:
Directory: /home/debian/GITHUB/DENIS99999/stf/node_modules/zeromq
Output:
gyp info it worked if it ends with ok
gyp info using [email protected]
gyp info using [email protected] | linux | x64
gyp info find Python using Python version 3.7.3 found at "/usr/bin/python3"
gyp info spawn /usr/bin/python3
gyp info spawn args [
gyp info spawn args   '/home/debian/.nvm/versions/node/v17.9.0/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'make',
gyp info spawn args   '-I',
gyp info spawn args   '/home/debian/GITHUB/DENIS99999/stf/node_modules/zeromq/build/config.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/home/debian/.nvm/versions/node/v17.9.0/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/home/debian/.cache/node-gyp/17.9.0/include/node/common.gypi',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=/home/debian/.cache/node-gyp/17.9.0',
gyp info spawn args   '-Dnode_gyp_dir=/home/debian/.nvm/versions/node/v17.9.0/lib/node_modules/npm/node_modules/node-gyp',
gyp info spawn args   '-Dnode_lib_file=/home/debian/.cache/node-gyp/17.9.0/<(target_arch)/node.lib',
gyp info spawn args   '-Dmodule_root_dir=/home/debian/GITHUB/DENIS99999/stf/node_modules/zeromq',
gyp info spawn args   '-Dnode_engine=v8',
gyp info spawn args   '--depth=.',
gyp info spawn args   '--no-parallel',
gyp info spawn args   '--generator-output',
gyp info spawn args   'build',
gyp info spawn args   '-Goutput_dir=.'
gyp info spawn args ]
gyp info spawn make
gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
make : on entre dans le répertoire « /home/debian/GITHUB/DENIS99999/stf/node_modules/zeromq/build »
  ACTION binding_gyp_libzmq_target_prepare_build zmq/BUILD_SUCCESS
Error: connect ECONNREFUSED 140.82.121.3:443
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1195:16) {
  errno: -111,
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '140.82.121.3',
  port: 443
}
make: *** [libzmq.target.mk:13: zmq/BUILD_SUCCESS] Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/home/debian/.nvm/versions/node/v17.9.0/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
gyp ERR! stack     at ChildProcess.emit (node:events:527:28)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12)
gyp ERR! System Linux 4.19.0-18-amd64
gyp ERR! command "/home/debian/.nvm/versions/node/v17.9.0/bin/node" "/home/debian/.nvm/versions/node/v17.9.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/debian/GITHUB/DENIS99999/stf/node_modules/zeromq
gyp ERR! node -v v17.9.0
gyp ERR! node-gyp -v v9.0.0
gyp ERR! not ok
make : on quitte le répertoire « /home/debian/GITHUB/DENIS99999/stf/node_modules/zeromq/build »

> [email protected] build:libzmq
> node-gyp rebuild

gyp info it worked if it ends with ok
gyp info using [email protected]
gyp info using [email protected] | linux | x64
gyp info find Python using Python version 3.7.3 found at "/usr/bin/python3"
gyp info spawn /usr/bin/python3
gyp info spawn args [
gyp info spawn args   '/home/debian/.nvm/versions/node/v17.9.0/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'make',
gyp info spawn args   '-I',
gyp info spawn args   '/home/debian/GITHUB/DENIS99999/stf/node_modules/zeromq/build/config.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/home/debian/.nvm/versions/node/v17.9.0/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/home/debian/.cache/node-gyp/17.9.0/include/node/common.gypi',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=/home/debian/.cache/node-gyp/17.9.0',
gyp info spawn args   '-Dnode_gyp_dir=/home/debian/.nvm/versions/node/v17.9.0/lib/node_modules/npm/node_modules/node-gyp',
gyp info spawn args   '-Dnode_lib_file=/home/debian/.cache/node-gyp/17.9.0/<(target_arch)/node.lib',
gyp info spawn args   '-Dmodule_root_dir=/home/debian/GITHUB/DENIS99999/stf/node_modules/zeromq',
gyp info spawn args   '-Dnode_engine=v8',
gyp info spawn args   '--depth=.',
gyp info spawn args   '--no-parallel',
gyp info spawn args   '--generator-output',
gyp info spawn args   'build',
gyp info spawn args   '-Goutput_dir=.'
gyp info spawn args ]
gyp info spawn make
gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
make : on entre dans le répertoire « /home/debian/GITHUB/DENIS99999/stf/node_modules/zeromq/build »
  ACTION binding_gyp_libzmq_target_prepare_build zmq/BUILD_SUCCESS
Error: connect ECONNREFUSED 140.82.121.3:443
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1195:16) {
  errno: -111,
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '140.82.121.3',
  port: 443
}
make: *** [libzmq.target.mk:13: zmq/BUILD_SUCCESS] Error 1
make : on quitte le répertoire « /home/debian/GITHUB/DENIS99999/stf/node_modules/zeromq/build »
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/home/debian/.nvm/versions/node/v17.9.0/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
gyp ERR! stack     at ChildProcess.emit (node:events:527:28)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12)
gyp ERR! System Linux 4.19.0-18-amd64
gyp ERR! command "/home/debian/.nvm/versions/node/v17.9.0/bin/node" "/home/debian/.nvm/versions/node/v17.9.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/debian/GITHUB/DENIS99999/stf/node_modules/zeromq

[jachstet-sea]

Hi @denis99999, I am behind a corporate proxy and my Linux VM is able to run npm i and npx gulp build just fine. That was at 51b86a8. Using Node v18.14.2 and NPM v9.5.0

[denis99999]

@jachstet-sea , thanks for your return, I tried using your Node and NPM versions but it does not change anything, what proxy settings or other configuration settings did you make in order it works behind your corporate proxy ?

[jachstet-sea]

It's mainly setting the environment variables http_proxy, https_proxy, no_proxy (and the upper-cased variants, just to be sure ;)). Some more useful information: https://smarie.github.io/develop-behind-proxy/

[denis99999]

It is probably not a proxy setting issue, in fact in my build, node-gyp is ran for compiling native addon modules for Node.js like zeromq in my case, but the correponding Node.js building code of zeromq is designed to access directly to the network without any proxy, so it can't work!
What I don't undertand is you should meet the same issue as me except if the zeromq addon module for Node.js was prebuilt in your machine, perhaps at a first build without the need of a proxy?