To improve discovery, we can add a log which writes out the fingerprint of the certificate that failed SSL validation at the error level. We should also consider adding an environment variable to set this value., To use an HTTP source, you must explicitly set 'allowInsecureConnections' to true in your NuGet.Config file. Please refer to https://aka.ms/nuget-https-everywhere for more information., In my case, I was trying to install a dotnet global tool, and for some frustrating reason it kept trying to use a myget nuget source, even though there was no reason for that., It worked previously, but now complains about HTTP sources on our local network being insecure. The command suggest using allowInsecureConnections, but it's not possible to set that option via CLI., I am having issue in building a source code . It uses nuget public repo and private . both of them fails to build and gives error of certificate . i have tried adding config in nuget.config file but unable to find path to solution ., Of course, when I configured the address in Nuget.config file to http protocol + not ssl port - it is all works fine. Therefore, I expecting a flag which mean “skip-ssl-verification” (like in curl, npm, docker and more) ..