AppD Archive

403 on npm install

CommunityUser
Splunk Employee
Splunk Employee

Hi There,

I'm evaluating AppDynamics and packages.appdynamics.com host is returning a 403 on npm install.  I've tried npm installing various versions to no avail.  Here's the output if it's helpful:

npm ERR! fetch failed http://packages.appdynamics.com/npm/4.2.1.0/appdynamics-protobuf.tgz
npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 403
npm ERR! fetch failed http://packages.appdynamics.com/npm/4.2.1.0/appdynamics-native.tgz
npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 403
npm ERR! fetch failed http://packages.appdynamics.com/npm/4.2.1.0/appdynamics-zmq.tgz
npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 403
npm ERR! fetch failed http://packages.appdynamics.com/npm/4.2.1.0/appdynamics-native.tgz
npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 403
npm ERR! fetch failed http://packages.appdynamics.com/npm/4.2.1.0/appdynamics-zmq.tgz
npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 403
npm ERR! fetch failed http://packages.appdynamics.com/npm/4.2.1.0/appdynamics-protobuf.tgz
npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 403
npm ERR! fetch failed http://packages.appdynamics.com/npm/4.2.1.0/appdynamics-native.tgz
npm ERR! fetch failed http://packages.appdynamics.com/npm/4.2.1.0/appdynamics-protobuf.tgz
npm ERR! fetch failed http://packages.appdynamics.com/npm/4.2.1.0/appdynamics-zmq.tgz
npm ERR! Linux 3.19.0-56-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" "appdynamics@4.2.x" "--save"
npm ERR! node v4.4.0
npm ERR! npm v3.8.1

npm ERR! fetch failed with status code 403
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! <https://github.com/npm/npm/issues>

Thanks,

Greg

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

This also just started occurring on our builds.  Was working fine last week.  Node version 4.3.2.

npm info attempt registry request try #1 at 10:03:21 PM
npm http fetch GET http://packages.appdynamics.com/npm/4.2.1.0/appdynamics-native.tgz
npm info retry fetch attempt 2 at 10:03:21 PM
npm info attempt registry request try #1 at 10:03:21 PM
npm http fetch GET http://packages.appdynamics.com/npm/4.2.1.0/appdynamics-zmq.tgz
npm http fetch 403 http://packages.appdynamics.com/npm/4.2.1.0/appdynamics-native.tgz
npm ERR! fetch failed http://packages.appdynamics.com/npm/4.2.1.0/appdynamics-native.tgz
npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 403
npm http fetch 403 http://packages.appdynamics.com/npm/4.2.1.0/appdynamics-zmq.tgz
npm ERR! fetch failed http://packages.appdynamics.com/npm/4.2.1.0/appdynamics-zmq.tgz
npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 403
npm http fetch 403 http://packages.appdynamics.com/npm/4.2.1.0/appdynamics-protobuf.tgz
npm ERR! fetch failed http://packages.appdynamics.com/npm/4.2.1.0/appdynamics-protobuf.tgz
npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 403

Tags (2)
0 Karma

CommunityUser
Splunk Employee
Splunk Employee

My calls to AppD NPM server are now succeeding.  According to support, there was an issue with their NPM server that is now resolved.

0 Karma

Brennan_Hildebr
Engager

We are aware of an ongoing issue with certain of the node.js agent package downloads and are actively investigating.

We expect to have a general solution shortly.

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

I am on node 4.4.1 and am installing agent 4.1.10. I get a HTTP 403 error however. This 403 error is coming for all agent versions. What do i need to resolve this ?

0 Karma

CommunityUser
Splunk Employee
Splunk Employee
I feel you.

I'm currently discussing with the problem with the maintener to see what to do with the current situation.
0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Well I certainly won't be downgrading my 4.4.2 app to 0.12.9 just to use AppD

However, I think that is a separate issue. If the AppD plugin was not compatible with 4.4.2 I'd be getting a warning when it installed (lots of libraries do this, especially with the huge version jump after the iojs merge). It would probably (hopefully?) still install and work.

A 403 means I'm not even able to get the installer package to attempt to install. It's being stopped at step one. This sounds like a problem with the repo. 

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

So, it looks like the repo explicitly checks "user-agent" from npm:

% npm config list
; cli configs
user-agent = "npm/3.7.3 node/v5.9.1 linux x64"

Here is the supported list of versions for 4.1:
https://docs.appdynamics.com/display/PRO41/Node.js+Supported+Environments

If you override the user-agent setting, downloads will work:

% npm config set user-agent "npm/3.7.3 node/v0.10.41 linux x64"
% npm install appdynamics@4.1.8

This only allowed me to download packages, I haven't tried loading this code yet with a spoofed node version.

Also, be careful: npm will write / update ~/.npmrc with this agent string. You'll probably want to delete this or update back to the original agent string.

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Fixed the issue.

Instead of yum install nodejs npm , we can use the following commands for installing nodejs.

[root@rhel-agent node]# wget https://rpm.nodesource.com/pub/el/7/x86_64/nodejs-0.10.31-1nodesource.el7.centos.x86_64.rpm
[root@rhel-agent node]# rpm -ivh nodejs-0.10.31-1nodesource.el7.centos.x86_64.rpm
[root@rhel-agent node]# node -v
[root@rhel-agent node]# npm -v
[root@rhel-agent node]# npm install appdynamics@4.1.0
[root@rhel-agent node]# npm list
/home/basu/node
└─┬ appdynamics@4.1.0
├── appdynamics-jre@1.7.0
├── appdynamics-native@4.1.0
├── appdynamics-protobuf@0.8.7
├── appdynamics-proxy@4.1.0
├── appdynamics-zmq@2.5.1
├── node-uuid@1.4.1
└── set-immediate@0.1.1

