Nuget connection attempt failed Unable to load the service index for source

Question

While trying to connect to Nuget  I m getting the error below  and then I am unable to connect    nuget org  Unable to load the service index for source https   api nuget org v3 index json  An error occurred while sending the request  Unable to connect to the remote server A connection attempt failed because the connected party did not properly respond after a period of time  or established connection failed because connected host has failed to respond 68 232 34 200 443  I am able to access https   api nuget org v3 index json on my browser  This question is not a duplicate  The other answers don t solve my problem

User · Answer

I had a similar problem while trying to execute Install-Package Modernizr on Visual Studio 2015. I fixed my problem by following the below steps:

Download the package from its online source.
Go to Tools/NuGet Package Manager/Package Manager Settings.
Select Package Sources from the window.
Add a new package source by clicking on the + sign. Enter a name and source location by clicking on ... (triple dot) sign.
Make sure that only the package source that you've just added is checked. Uncheck all the other package sources.
Go to Package Manager Console and type Install-Package Modernizr.
Visual Studio 2015 installs the package automatically and creates Scripts and packages folders in your root folder.

I hope the same solution works while installing other packages, too.

User · Answer

I was getting the same error while trying to browse the NuGet Package  to resolve the same followed below step  1- go to   appdata  NuGet NuGet config  2- Verify the urls mentioned in that config   3- Remove the url which is not required   4- Restart visual studio and check

User · Answer

If using Visual Studio 2019  just delete the  defaultproxy  section if you are not using any default proxies in devenv exe config  in VS 2017 this section was not present  change    lt defaultProxy enabled  true  useDefaultCredentials  true  gt       lt proxy bypassonlocal  True  proxyaddress  http    lt yourproxy port  gt    gt   lt  defaultProxy gt    to   lt  -- lt defaultProxy enabled  true  useDefaultCredentials  true  gt       lt proxy bypassonlocal  True  proxyaddress  http    lt yourproxy port  gt    gt   lt  defaultProxy gt -- gt    Else provide the appropriate proxy username and password

User · Answer

Setting of your PC -  Network And Internet Proxy -  Automatic Proxy Setup then set Automatically detect settings to off and clear the Script Address

User · Answer

It seems Nuget still uses the proxy script address  for our VPN  even though the proxy settings are disabled  I removed the script address and it works

User · Answer

In my case  the problem was that I was building on a  older virtual machine which was based on Win7  I found this fix from https   github com NuGet NuGetGallery issues 8176 issuecomment-683923724    nuget org started enforcing the use of TLS 1 2  and dropped support for TLS 1 1 and 1 0  earlier this year  Windows 7 has TLS 1 2 disabled by default  check the DisabledByDefault value under HKLM SYSTEM CurrentControlSet Control SecurityProviders SCHANNEL Protocols TLS 1 2 Client in your registry   To enable the support  please make sure you have an update     installed and switch the support on  reg add HKLM SYSTEM CurrentControlSet Control SecurityProviders SCHANNEL Protocols TLS 1 2 Client quot   v DisabledByDefault  t REG DWORD  d 0  f  reg 32 reg add  quot HKLM SYSTEM CurrentControlSet Control SecurityProviders SCHANNEL Protocols TLS 1 2 Client quot   v DisabledByDefault  t REG DWORD  d 0  f  reg 64 reg add  quot HKLM SYSTEM CurrentControlSet Control SecurityProviders SCHANNEL Protocols TLS 1 2 Client quot   v Enabled  t REG DWORD  d 1  f  reg 32 reg add  quot HKLM SYSTEM CurrentControlSet Control SecurityProviders SCHANNEL Protocols TLS 1 2 Client quot   v Enabled  t REG DWORD  d 1  f  reg 64   The     update referred to was Microsoft kb3140245  Update for Windows 7  KB3140245  I installed the update  rebooted  as requested by the update   added those registry keys  and then Nuget worked fine

User · Answer

go to  appdata  NuGet NuGet config  Modify this line   lt packageSources gt       lt add key  quot Microsoft Visual Studio Offline Packages quot  value  quot C  Program Files  x86  Microsoft SDKs NuGetPackages  quot    gt       lt add key  quot Package source quot  value  quot https   api nuget org v3 index json quot    gt   lt  packageSources gt

User · Answer

Go to   Settings   Global Settings of your PC     Network and Internet   Proxy   Automatic Proxy Setup   and set Automatically detect settings to off

User · Answer

