Nevermind. It was due to my local cache in ~\AppData\Roaming\npm-cache so npm never tried to fetch them from the server. I cleaned it out and ran npm install and now everything works! Sorry for the noise.

UPDATE: This is a breaking behavior change planned for NuGet 3.4. https://github.com/NuGet/Home/issues/2298 This may not have a large/widespread impact, and it might be difficult for us to fix server side without breaking everything other than NuGet 3.4... so for now our advice is "don't upgrade to 3.4 or don't rely on that behavior". Please update/share if this issue impacts you.

In this case, you will need to diagnose why your computer (client) is unable to connect to the server (ProGet). It could be so many things.... bad wireless reception, the server is turned off, or anything in between. Suggest to use Wireshark to see where packets/information is being lost, or work with your network engineers to see why this is happening.

Please note, the 4.0 upgrade notes discussed the changes to permissions. So in v4, you will just need to edit the "task" that you want to give privileges to.

Unfortunately there's not enough information provided for us to provide any assistance. I'm not sure what feed/package type this is (NuGet, npm, etc), what version you upgraded from, how you're trying to use ProGet, what specific errors you're receiving, etc.

It's hard to say... 3.6 was almost a year ago, and I know the npm api/format specification has likely changed since then. So, it could be a related to that...

You can use the "Anonymous" pseudo-user, but note that "Windows Integrated Authentication" is a protocol (not unlike HTTPS) that requires negotiation by the client/server before getting to the application layer... and unfortunately it's not possible to have WIA enabled on some urls/feeds and not others.

There weren't any major, systematic changes that would have caused this to occur. Most likely ,the service isn't running, etc... I would roll back to the old version, then try to do the upgrade again.

Hi Owen, you can just run the ProGet.Service.exe, and there will be an option to reset the Admin info and directory provider.

Version 2022.24 (Build 5) has an option to unlist all packages on an ID.

Yes, all of our the free/express versions of our products allow for commercial use! Thank you for your interest.

Please see http://inedo.com/support/questions/4360

I bumped into this issue as well. It turns out if you wanna use existing local SQL server, you need to add an account "NT AUTHORITY\NETWORK SERVICE" to your SQL database. To be clear, this account is added to ProGet database during installation but it didn't mark as "Public" in server role.

Unfortunately the behavior of Visual Studio's Debugging/Symbol Serving can be a bit strange; there's not much we can do to control that... however if you carefully follow the tutorial, it should help you get set up!

When I changed IIS to use ONLY Windows Authentication and then changed Proget to Integrated mode, all my problems went away.

Most definitely :) We don't have a target date just yet, but it's on our ProGet Roadmap. I'll add a +1 to the feature. Thanks.

In Chocolatey v0.10.1, we will automatically switch to using better TLS versions when available. This was done in https://github.com/chocolatey/choco/issues/458. If you see this issue when you are attempting to install Chocolatey itself, please see this documentation to understand your options: https://github.com/chocolatey/choco/wiki/Installation#installing-with-restricted-tls

this should be resolved in ProGet 4.0.8.

Hi, the package is superagent-mocker 0.3.0 fetched from registry.npmjs.org: see display in the npmjs.org : display of superagent-mocker 0.3.0 in npmjs org see display in proget