Nuget Package Manager always reportsNuGet.Protocol.Core.Types.FatalProtocolException

I've tried both the Nuget 3 official package source and our own internal package source, using the same setting I use for VS2017, and both report the same error as above with the detail "Unable to load the service index for source https://api.nuget.org/v3/index.json" (or our internal URL).

I tried setting the proxy server settings to either auto-detect or nothing (as a developer, I have proxy bypass allowed, although the auto-detect will detect the proxy) and also tried manually specifying the proxy. All reported successful for the proxy test, but have no effect on the NuGet Package Manager. Obviously, the local package source shouldn't be affected by proxy anyway!

I then tried the Beta (5.32.01) which reported "Nuget.Core threw an exception: Unable to load the service index for source https://api.nuget.org/v3/index.json. The ServicePointManager does not support proxies with the https scheme.". However, the beta was able to load our internal package index.

Is there any way to fix this or a workaround to directly get NuGet packages from the official source?

If you need more details, let me know how I can provide them.

Thanks.
Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!