The error can be caused by just temporary network issue  and disappear  if try again

User · Answer

Go to -  Tools -  Extensions and Updates and uninstall NuGet package manager   restart visual studio and reinstall it     every thing will set to normal

User · Answer

In my case it is happened because I don   t have internet connection and it is trying to scaffolding

User · Answer

In my case  I just restarted the docker and just worked

User · Answer

I have resolved this issue using below steps  Click on run search this  APPDATA  NuGet NuGet config   Open the setting and add this http proxy keyin NuGet config    Then you will able install the BouncyCastle Crypto dll in your application    Thank you  Responses are welcome if you help this answer

User · Answer

I had the same error message while scaffolding Identity to my ASP NET Core MVC project  Since my connection was not behind a proxy  removing editing proxy configurations didn t make sense  And I didn t want to delete a file or uninstall PMC either  While looking around I realized a  quot Clear All Nuget Cache s  quot  button on Tools -- gt  Options -- gt  NuGet Package Manager -- gt  General  After pressing the button I had to wait for some time for the operation to complete  After that I tried to scaffold the Identity again but it didn t work  Then I decided to restart VS and voila

User · Answer

Maybe this helps      For me removing the  nuget folder located in C  Users YourNameHere fixed the problem

User · Answer

I encountered this error when trying to set up NuGet packages inside locally hosted Gitlab instance   The error indicated 401 Unauthorized code   The solution was removing offending source with  nuget source Remove -Name SOURCE NAME  And then adding the same source  but this time specifying the username and password in the command  nuget source Add -Name SOURCE NAME -Source SOURCE URL -UserName GITLAB DEPLOY TOKEN USERNAME -Password GITLAB DEPLOY TOKEN

User · Answer

Open Registry Editor by pressing Win   R and type regedit Enter Navigate to   HKEY LOCAL MACHINE SYSTEM CurrentControlSet Control SecurityProviders SCHANNEL Protocols TLS 1 3 Client  Change the value of DisabledByDefault key 0 to 1 Then restart the Visual Studio  Read more about TLS Read more about this issue w r t  NuGet

User · Answer

Some development environment may not be using neither a browser nor a proxy    One solution would downloading the package from nugget such as the https   dotnet myget org F dotnet-core api v3 index json to a shared directory then execute the following   dotnet add package Microsoft AspNetCore StaticFiles -s  shared drive  index json    I hope that works for you   nbsp

User · Answer

If you see error as follow  you may need to set up your Azure Artifacts Credential  see this Github link  you could either install the credential provider by running a powershell script or manually  error     Response status code does not indicate success  401  Unauthorized

User · Answer

Installing fiddler was causing me similar problem  Uninstalling fiddler and removing the fiddler proxy from the machine config  from both Framework and Framework64  solved the problem

User · Answer

You need to add proxy settings into Nuget Config file  Refer to this link for details  Nuget Config Section  amp  Nuget Proxy Settings

User · Answer

I was trying to add an Azure Artifacts NuGet source   I followed Microsoft s instructions here  with one critical oversight   I forgot to replace  v3 index json with  v2

User · Answer

In support of the answer provided by  Eddie Chen  here  I had to add http proxy setting to following file as well   C  Windows system32 config systemprofile AppData Roaming NuGet NuGet Config   lt add key  http proxy  value  http   your proxy url 8080    gt

User · Answer

In my case i had had Fiddler running which had changed my proxy settings

User · Answer

It is worth noting that there was a bug with  net core SSL authentication that could cause this  Disabling their latest networking stack implementation  solved this issue for me   You can set this permanently or just launch your app using   DOTNET SYSTEM NET HTTP USESOCKETSHTTPHANDLER 0 dotnet

User · Answer

Make sure docker is running in your local machine  build command will work but its required running docker to get network data   I think it will help

User · Answer

in my case i had to add the sources in the Visual studio Options- NugetPAckageManager- sources and then restart the visual studio command prompt

User · Answer

I had this error and then I realized I was logged in with my personal Microsoft account instead of my work account   Hope this helps

User · Answer

Deleting the  AppData  NuGet NuGet Config and restarting VS2019 worked for me  Similar to https   github com NuGet Home issues 3281

User · Answer