Cheers!!

Arunava

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

$ npm view appdynamics dist-tags.latest

4.1.8

 

$ npm install appdynamics@4.1.8

npm ERR! fetch failed http://packages.appdynamics.com/npm/4.1.8.0/appdynamics-native.tgz

npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 403

npm ERR! fetch failed http://packages.appdynamics.com/npm/4.1.8.0/appdynamics-zmq.tgz

npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 403

npm ERR! fetch failed http://packages.appdynamics.com/npm/4.1.8.0/appdynamics-protobuf.tgz

npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 403

npm ERR! fetch failed http://packages.appdynamics.com/npm/4.1.8.0/appdynamics-native.tgz

npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 403

npm ERR! fetch failed http://packages.appdynamics.com/npm/4.1.8.0/appdynamics-protobuf.tgz

npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 403

npm ERR! fetch failed http://packages.appdynamics.com/npm/4.1.8.0/appdynamics-zmq.tgz

npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 403

 

Do I have to add something to my .npmrc or something? 

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

@jcollum: If you use appdynamics 4.1.8, the Node version you use has to be under 0.12.9
Try to run `$ node --version` to see your current version.

You can force downloading 4.2.1 if your app run with Node 5.7.1 or less.

`npm install appdynamics@4.2.1`

But by doing that I'm afraid it might not connect to the controller unless you contact the support.

0 Karma

CommunityUser
Splunk Employee
Splunk Employee
Hold on, 0.12.9? 0.12.0 was released over a year ago and there has been an
LTS release since then. Just to be clear, you're telling me that I can't
use the -only- LTS release for this platform with Appdynamics?
0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi,

appdynamics version 4.2.1 has the following limitation in its package.json:
`engines: { node: '>=0.8.0 <=5.7.1' }`

So anybody using the latest version of node can't use appdynamics.
It would be nice from AppDynamics to avoid setting an maximum version for Node, specially since it keeps moving forward.

Having a list a tested and supported version should be enough.

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

I also got the same issue.

# npm install appdynamics@4.1.0
npm http GET https://registry.npmjs.org/appdynamics/4.1.0
npm http 304 https://registry.npmjs.org/appdynamics/4.1.0
npm http GET http://packages.appdynamics.com/npm/4.1.0.0/appdynamics-native.tgz
npm http GET http://packages.appdynamics.com/npm/4.1.0.0/appdynamics-jre.tgz
npm http GET http://packages.appdynamics.com/npm/4.1.0.0/appdynamics-zmq.tgz
npm http GET http://packages.appdynamics.com/npm/4.1.0.0/appdynamics-proxy.tgz
npm http GET http://packages.appdynamics.com/npm/4.1.0.0/appdynamics-protobuf.tgz
npm http 200 http://packages.appdynamics.com/npm/4.1.0.0/appdynamics-jre.tgz
npm http 200 http://packages.appdynamics.com/npm/4.1.0.0/appdynamics-proxy.tgz
npm http 403 http://packages.appdynamics.com/npm/4.1.0.0/appdynamics-zmq.tgz
npm ERR! fetch failed http://packages.appdynamics.com/npm/4.1.0.0/appdynamics-zmq.tgz
npm ERR! Error: 403 Forbidden
npm ERR! at WriteStream.<anonymous> (/usr/lib/node_modules/npm/lib/utils/fetch.js:57:12)
npm ERR! at WriteStream.emit (events.js:117:20)
npm ERR! at fs.js:1610:14
npm ERR! at /usr/lib/node_modules/graceful-fs/graceful-fs.js:103:5
npm ERR! at Object.oncomplete (fs.js:108:15)
npm ERR! If you need help, you may report this log at:
npm ERR! <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR! <npm-@googlegroups.com>

npm ERR! System Linux 3.10.0-327.el7.x86_64
npm ERR! command "node" "/bin/npm" "install" "appdynamics@4.1.0"
npm ERR! cwd /home/basu/node
npm ERR! node -v v0.10.42
npm ERR! npm -v 1.3.6
npm http 403 http://packages.appdynamics.com/npm/4.1.0.0/appdynamics-protobuf.tgz
npm ERR! fetch failed http://packages.appdynamics.com/npm/4.1.0.0/appdynamics-protobuf.tgz
npm http 403 http://packages.appdynamics.com/npm/4.1.0.0/appdynamics-native.tgz
npm ERR! fetch failed http://packages.appdynamics.com/npm/4.1.0.0/appdynamics-native.tgz
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/basu/node/npm-debug.log
npm ERR! not ok code 0

Does anyone has a solution?

Thanks,

Arunava

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!

Tech Talk Recap | Mastering Threat Hunting

Mastering Threat HuntingDive into the world of threat hunting, exploring the key differences between ...

Observability for AI Applications: Troubleshooting Latency

If you’re working with proprietary company data, you’re probably going to have a locally hosted LLM or many ...

Splunk AI Assistant for SPL vs. ChatGPT: Which One is Better?

In the age of AI, every tool promises to make our lives easier. From summarizing content to writing code, ...