Source ошибка unable to load

-> R332380971217
-> Z401067074716

Связь!
Skype-mapbynoy
Мой ник DoSs_+

asked Dec 16, 2016 at 13:24

I was getting the same error while trying to browse the NuGet Package, to resolve the same followed below step:

1- go to %appdata%NuGetNuGet.config

2- Verify the urls mentioned in that config

3- Remove the url which is not required

4- Restart visual studio and check

A developer of the nuget-package manager suggested in 2019 to disable tls 1.3 as a workaround (see issue 7705).

Open Registry Editor by pressing Win + R and type regedit Enter

Navigate to:

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSecurityProvidersSCHANNELProtocolsTLS 1.3Client

Change the value of DisabledByDefault key 0 to 1

Then restart the Visual Studio.

Read more about TLS on wikipedia
Read more about issue 7705 w.r.t. NuGet at github

3rd party edit

Be aware that this disables tls 1.3 for the os not just for nuget or dotnet.
Windows 10 version 1909 did contain an experimental implementation of TLS 1.3 but later versions should be fine. Based on one answer from Unable to browse nuget packages you can test if tls is the problem via a console programm

static async Task Main(string[] args)
{
    var client = new HttpClient();
    string uri = "https://apiint.nugettest.org/v3-index/index.json";
    var response = await client.GetAsync(uri);
    string msg = "If you see this, your machine has no TLS/SSL issues with nuget.org";
    Console.WriteLine(msg);

}

Go to

Settings ( Global Settings of your PC ) > Network and Internet > Proxy > Automatic Proxy Setup > and set Automatically detect settings to off.

answered Sep 30, 2017 at 6:43

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).

answered Jul 1, 2020 at 15:15

This can also happen due to authentication issues, so you may need to re-authenticate to Visual Studio.

In that case, you can simply run the following command from the folder where your package.config file is located (usually you project’s root):

dotnet restore --interactive

You will be prompted to visit a pairing URL from your browser and enter a pairing code, for instance:

To sign in, use a web browser to open the page https://microsoft.com/devicelogin and enter the code C2DEJ87H to
authenticate.

This requires the .NET CLI, which is included in the .NET Core SDK that can be installed from https://learn.microsoft.com/en-us/dotnet/core/install/windows

Furthermore, if no sign-in prompt appears upon running the nuget restore command, your installation may be missing the artifacts-credprovider nuget plugin, which you can install with:

iex "& { $(irm https://aka.ms/install-artifacts-credprovider.ps1) }"

answered Oct 25, 2022 at 15:00

answered Aug 30, 2022 at 12:48

Simple :

1. Close VS2019
2. Go to C:UsersyouAppDataRoamingNuGet
3. Delete the file NuGet.Config
4. Relaunch VS2019

You’re good to go !

answered Sep 22, 2021 at 14:20

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:

  <packageSourceCredentials>
      <vstsfeed>
          <add key="Username" value="yourname@company.com" />
          <add key="Password" value="this is an encrypted password" >
          <!-- add key="ClearTextPassword" value="not recommended password" -->
      </vstsfeed>
  </packageSourceCredentials>

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.

answered Nov 8, 2019 at 16:10

In my case, the problem was that I was building on an older Win7 virtual machine.

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
HKLMSYSTEMCurrentControlSetControlSecurityProvidersSCHANNELProtocolsTLS 1.2Client in your registry). To enable the support, please make sure you have an update (*) installed and switch the support on:

reg add HKLMSYSTEMCurrentControlSetControlSecurityProvidersSCHANNELProtocolsTLS 1.2Client" /v DisabledByDefault /t REG_DWORD /d 0 /f /reg:32
reg add "HKLMSYSTEMCurrentControlSetControlSecurityProvidersSCHANNELProtocolsTLS 1.2Client" /v DisabledByDefault /t REG_DWORD /d 0 /f /reg:64
reg add "HKLMSYSTEMCurrentControlSetControlSecurityProvidersSCHANNELProtocolsTLS 1.2Client" /v Enabled /t REG_DWORD /d 1 /f /reg:32
reg add "HKLMSYSTEMCurrentControlSetControlSecurityProvidersSCHANNELProtocolsTLS 1.2Client" /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.

answered Dec 23, 2020 at 13:13

Prince OwenPrince Owen

