Apparently I was an idiot and couldn't do basic auth correctly, because once I did that correctly it worked fine without anonymous access involved. I am using Java 8, and the Authenticator class to set the authentication on my URL globally. Hope this helps the next person coming along.

I'm on ProGet Version 4.7.8 (Build 4) (locally hosted, not on EC2) and I'm able to upload universal packages to an S3-backed feed using the upack.exe tool with both the latest published release of the Amazon plugin and a debug build from source code. Can you still reproduce the error on the latest version of ProGet?

The endpoint is not yet deprecated. This error means that connector url is incorrect, npmjs.org is returning an error, or you have some proxy server blocking the request in between ProGet and npmjs.org.

This appears to be an internal Java error, indicating that the package cannot be bufered due to low process memory. So, I would increase the memory of your Java/Jenkin instance. You can use the -Xmx1024m option to give 1GB of memory to your application. This will increase the amount of data you can store in memory.

The npm endpoint to get all packages is /-/all, so in your case: http://dr-tj-pkgsvr01/npm/npm/-/all

Tried stoping the service that was tying up port 80. No help.

Ok, I noticed that in your log, npm isn't authenticating. Is the anonymous user allowed to access the feed in ProGet?

The native API is a database wrapper, and thus would only be able to return local/cached packages. You should consider using the NuGet API instead.

Team member here. I'd like to let you know that we've moved to the public npm registry. See Retiring the Progress NPM Registry.

As of v4, ProGet will no longer support packages pulling packages with dependencies from the UI. This is because it's "impossible" to do without visual studio's context (target framework, .net version, etc).

Well, for this, you would use the Download package endpoint There's a lot of guides out there on how to use cUrl (here's a good one), but a basic use would be... curl http://proget.local/upack/my-feed/download/my-group/my-package/1.2.3?contentOnly=zip -o my-package1.2.3.zip ... then you can just use unzip.

We have added these exclusions to the Web.config that we include with ProGet.

Hmm, sounds like a NuGet/VS bug... definitely worth sharing this with them!

Please request a key at My.Inedo

I solved this by configuring the URL including port number in the Advanced Settings at "Web.BaseUrl"

This should not impact your ProGet installation

I can't get the Visual Studio 2012 or 2013 SDK to install. In the meantime, you could try building the extension locally with the reference to the 2015 DLL changed to the 2012 or 2013 version: https://github.com/Inedo/VsPushToProGet

Hi, So I delved into the Proget Vor Security extension and found the URL below gets used with the key on the end and a reference to a header too. Tried it through PowerShell and it is blocked so I'll get it added to the white list and retry :) https://vorsecurity.com/92614235v2.0/report/{id} Thanks for your help /Matt

Thank you!! It's finally working.

THis is logged as a bug for [PG-758], and we may get this in next maintence release. Unfortunately it's a non-trivial fix.