We have been running the update since it has been out and it does look like it has fixed our issues with random failing npm restores. Running my LinqPad test script now (which makes 32 concurrent requests for the same resource), still makes it "fail", but now with a 404 as you described, instead of returning an empty package. (Which is still quite weird behavior IMO...) Thanks for the quick response and help on solving this!

As far as I'm aware, the original issue in this thread has been resolved long ago. If there is a new issue with pulling connector packages, please post a new question.

Yes, but it's not "officially" scheduled as BuildMaster v5 is the top priority at the moment. Here is the roadmap for reference: http://inedo.com/proget/roadmap

We will explore this further; NuGet 3.4 added new abbrebrivations that we will be supporting in the next maintenance release.

Understood! Thanks for the quick response. Btw, it would also be nice to have a "Clear All" button in the recent errors section, because when we start having a ton of the same error, it fills it up and we can't clear them easily. Thanks again!

You might be getting that message if you have Windows Integrated AUthentication enabled; this is unfortunately not supported in the npm client. Otherwise if you follow the steps in the npm tutorial it should work just fine.

This seems to be unrelated; the problem before was that ProGet was not providing a 404 when a package was not found, but instead an empty result. Also, we cannot reproduce this error at all, so it's isolated to yours. As such, please Ask a New Question as not fill this one; and also make sure to provide a stack trace of the 500 error message; this can be found in Admin > Error Logs.

This would require creating an after-push adapter using the sdk. Several folks have done this in their own instances, but we currently don't hav ea tutorial for how exactly to write one;, but the classes should be fairly self-explanatory to assist with this.

Actually, reading your last sentence again, it sounds like I shouldn't use API keys in cases where I want to keep a feed secure. This is probably the best answer correct? Yes, pretty much. I suppose you could think of it as two different sets of doors that could secure a feed --- the first door (LDAP) is quite secure and can be user/group controlled, whereas the second door (API Key) is quite weak and works a bit like a skeleton key that everyone shares. There's zero point in requiring users to unlock two different doors, which is why we say using an API key doesn't make sense when you've enabled LDAP. If you want to use only an API key, then you must bypass the first door by allowing anonymous. This is less secure and generally not recommended.

Thanks! We will have this fixed in ProGet 4.0.14, which will be released within the hour.

Thanks, Tod, but I want to keep all the actions on the client side. I found that I can just do a GET and a PUT, and once I constructed the multi-part form data correctly and added a boundary to the content, it worked.

Connectors can only be filtered by ID, so you'll have to rely on the client to filter by pre-release versions. You can clear the cache on the Manage Feed page.

Hi, upack is the command line client for ProGet universal feeds. We will soon have it available to download from Chocolatey and Inedo.com, but for now you can find it directly at this URL: http://cdn.inedo.com/downloads/proget/upack1.0.0.zip

I'm afraid we don't have that tutorial yet; but we'd like to soon!

ProGet is the server, so it just hosts your private packages. If you want to push something to a different feed, use the -Source ... argument in the nuget.exe client. Connectors for NuGet are simply a convenience that make it easy to cache nuget.org packages and provide a single endpoint to download them.

Ya thats goes well! thanks alot. Its working now.

hi, i think this is not an nuget or chocolatey specific thing. proget has to render the *.nuspec infos. like uget gallery https://github.com/NuGet/NuGetGallery/issues/2280 regards sundayout

Of course, it's possible that NuGet 3.4 works with your proxy servers differently. I don't know. But in either case, it's most definitely a bug in the 3.4 client; a "nuget push" is a very simple HTTP POST or PUT with a body containing a single file with a multi-part encoding, so if you are getting that error, then no file is being sent (unlikely multiple files). You can use cURL or any other tool to send file to ProGet like that. There is nothing we can change on the ProGet's end to work-around this bug, so please report this to the NuGet team. You should use Fiddler or Wireshark to capture the output from NuGet, and find precisely what requests it is struggling with, so you can share it with them.

You can visit this directly (it'll look a bit strange since it's designed to be a modal page): http://{proget-server}/administration/security/users/change-password Apparently you're correct that the link to that is missing, it's supposed to be in the dropdown beneath the user icon - we'll add it back in the next maintenance version.

You can install a separate website in IIS that points to the same home directory, which supports forms authentication, then use that separate URL for npm & bower. With a separate IIS site, upgrading won't touch it so it will upgrade as per normal with the installer.