@rhessinger It is, yes.

@atripp
Alternatively, is there a way to stop outbound requests being made to a nuget.org connector? For example, there is no point asking nuget.org for packages that we host on our own internal feeds.

Thanks,

Mike.

Hi Rich,

Web.BaseUrl was already set to "http://crn-ppfs02/". Is that what you meant?

Thanks,

Mike.

@atripp Hi, thanks for your reply. Understood. I'll start with getting the clients to use the v3 endpoint to the local feeds. Hopefully then things will stay in the v3 world.

Hi,

We are on 5.3.11 Free Edition, a single instance. We have multiple feeds to allow us to structure them as we wish and we have some connectors back onto this instance to aggregate feeds and make consuming them simpler. However, we are getting thousands of license violations recorded even though this is all on the same instance. We have no proxy servers involved but we do have more than one layer of connector/feed. For example:

Feed A -> Connector B -> Feed C
-> Feed D -> Connector E -> nuget.org

Could this be causing it?
Another thought: our feed and connector urls use the DNS name of the server and not the IP address. Could this make a difference?

We also have errors logged when recording violations, which looks like a straight up bug to me?

Unhandled exception recording license violation: Violation of UNIQUE KEY constraint 'UQ__ProGetLicensingViolations__Lookup_Hash'. Cannot insert duplicate key in object 'dbo.ProGetLicensingViolations'. The duplicate key value is (15, 0xa9e4198114110a2e3ee3ed859e66e9c91c469cca9bacfc55c952a2ae03e035b6). The statement has been terminated.

Thanks in advance.

Mike.

Hi,

We have just upgraded to 5.3.11, hoping to be able to avoid "429 Too Many Requests" responses from nuget.org by moving to use their v3 api. However, we are still getting these errors despite having only a single connector to nuget.org and that being configured with the v3 url. In addition, the upgrade notes (https://inedo.com/support/kb/1767/proget-5-3-upgrade-notes#nuget-v3-api) state that ProGet will use v3 regardless of what is configured. This doesn't appear to be the case for us.

We do have clients connecting to our local ProGet feeds using the ODATA format/urls. Does that make the connector use the same onto nuget.org?

Thanks in advance.

Mike.