Error when using connector to MyGet

Hi,

Since we have migrate to ProGet version 4, we are no more able to "really" connect to our MyGet feed.

What happen is that the status of the connector is Healthy, on the connectors page, but when we try to do research for a package on the ProGet feed (that use this connector), we receive 500 error. Also the ProGet Feed is not up to date with the MyGet feed, only the cache package display and are acessible.

We use the NuGet v2 feed URL from MyGet ( because the v3 feed URL return 404 error).

Can you help us with this? For now we had try to delete the connector, use the feed address with and without pre-authenticated information and create new feed using this connector and nothing works.

Thanks,

Alexandre Beaudoin

Product: ProGet
Version: 4.1.2

If the feed is reporting "healthy" that means that an initial check passed.

The 500-status errors will be logged on Admin > Error Logs; without seeing those, it's not really possible for us to advise on what the issue is. Hopefully that will give insight as to what could be failing.

You may need to attach a proxy server between ProGet and MyGet (e.g., install Fiddler on the server, then point ProGet to use the Fiddler proxy), in order to capture the traffic.