1,10510 silver badges19 bronze badges

Michael FreidgeimMichael Freidgeim

26.1k16 gold badges149 silver badges169 bronze badges

answered Jun 1, 2018 at 22:36

If you are getting this error, but you don’t have a proxy server, you can go to

%userprofile%AppDataRoamingNuGetNuGet.Config

And comment this lines:

<config>
     <!-- Proxy settings -->
     <add key="http_proxy" value="host" />
     <add key="http_proxy.user" value="username" />
     <add key="http_proxy.password" value="encrypted_password" />
</config>

It worked for me because I was getting that error, but I don’t have a proxy server.

firetiger77firetiger77

3413 silver badges8 bronze badges

answered Oct 29, 2019 at 9:43

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 HKLMSOFTWAREMicrosoft.NETFrameworkv4.0.30319 /v SystemDefaultTlsVersions /t REG_DWORD /d 1 /f /reg:64

reg add HKLMSOFTWAREMicrosoft.NETFrameworkv4.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

answered Jun 17, 2020 at 5:33

David CastroDavid Castro

1,74321 silver badges20 bronze badges

imsanimsan

3493 silver badges15 bronze badges

answered Sep 20, 2017 at 0:47

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.

answered Jun 3, 2019 at 14:49

nuget restore 

and

msbuild /t:restore

both didn’t work for me with same error. But

dotnet restore 

worked perfect. Try that

answered Oct 2, 2020 at 5:54

In my case i lost the connection with Git. I just added the connection again and it worked!:

answered Jan 24, 2022 at 15:37

OK I tried all the answers above and hope my registry is not now hosed. But this appears to have fixed it for me:

https://learn.microsoft.com/en-us/answers/questions/959588/visual-studio-2022-won39t-connect-to-nuget.html

Add this: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384

To the comma-separated string in this:

HKLMSOFTWAREPoliciesMicrosoftCryptographyConfigurationSSL0010002

I hope this helps the next person who hope to make a fun quick Saturday morning proof-of-concept, and then winds up spending 3 hours searching for a fix!!!

answered Aug 13, 2022 at 20:34

In support of the answer provided by @Eddie Chen (here) I had to add http_proxy setting to following file as well:

C:Windowssystem32configsystemprofileAppDataRoamingNuGetNuGet.Config

<add key="http_proxy" value="http://your_proxy_url:8080" />

answered Nov 17, 2017 at 2:43

DooieDooie

1,6297 gold badges30 silver badges47 bronze badges

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.

answered Mar 4, 2019 at 18:07

При старте появляется данный вывод:
——————————————————————————
CSS server
Auto detecting CPU
Using SSE2 Optimised binary.
Server will auto-restart if there is a crash.
AppFramework : Unable to load module bin/engine_i686.so!
Unable to load interface VEngineCvar003 from bin/engine_i686
——————————————————————————
Пробовал патчить с помощью ugsp и на 4-м пункте ловил данную ошибку:
——————————————————————————
4) Looking for client’s network Class check …
Not Found

Saving changes to file… DISABLED(Patching Failed)
——————————————————————————
Также качал другие готовые сборки и проблема аналогичная.

Много искал в интернете и куча всего попробовал, но к сожалению ничего не помогло. Тех. поддержка отправила на форум

OC — Ubuntu 20, доустановил только что 2 библиотеки и сервер теперь просто виснет на:
————————————-—
CSS server
Auto detecting CPU
Using SSE2 Optimised binary.
Server will auto-restart if there is a crash.

Console initialized.
Game.dll loaded for «Counter-Strike: Source»
maxplayers set to 32
Unknown command «s»
Unknown command «ementt»
Unknown command «stuff»
Unknown command «/»
Unknown command «stuffcmdstuffcmds»
Unknown command «s»
Unknown command «cmds»
Unknown command «cmdcmds»
Unknown command «cmds»
Network: IP ***, mode MP, dedicated Yes, ports 27016 SV / 27005 CL

rrelyea

changed the title
Package Manager Error: Unable to load the service index for source

Package Manager Error: Unable to load the service index for source (bad proxy settings)

Jun 28, 2016

d4nt

mentioned this issue

Apr 21, 2020

MikaelMayer

added a commit
to dafny-lang/dafny
that referenced
this issue

Nov 8, 2021