I try ‘npm install -g meteor’, but see a timeout after the ‘>node cli.js install’ line of output. The progress bar stays at 0% and eventually fails with ETIMEDOUT.
Error: read ETIMEDOUT
at TLSWrap.onStreamRead (internal/stream_base_commons.js:209:20)
Emitted 'error' event on b instance at:
at /work/user/git/unischedulerwebui/npm-global/lib/node_modules/meteor/node_modules/node-downloader-helper/dist/index.js:1:10036
at processTicksAndRejections (internal/process/task_queues.js:95:5) {
errno: -110,
code: 'ETIMEDOUT',
syscall: 'read'
}
The company I work for has a particularly fas— errr, I mean strict outbound firewall for the datacentre in question. They’ve added entries for the general npm distribution, but I’m guessing the meteor install script also calls out elsewhere. The errors and debug log do not mention what URLs are being attempted.
Can I get a list of hostnames/IPs to add to the company firewall?