I have stumbled across this issue when trying to run nuget exe via Jenkins  configured as a service  by default using Local System account   I have edited C  Windows System32 config systemprofile AppData Roaming NuGet NuGet Config file which looks like the following    lt  xml version  1 0  encoding  utf-8   gt   lt configuration gt       lt config gt           lt add key  http proxy  value  http   proxy hostname or ip 3128    gt           lt add key  https proxy  value  http   proxy hostname or ip 3128    gt       lt  config gt      lt packageSources gt       lt add key  nuget org  value  https   api nuget org v3 index json  protocolVersion  3    gt     lt  packageSources gt    lt  configuration gt     In order to test command prompt can be started via PSTools   psexec -i -s CMD   and actual test run in the newly created cmd windows  runs as Local System    path to nuget nuget exe restore  path to solution theSolution sln

User · Answer

If you are behind a company proxy and on Mac  just make sure your http https checkboxes are checked and applied

User · Answer

I was getting this same error while running RUN dotnet restore in my Dockerfile using docker-compose up command in Windows 10      I have tried all the possible solution provided on the internet and was also keep an eye on this open issue  Finally  after spending more than 8 hours  by following the preceding steps  I was able to fix my issue    Uninstall Docker from your system Restart your system Install Docker from this link  Below is the version of my Docker   Restart your system Start Docker for Windows  search Docker in the search bar in Windows  Make sure it is running  You should also go to Services msc and make sure the services Docker Engine and Docker for Windows Service are running    At last  you must check your Nuget config file from C  Users  Username  AppData Roaming NuGet  For me  the content of that file was as below    lt  xml version  1 0  encoding  utf-8   gt   lt configuration gt     lt packageSources gt       lt add key  nuget org  value  https   api nuget org v3 index json    gt     lt  packageSources gt     lt packageRestore gt       lt add key  enabled  value  True    gt       lt add key  automatic  value  True    gt     lt  packageRestore gt     lt bindingRedirects gt       lt add key  skip  value  False    gt     lt  bindingRedirects gt     lt packageManagement gt       lt add key  format  value  0    gt       lt add key  disabled  value  False    gt     lt  packageManagement gt   lt  configuration gt   Hope this helps

User · Answer

I couldn t resolve the problem itself  but found a way to install packages  Just specify nuget org as a source directly in Package Manager Console  Update-Package -reinstall -Source nuget org

User · Answer

nuget restore   and msbuild  t restore  both didn t work for me with same error  But dotnet restore   worked perfect  Try that

User · Answer

Something may have change your proxy setting  like Fiddler  Close Fiddler  then close Visual Studio and open it again

User · Answer

I had a similar issue trying to connect to my private TFS server instead of the public NuGet API server  For some reason I had an issue between the AD server and the TFS server so that it would always return a 401  The NuGet config article shows that you can add your AD username and password to the config file like so      lt packageSourceCredentials gt         lt vstsfeed gt             lt add key  Username  value  yourname company com    gt             lt add key  Password  value  this is an encrypted password   gt             lt  -- add key  ClearTextPassword  value  not recommended password  -- gt         lt  vstsfeed gt     lt  packageSourceCredentials gt    This is not quite an ideal solution  more of a temporary one until I can figure out what the problem is with the AD server  but this should do it

User · Answer

I m using VSO Azure DevOps   You can also visit the feed url directly in your browser   You may end up with a response that contains a message like this  which may make your diagnosis a lot quicker   The user does not have a license for the extension ms feed

User · Answer

If you are getting this error  but you don t have a proxy server  you can go to   userprofile  AppData Roaming NuGet NuGet Config   And comment this lines    lt config gt        lt  -- Proxy settings -- gt        lt add key  http proxy  value  host    gt        lt add key  http proxy user  value  username    gt        lt add key  http proxy password  value  encrypted password    gt   lt  config gt    It worked for me because I was getting that error  but I don t have a proxy server

User · Answer

I was using an older version of Nuget on VS2010  where it defaults to TLS 1 0 here it can be fixed by changing the default TLS version used by  Net framework which is configured in Registry keys  reg add HKLM SOFTWARE Microsoft  NETFramework v4 0 30319  v SystemDefaultTlsVersions  t REG DWORD  d 1  f  reg 64  reg add HKLM SOFTWARE Microsoft  NETFramework v4 0 30319  v SystemDefaultTlsVersions  t REG DWORD  d 1  f  reg 32   FYI      NuGet org will permanently remove support for TLS 1 0 and 1 1 on June 15th  Please ensure that your systems use TLS 1 2    You can refer to this link for info on TLS 1 2 support

[.net] Nuget connection attempt failed "Unable to load the service index for source"

Examples related to .net

Examples related to visual-studio

Examples related to nuget