Splunk AppDynamics

Node.js agent fails to download

CommunityUser
Splunk Employee
Splunk Employee

npm install appdynamics@4.5.13 fails

Looks like some form of SSL problem. Only with the appdynamics package, all other packages install OK.

npm WARN deprecated set-immediate@0.1.1: Use `setimmediate` instead
npm ERR! code ECONNREFUSED
npm ERR! errno ECONNREFUSED
npm ERR! FetchError: request to https://cdn.appdynamics.com/packages/nodejs/4.5.13.0/appdynamics-libagent-node.tgz failed, reason: connect ECONNREFUSED 0.0.0.0:443
npm ERR! at ClientRequest.req.on.err (/usr/local/lib/node_modules/npm/node_modules/node-fetch-npm/src/index.js:68:14)
npm ERR! at ClientRequest.emit (events.js:198:13)
npm ERR! at TLSSocket.socketErrorListener (_http_client.js:392:9)
npm ERR! at TLSSocket.emit (events.js:198:13)
npm ERR! at emitErrorNT (internal/streams/destroy.js:91:8)
npm ERR! at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
npm ERR! at process._tickCallback (internal/process/next_tick.js:63:19)
npm ERR! { FetchError: request to https://cdn.appdynamics.com/packages/nodejs/4.5.13.0/appdynamics-libagent-node.tgz failed, reason: connect ECONNREFUSED 0.0.0.0:443
npm ERR! at ClientRequest.req.on.err (/usr/local/lib/node_modules/npm/node_modules/node-fetch-npm/src/index.js:68:14)
npm ERR! at ClientRequest.emit (events.js:198:13)
npm ERR! at TLSSocket.socketErrorListener (_http_client.js:392:9)
npm ERR! at TLSSocket.emit (events.js:198:13)
npm ERR! at emitErrorNT (internal/streams/destroy.js:91:8)
npm ERR! at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
npm ERR! at process._tickCallback (internal/process/next_tick.js:63:19)
npm ERR! message:
npm ERR! 'request to https://cdn.appdynamics.com/packages/nodejs/4.5.13.0/appdynamics-libagent-node.tgz failed, reason: connect ECONNREFUSED 0.0.0.0:443',
npm ERR! type: 'system',
npm ERR! errno: 'ECONNREFUSED',
npm ERR! code: 'ECONNREFUSED',
npm ERR! stack:
npm ERR! 'FetchError: request to https://cdn.appdynamics.com/packages/nodejs/4.5.13.0/appdynamics-libagent-node.tgz failed, reason: connect ECONNREFUSED 0.0.0.0:443\n at ClientRequest.req.on.err (/usr/local/lib/node_modules/npm/node_modules/node-fetch-npm/src/index.js:68:14)\n at ClientRequest.emit (events.js:198:13)\n at TLSSocket.socketErrorListener (_http_client.js:392:9)\n at TLSSocket.emit (events.js:198:13)\n at emitErrorNT (internal/streams/destroy.js:91:8)\n at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)\n at process._tickCallback (internal/process/next_tick.js:63:19)',
npm ERR! parent: 'appdynamics' }
npm ERR!
npm ERR! If you are behind a proxy, please make sure that the
npm ERR! 'proxy' config is set properly. See: 'npm help config'

Labels (1)
0 Karma
1 Solution

CommunityUser
Splunk Employee
Splunk Employee

Found it. It was our corporate firewall blocking access.

View solution in original post

CommunityUser
Splunk Employee
Splunk Employee

Found it. It was our corporate firewall blocking access.

Get Updates on the Splunk Community!

Accelerating Observability as Code with the Splunk AI Assistant

We’ve seen in previous posts what Observability as Code (OaC) is and how it’s now essential for managing ...

Integrating Splunk Search API and Quarto to Create Reproducible Investigation ...

 Splunk is More Than Just the Web Console For Digital Forensics and Incident Response (DFIR) practitioners, ...

Congratulations to the 2025-2026 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...