I'm a bit of a loss, because we haven't seen such an error before... and it's not something that ProGet would be doing. You may have some IIS setting enabled, that's intercepting requests and ... doing "something" with them? It's really hard to say, because it simply doesn't make any sense, and the solution will not be found looking in ProGet settings/installation. Would suggest to use the integrated web server in this case. Or, use a fresh IIS installation.

You can just back-up the database, and then restore it in the new SQL Server.

This is not a known issue with ProGet or our tools. But I'll note, there is a little bit of a "warm-up" time needed for .NET-based applications; it should be pretty quick (5-10 seconds), but it sounds like your server might be a bit underpowered? Or maybe there is some other thing preventing .NET applications from "warming up" in a fast enough time?

Hello Srinivas, The Push to ProGet extension is specifically for Universal feeds. That error message appears to be coming from a NuGet feed. You can use a generic NuGet Visual Studio plugin to push to a NuGet feed on ProGet.

Hello I installed it using your integrated database installation.

Hello Tom, You are correct that this is caused by the npm feed type not being found. I've filed this as PG-1073 and submitted a fix for review, so it should be fixed in the next version of ProGet.

Tagging would indeed be the solution, now it's clear how we should have been working. Thanks for the fast feedback!

That actually worked out very well, thank you for the information. Looking forward to the next release.

We don't support doing this sort of tweaking on the ProGet database; it might work, but we don't test it so I can't say.

I followed your suggestion of providing a Nuget API key, I got a different error. I found that if I unregistered the repository in PowerShell, and reregistered it, things work as expected when you provide an API key. It appears that Publish-Module does not work without an API key. Since ProGet will ignore it, (assuming the feed is not configured with one), you get the effect of just credential auth. (So might as well put an API key on the feed to avoid confusion.)

I haven't seen the error before, but it appears to be network related. I would suggest switching to IIS, so that you can debug those network problems a lot easier than the integrated web server.

Please refer to these documents from Microsoft: https://docs.microsoft.com/en-us/nuget/create-packages/creating-a-package https://docs.microsoft.com/en-us/nuget/create-packages/symbol-packages If the symbol files are inside of a package, then ProGet will index them.

That is the requirement; the installer requires SQL_Latin1_General_CP1_CI_AS collation in the database, so if it's not that (and the installer can't change it), you won't be able to install ProGet.

ProGet supports overwriting existing packages, provided the user has such a permission.

It's not supported under any hosting (IWS, IIS); our applications must be a "root" application.

3 nodes are only required if the load is such that 2 nodes are needed to handle expected load That's pretty much it! Keep in mind, it's tough for us to generalize things because there are so many different usecases and usages levels. But generally speaking, LB of ProGet is about managing peak usage -- like, when a few developers run their npm builds (requesting thousands of packages) using their 32GB/8-core desktops, that can quickly overpower a server. One server is often not enough for situations like that. Two is probably good enough. Three is pretty good. This is why we say dropping from "probably good enough" to "not enough" is not HA. Also, it's almost always easier and more cost effective for organizations to add another server in the mix than it is to spend the time determining how much they might actually need and risks that not being enough.

I think I determined that the nodes need to reboot after enabling high availability. That seems to resolve the issue. It may also be possible that it just takes time for the servers to report in, and that the console will show an error state until things settle out. (I didn't test that.)

Unfortunately there's nothing for us to go on here; with the limited information we have here, everything appears to be fine (the 401 is to be expected when you have an authenticated feed). Because you're using the unsupported VS2013 NuGet Plugin (which we cannot test with), and you upgraded from an a two-year old version of ProGet with a ton of changes between, we have no idea what is going on. We would need to know precisely which requests worked before (request/response), and precisely what it's doing now. Otherwise, you should just consider rolling back to 3.8.6 until you can upgrade to a supported version of Visual Studio.

Unfortunately Microsoft does not provide this information available in the feed; it's only available for viewing on NuGet.org through a special partnership with third-party software vendor SonaType. This information is proprietary, and only available when purchasing software from SonaType.