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.

Hello Sam, This should be fixed in version 4.6.4 of progetx-amazon, which is currently being tested.

INdeed; actually, we've updated our documentation on this matter -- and we do have supporting the v3 api on our roadmap now that it's supported by Microsoft.

If you've removed the "Anonymous" pseudo-user from the privileges for the current user directory, then you will see "You are browsing as the anonymous user, therefore certain functionality may be missing. Click the User Icon in the top right to log in.". note that, if you've enabled Windows Integrated Authentication, you will always be logged in as yourself, so you will not be able to go "anonymous".

ProGet will not give this error code, so it's coming from another tool/service in between NuGet.exe and ProGet software. Please disable WebDAV, and any other things sitting in front of the ProGet server that would issue a 405 before relaying the request to ProGet.

Hi @mhull_0872, We just released the latest version of ProGet 5.2.26 on 2/28/2020 which includes the new Package Deployment API. You can learn more about the package deployment tracking feature here. We also have documentation on how to use the API endpoint here. Thanks, Rich

Unfortunately there's not enough information.. or a question here.. for us to be able to provide a meaningful answer. If this just happens as a one off, please ignore it. if it's preventing you from doing something, please describe in deatail what you're trying to do. I already see some strange things, such as "port 44300" that make the set-up seem not very obvious, so please describe that too.

Surfing Pikachu, That was one of the steps I mentioned in my original post. Did not work for this issue. Alana, Already attached Fiddler before original post. Just showed 404's for symbol requests. Downloading the package locally allows the symbols to be found; but using ProGet's symbol server doesn't work.

It's certainly planned on our end, but because it would require a major change to the way we do package indexing, which is a significant risk and thus could impact a lot of our enterprise customers.

Generally, you "subscribe" to a feed to get notifications; however, there will be a "webhook" feature coming soon that will allow you to send webhook notifications to other tools. We will be posting more information about it soon... stay tuned.

Nevermind, I had to grant the Feeds_AddPackage privilege to the Anonymous User.

Ah ha! Thank you so much. I'll look in to this right now :)

I would remove the "NuGet API Key" from your NuGet feed; that is a seperate thing from "ProGet API Keys", which makes it quite confusing. This is why it will be deprecated in v5. You don't need an API key; you can just publish using usename/[password.

As far as we can tell, ProGet has never returned a 409 response from that endpoint. A quick Google search reveals this NuGet bug: https://github.com/NuGet/Home/issues/2910 You can fix this by upgrading to NuGet.exe 3.4.5, NuGet.exe 3.5.0-beta2, or a later version.

A connector will transparently mirror all of the feed, including pre-release versions. So, if you don't want to see pre-release, then disable your connectors to NuGet.org or use multiple feeds.

Ben, That works. Thank you! TLDR; don't use "MultipartFormDataContent" when making this request.

Thanks, Tod. That works. I appreciate it!

In our testing, we couldn't get the maven feed to crash, but I was able to get an "invalid response" error in Google Chrome when requesting a snapshot from a connector, and I did notice that requesting an old version of a snapshot 404s because ProGet finds the correct version number and then overrides it with the latest version number. We're still investigating...

Hello Mark, This is not currently possible due to a bug, but I've filed PG-1059 and submitted some code that will fix this for review.