[FAQ] io.Connect CLI setup - internal corporate network npm registry blocking access to the public registry

io.Connect Desktop
,
1

Question

Inside a corporate network with an internal npm registry and restricted outbound access, installing @interopio/iocd-cli fails with:

  • npm ERR! network request to https://codeload.github.com/... failed, reason: read ECONNRESET
  • After setting proxy: npm ERR! 502 Bad Gateway - GET .../@interopio%2fiocd-cli
  • Git SSH failure: ssh: connect to host github.com port 22: Connection timed out

Answer

  1. Ensure the CLI can reach GitHub endpoints via proxy
  • Set HTTPS_PROXY (and typically HTTP_PROXY) to the corporate proxy.
  • If your internal npm registry returns errors when the proxy is enabled (for example 502 Bad Gateway) set NO_PROXY to your internal registry host (and any other internal hosts)
setx HTTPS_PROXY "http://proxy.company.com:8080"
setx HTTP_PROXY  "http://proxy.company.com:8080"
setx NO_PROXY    "internal-registry.company.net,localhost,127.0.0.1"

or

export HTTPS_PROXY="http://proxy.company.com:8080"
export HTTP_PROXY="http://proxy.company.com:8080"
export NO_PROXY="internal-registry.company.net,localhost,127.0.0.1"
  1. If you see GitHub SSH/port 22 timeouts, force HTTPS for GitHub
    Some networks block SSH to GitHub. If npm triggers Git operations and you see ssh://git@github.com/... failures, configure:
  • http.proxy
  • http.sslCAInfo
  • Rewrite GitHub SSH → HTTPS:
    • git config --global url."https://github.com/".insteadOf "ssh://git@github.com/"
    • git config --global url."https://github.com/".insteadOf "git@github.com:"

Re-run and inspect CLI logs
The CLI log file should be located in the @interopio-iocd-cli folder in the OS temporary directory (temp folder) e.g. C:\Users\<your-username>\AppData\Local\Temp\@interopio-iocd-cli
Also confirm the correct repository URL and required credentials with IT and check the troubleshooting section here io.Connect Desktop Documentation - Seed Project.