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.

ProGet for Linux is already out; it's shiped as a docker container. We have a lot of users who install ProGet on server core, but please note it's an advanced OS and requires a lot of commandline use. So, it's a bit more difficult to install ProGet on this. A ProGet Node is either the Web or Indexing Service. The "Load Balanced Only" comes with just three nodes, so for this yo you would have two web nodes and then Service node. An enterprise installation will have 5+ nodes, which typically is multiple services nodes (at least two) and then the rest web nodes. With automatic failover, basically if one of the indexing services becomes inactive, then the other takes over indexing duties. Sure, as long as the web and indexing service can access the files using the regular File IO (i.e. it shows up as a drive in windows), then you can use the regular disk package store for this.

If this is happening, then the package is not being deleted from the package store on disk and is being re-added by the routine index reconcillation. The most likely cause for this is a misconfiguration (pointing to wrong file store), a file permissions error, or a back-up system restoring the package. When you delete a package, it should be deleted from the database and from the disk.

You can make an AfterPushPackageAdapter in a plugin. There's an example of an adapter on GitHub.

It seems like the problem is caused outside of ProGet. So, i would investigate Windows integrated Authentication (if you have it enabled, disable it as a test). Also look for other "random" IIS settings that may have inadvertently been changed. It's also possible to be networking equipment (bad router, switch, etc).

It's working again now, there was an issue with one of our feed URL's. But I would expected an HTTP 404 error instead of an HTTP 500 error then..

These are two separate errors: 404 - the package you asked for was not found 401 - you are not authorized to ask for a package If you configure your feed for authentication, then you're going to need to authenticate to the feed before you can query. The query will not even be considered if you do not authenticate. However, even if you authenticate correctly, if the package is not there, you will receive a 404. They are unrelated messages.