You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I did some investigation and the same issue can be reproduced on my (windows) box by running: dotnet restore in the src folder. I get:
C:\Program Files\dotnet\sdk\5.0.103\NuGet.targets(131,5): error : Unable to load the service index for source https://www.myget.org/F/dotnet-corefxlab/api/v3/index.json. [C:\i\s\MineCase\src\MineCase.sln]
C:\Program Files\dotnet\sdk\5.0.103\NuGet.targets(131,5): error : The SSL connection could not be established, see inner exception. [C:\i\s\MineCase\src\MineCase.sln]
C:\Program Files\dotnet\sdk\5.0.103\NuGet.targets(131,5): error : The remote certificate is invalid according to the validation procedure: RemoteCertificateNameMismatch [C:\i\s\MineCase\src\MineCase.sln]
Indeed when I try to retrieve that index.json file, I get cert errors and redirected to a website (not the index.json file).
Probably only manifests on the first restore (folks that had restored when that nuget source was up/working would have the correct packages cached). I think you'd have to do a nuget restore --no-cache to see it?
Anyway, anyone have a guess as to where those nuget packages reside now? What would be the correct nuget source url?
The text was updated successfully, but these errors were encountered:
On a brand new clone:
.\build_and_run.bat
It fails during the build process.
I did some investigation and the same issue can be reproduced on my (windows) box by running:
dotnet restore
in thesrc
folder. I get:Indeed when I try to retrieve that index.json file, I get cert errors and redirected to a website (not the index.json file).
Probably only manifests on the first restore (folks that had restored when that nuget source was up/working would have the correct packages cached). I think you'd have to do a
nuget restore --no-cache
to see it?Anyway, anyone have a guess as to where those nuget packages reside now? What would be the correct nuget source url?
The text was updated successfully, but these errors were encountered: