Nuget connector not working properly

[jyip_5228]

I have noticed that since upgrading to v5.3.5 Proget, the connector/nuget feed is not working properly. For example I am trying to download CommonServiceLocator.1.3.0.0.nupkg, it is an external package in the public nuget server. This is what i get when running in CLI

C:\Dev\Nuget>nuget install CommonServiceLocator -Version 1.3.0 -Source https://localprogetserver/nuget/ks-nuget/
Feeds used:
  C:\Dev\NuGet\packages
  https://localprogetserver/nuget/ks-nuget/

Attempting to gather dependency information for package 'CommonServiceLocator.1.3.0' with respect to project 'C:\Dev\Nuget', targeting 'Any,Version=v0.0'
Gathering dependency information took 342 ms
Attempting to resolve dependencies for package 'CommonServiceLocator.1.3.0' with DependencyBehavior 'Lowest'
Resolving dependency information took 0 ms
Resolving actions to install package 'CommonServiceLocator.1.3.0'
Resolved actions to install package 'CommonServiceLocator.1.3.0'
Retrieving package 'CommonServiceLocator 1.3.0' from 'https://localprogetserver/nuget/ks-nuget/'.
  GET https://localprogetserver/nuget/ks-nuget/package/CommonServiceLocator/1.3
  NotFound https://localprogetserver/nuget/ks-nuget/package/CommonServiceLocator/1.3 152ms
WARNING: Install failed. Rolling back...
Executing nuget actions took 199 ms
Package 'CommonServiceLocator.1.3.0' is not found on source 'https://localprogetserver/nuget/ks-nuget/'.

In the pictures above, it shows that its clearly available online through the external connector.
Prior/ expected result when I try to install a nuget package not on our local proget server is that I get proxied out to the external nuget.org and get the installation.

Please assist.

[jyip_5228]

I might have found a temporary fix by utilizing enabling and utilizing v3 api, running this allows it to install perfectly fine it seems.

nuget install CommonServiceLocator -Version 1.3.0 -Source https://localnugetserver/nuget/ks-nuget/v3/index.json

can someone look into this issue/ verify that it is not just me having the issue?

[apxltd]

Hard to say, but there were some bugs with NuGet.org, where some packages would not show up when queried through the v2 API, but would come with v3. I wonder if it's related to you using a v3 API connector, but a v2 API call to ProGet? It should work.

You can append #v2 to a nuget.org connector's API to force it to use the v2 api instead of the v3.

[jyip_5228]

I tested the following: changing the nuget connector to utilize v2. The effect is the same where I cannot pull from nuget.org. This definitely worked prior to v5.3

Right now i have proget running a v3 api for the feed with a v2 connector and it is working fine so far.

I believe its a bug when the feed is running v2.