Базовое соединение закрыто непредвиденная ошибка при передаче visual studio

I want to install Microsoft ASP.NET Identity Core through the use of Manage Nuget Packages, but when I click the install button the following error occurs:

The underlying connection was closed: An unexpected error occurred on a send

asked Dec 7, 2013 at 19:32

Try pasting the following into a .reg file and run it. Then try running your NuGet command (no reboot required).

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINESOFTWAREMicrosoft.NETFrameworkv4.0.30319]
"SchUseStrongCrypto"=dword:00000001

[HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoft.NETFrameworkv4.0.30319]
"SchUseStrongCrypto"=dword:00000001

Ran into this issue because TLS1.2 was not enabled (similar to Tony’s response). Using http does not fix the situation because NuGet redirects to https now that TLS1.2 is enforced.

answered Dec 7, 2018 at 23:00

neoscribeneoscribe

2,0931 gold badge20 silver badges18 bronze badges

answered Dec 19, 2013 at 21:00

Ali Gol GolAli Gol Gol

7657 silver badges14 bronze badges

I got this error on an old customer developer VM with Microsoft Visual Studio Premium 2012:

Install-Package : An error occurred while loading packages from
‘https://nuget.org/api/v2/’: The underlying connection was closed: An
unexpected error occurred on a send

enter image description here

Solved it by going to Tools -> Extensions and Updates… -> Updates -> Visual Studio Gallery and Updated NuGet Package Manager from there.

enter image description here

After reboot everything worked:

enter image description here

answered Feb 4, 2020 at 13:22

OgglasOgglas

56.9k32 gold badges309 silver badges387 bronze badges

NuGet has removed support for TLS 1.0 and 1.1 as of June 15, 2020.
See https://devblogs.microsoft.com/nuget/deprecating-tls-1-0-and-1-1-on-nuget-org/

If you are using VS2013 or less you have lost NuGet connectivity as of this date and you will only be able to use NuGet by upgrading at least to VS2015, although I would suggest upgrading to VS2019 to be at the latest at time of this comment.

answered Jul 3, 2020 at 19:53

This can also happen if you don’t have TSL 1.0 enabled (disabled by default in Server 2012R2). In this case you may see some packages installing successfully before you hit the ‘The underlying connection was closed: An unexpected error occurred on a send’ error.

For more details on the error, run nuget install from the command line using «Verbosity detailed»

i.e.

System.Net.WebException: The underlying connection was closed: An unexpected err
or occurred on a receive. —> System.ComponentModel.Win32Exception: The client
and server cannot communicate, because they do not possess a common algorithm

Tony Hinkle

4,6867 gold badges22 silver badges35 bronze badges

answered Jun 15, 2016 at 16:30

This can happen if your firewall is doing SSL inspection. You may need to white list the repo.

answered Oct 16, 2015 at 18:25

The only thing that helped me was switching from Windows 7 to Windows 10.
For people like me who don’t really like updates details are described below.

As @Rob Farquharson have said above Nuget team threw away support for tls 1.0 and 1.1.

Some confusion is introduced by the fact that the https://api.nuget.org/v3/index.json opens perfectly through the browsers. Nevertheless, through Visual Studio we get an error «Unable to load the service index for source».

[nuget.org] Unable to load the service index for source
https://api.nuget.org/v3/index.json. An error occurred while sending
the request. The underlying connection was closed: An unexpected
error occurred on a send. Unable to read data from the transport
connection: An existing connection was forcibly closed by the remote
host. An existing connection was forcibly closed by the remote host

This happens because the browser like Chrome and Firefox maintain and ship their own ciphers. .NET applications however rely on the ciphers provided by the OS. And therefore no action will help if support is not implemented at the OS level.

Neither suggestions here nor in the question Nuget connection attempt failed «Unable to load the service index for source» could help me. I’ve tried approximately 10 various ways to solve the desribed issue.

I’ve checked registry 3 times. Installed kb3140245 twice and did others stepd for activates tls 1.2, but none of them helped. Updating VS2019 from 16.4 (released in december 2019) to 16.11.8 (released in december 2021) didn’t help either.

After that I installed brand new Windows 10 with Visual Studio 2019 and error went away.

answered May 27, 2022 at 16:21

Typically this is related to the webserver not having a valid SSL certificate. An invalid SSL certificate can be due to it being self-signed and not trusted by a CA, or the certificate has been revoked by the CA.

Using the unauthenticated URL can be a workaround for the issue however the solution to the problem is to ensure the SSL certificate is valid.

answered Jul 30, 2015 at 21:03

In my case, we have rules blocking .EXE downloads, so we keep a copy of NuGet.exe in the .nuget solution folder, right next to NuGet.targets and NuGet.Config

For whatever reason, this was missing in the new branch.

answered Feb 26, 2020 at 19:18

CZahrobskyCZahrobsky

7157 silver badges7 bronze badges

Источник

Remove From My Forums

Вопрос
При попытке выполнить «вход» в Visual Studio 13 выходит ошибка: «Базовое соединение закрыто: непредвиденная ошибка при передаче». Войти необходимо для регистрации продукта, но из-за этой ошибки никак не получается ((

Ответы

Решение проблемы нашел
здесь

Касперский блокировал канал )
- Помечено в качестве ответа
  Kadykov Michael
  30 января 2015 г. 10:48

Все ответы

Было дело. Попробуйте восстановить Windows или удалить и установить студию ещё раз.

Сделаем содержимое сообщества лучше, вместе!
Переустановил студию… удалил и поставил заново, не помогло ((

может есть еще какие варианты?
Попробовал официально обратиться в поддержку Microsoft, благо, есть действующая подписка MSDN и статус партнера… но не тут-то было ((

выбираю продукт — Visual Studio 13 Prof …выбираю проблему — Установка… выбираю подпункт Регистрация и лицензирование… если кто не понял, проблема с регистрацией и лицензированием при установке VS 13…

следующим пунктом надо ввести КОД ПРОДУКТА!!! (который необходим, для бесплатной техподдержки)…который я как раз и не могу получить из-за этого (censored) глюка, по поводу которого и хочу обратиться в техподдержку!

Отсюда два вопроса:

1. т.к. проблема висит уже третий день, третий день ни с кем из Microsoft связаться не могу… могу ли я на данном ресурсе уже ругаться матом?

2. КАК можно получить прямую ТП от Microsoft??? если их сайты такие кривые? …может кто знает секретный e-mail или телефон по которым можно связаться хоть с кем-то?? ((( Увы, ни на одном ресурсе не нашел ни
одного способа обратной связи ((((
- Изменено
  Kadykov Michael
  28 января 2015 г. 19:44
Добрый день.

1. Здесь этого не оценят.

2. Здесь нет сотрудников MS, кроме модераторов. Остальные добровольцы. Если у кого из нас и есть какие-то контакты, то они, как правило, получены при личных контактах и разглашению не подлежат.

У вас используется Proxy? Если да, то проблема в нем. Убедитесь что он прописан в IE и вы на нем авторизованы именно из IE. Попробуйте подключить устройство на котором вы устанавливаете VS к Internet без Proxy.
По поводу п. 1. это была грустная шутка ((

Прокси нет, пробовал заходить с разных соединений (работаю на ноутбуке)…
А там всякие Office и/или колендарь нормально конектятся под LiveId? Просто эта ошибка с высокой вероятностью именно клиента. Нет, теоретически, может и сервера, но в этом случае здесь было бы намного больше вопросов
аналогичных вашему…
Я даже не сомневаюсь, что ошибка именно на клиенте, вопрос в том, как ее исправить…

А где Office должен коннектиться под LiveId?
Решение проблемы нашел
здесь

Касперский блокировал канал )
- Помечено в качестве ответа
  Kadykov Michael
  30 января 2015 г. 10:48

Источник

title

description

ms.date

ms.topic

helpviewer_keywords

ms.assetid

author

ms.author

manager

ms.workload

ms.prod

ms.technology

Troubleshoot network or proxy errors

Find solutions for network- or proxy-related errors that you might encounter when you install, update, or use Visual Studio behind a firewall or a proxy server.

1/6/2023

troubleshooting

network installation, Visual Studio

administrator guide, Visual Studio

installing Visual Studio, administrator guide

list of domains, locations, URLs, Visual Studio

proxy errors, Visual Studio

anandmeg

meghaanand

jmartens

multiple

visual-studio-windows

vs-installation

Troubleshoot network-related errors when you install, update, or use Visual Studio

[!INCLUDE Visual Studio]

We’ve got solutions for the most typical network- or proxy-related errors. You might encounter these errors when you install, update, or use Visual Studio behind a firewall, a proxy server, or on a client machine that doesn’t have access to the internet.

Error: “Proxy authorization required”

This error generally occurs when users connect to the internet through a proxy server. The proxy server then blocks the calls that Visual Studio makes to some network resources.

To fix this proxy error

Restart Visual Studio. A proxy authentication dialog should appear. Enter your credentials when prompted in the dialog.
If restarting Visual Studio doesn’t solve the problem, it might be because your proxy server doesn’t prompt for credentials for http://go.microsoft.com addresses, but it does so for *.visualStudio.microsoft.com addresses. For these servers, add the following URLs to an allowlist to unblock all sign-in scenarios in Visual Studio:
- *.windows.net
- *.microsoftonline.com
- *.visualstudio.microsoft.com
- *.microsoft.com
- *.live.com
We recommend that you remove the http://go.microsoft.com address from the allowlist. Removing the address allows the proxy authentication dialog to show up for both the http://go.microsoft.com address and the server endpoints when Visual Studio restarts.

-OR-
If you want to use your default credentials with your proxy, you can perform the following actions:

::: moniker range=»vs-2019″

Find devenv.exe.config (the devenv.exe configuration file) in: %ProgramFiles%Microsoft Visual Studio2019EnterpriseCommon7IDE or %ProgramFiles(x86)%Microsoft Visual Studio2019EnterpriseCommon7IDE.
In the configuration file, find the <system.net> block, and then add this code:
```
<defaultProxy enabled="true" useDefaultCredentials="true">
    <proxy bypassonlocal="True" proxyaddress="http://<yourproxy:port#>"/>
</defaultProxy>
```
You must insert the correct proxy address for your network in proxyaddress="<http://<yourproxy:port#>.

[!NOTE]
For more information, see the <defaultProxy> Element (Network Settings) and <proxy> Element (Network Settings) pages.

::: moniker-end

::: moniker range=»vs-2022″

Find devenv.exe.config (the devenv.exe configuration file) in: %ProgramFiles%Microsoft Visual Studio2022EnterpriseCommon7IDE or %ProgramFiles(x86)%Microsoft Visual Studio2022EnterpriseCommon7IDE.
In the configuration file, find the <system.net> block, and then add this code:
```
<defaultProxy enabled="true" useDefaultCredentials="true">
    <proxy bypassonlocal="True" proxyaddress="http://<yourproxy:port#>"/>
</defaultProxy>
```
You must insert the correct proxy address for your network in proxyaddress="<http://<yourproxy:port#>.

[!NOTE]
For more information, see the <defaultProxy> Element (Network Settings) and <proxy> Element (Network Settings) pages.

::: moniker-end

Error: “Disconnected from Visual Studio” when attempting to report a problem

This error generally occurs when a user connects to the internet through a proxy server. The proxy server then blocks the calls that Visual Studio makes to some network resources.

To fix this proxy error

Find feedback.exe.config (the feedback.exe configuration file) in: %ProgramFiles(x86)%Microsoft Visual StudioInstaller or %ProgramFiles%Microsoft Visual StudioInstaller.
In the configuration file, check whether the following code is present; if the code isn’t present, add it before the last </configuration> line.
```
<system.net>
    <defaultProxy useDefaultCredentials="true" />
</system.net>
```

Error: “The underlying connection was closed”

If you’re using Visual Studio in a private network that has a firewall, Visual Studio might not be able to connect to some network resources. These resources can include Azure DevOps Services for sign-in and licensing, NuGet, and Azure services. If Visual Studio fails to connect to one of these resources, you might see the following error message:

The underlying connection was closed: An unexpected error occurred on send

Visual Studio uses Transport Layer Security (TLS) 1.2 protocol to connect to network resources. Security appliances on some private networks block certain server connections when Visual Studio uses TLS 1.2.

To fix this connection error

Enable connections for the following URLs:

https://management.core.windows.net
https://app.vssps.visualstudio.com
https://login.microsoftonline.com
https://login.live.com
https://go.microsoft.com
https://graph.windows.net
https://app.vsspsext.visualstudio.com
*.azurewebsites.net (for Azure connections)
*.visualstudio.microsoft.com
cdn.vsassets.io (hosts content delivery network, or CDN, content)
*.gallerycdn.vsassets.io (hosts Azure DevOps Services extensions)
static2.sharepointonline.com (hosts resources that Visual Studio uses in the Office UI Fabric kit, such as fonts)
*.nuget.org (for NuGet connections)

[!NOTE]
Privately owned NuGet server URLs may not be included in this list. You can check for the NuGet servers that you are using in %APPData%NugetNuGet.Config.

Error: «Failed to parse ID from parent process»

You might encounter this error message when you use a Visual Studio bootstrapper and a response.json file on a network drive. The error’s source is the User Account Control (UAC) in Windows.

Here’s why this error can happen: A mapped network drive or UNC share is linked to a user’s access token. When UAC is enabled, two user access tokens are created: One with administrator access, and one without administrator access. When a network drive or share is created, the user’s current access token is linked to it. Because the bootstrapper must be run as administrator, it won’t be able to access the network drive or share if either the drive or the share isn’t linked to a user-access token that has administrator access.

To fix this error

You can use the net use command or you can change the UAC Group Policy setting. For more information about these workarounds and how to implement them, see the following Microsoft support articles:

Mapped drives aren’t available from an elevated prompt when UAC is configured to «Prompt for credentials» in Windows
Programs may be unable to access some network locations after you turn on User Account Control in Windows operating systems

Error: The product fails to install or update because network share permissions aren’t configured correctly

You need to make sure that the account performing the install or update has sufficient access to the network shares.

Issue	Solution
User account can’t access files	If the user has administrator permissions on the machine and is going to be installing or updating from a layout, then you’ll need to make sure that the network share permissions (ACLs) are configured to grant users read access before the network location is shared.
System account can’t access files	Sometimes the installation or update is run using the system account instead of a user account. This typically happens when Administrator updates are used to keep the machine updated and secure. You’ll need to make sure that the client machines’ system accounts have read permissions to the network file share. You can do this by creating an Active Directory group containing the machine accounts that need access to the share, and then granting that AD group access to the share.

Issue

Solution

User account can’t access files

If the user has administrator permissions on the machine and is going to be installing or updating from a layout, then you’ll need to make sure that the network share permissions (ACLs) are configured to grant users read access before the network location is shared.

System account can’t access files

Sometimes the installation or update is run using the system account instead of a user account. This typically happens when Administrator updates are used to keep the machine updated and secure. You’ll need to make sure that the client machines’ system accounts have read permissions to the network file share. You can do this by creating an Active Directory group containing the machine accounts that need access to the share, and then granting that AD group access to the share.

[!INCLUDEinstall_get_support_md]

Troubleshoot network-related errors when you install, update, or use Visual Studio

[!INCLUDE Visual Studio]

Error: “Proxy authorization required”

This error generally occurs when users connect to the internet through a proxy server. The proxy server then blocks the calls that Visual Studio makes to some network resources.

To fix this proxy error

Restart Visual Studio. A proxy authentication dialog should appear. Enter your credentials when prompted in the dialog.
If restarting Visual Studio doesn’t solve the problem, it might be because your proxy server doesn’t prompt for credentials for http://go.microsoft.com addresses, but it does so for *.visualStudio.microsoft.com addresses. For these servers, add the following URLs to an allowlist to unblock all sign-in scenarios in Visual Studio:
- *.windows.net
- *.microsoftonline.com
- *.visualstudio.microsoft.com
- *.microsoft.com
- *.live.com
We recommend that you remove the http://go.microsoft.com address from the allowlist. Removing the address allows the proxy authentication dialog to show up for both the http://go.microsoft.com address and the server endpoints when Visual Studio restarts.

-OR-
If you want to use your default credentials with your proxy, you can perform the following actions:

::: moniker range=»vs-2019″

Find devenv.exe.config (the devenv.exe configuration file) in: %ProgramFiles%Microsoft Visual Studio2019EnterpriseCommon7IDE or %ProgramFiles(x86)%Microsoft Visual Studio2019EnterpriseCommon7IDE.
In the configuration file, find the <system.net> block, and then add this code:
```
<defaultProxy enabled="true" useDefaultCredentials="true">
    <proxy bypassonlocal="True" proxyaddress="http://<yourproxy:port#>"/>
</defaultProxy>
```
You must insert the correct proxy address for your network in proxyaddress="<http://<yourproxy:port#>.

[!NOTE]
For more information, see the <defaultProxy> Element (Network Settings) and <proxy> Element (Network Settings) pages.

::: moniker-end

::: moniker range=»vs-2022″

Find devenv.exe.config (the devenv.exe configuration file) in: %ProgramFiles%Microsoft Visual Studio2022EnterpriseCommon7IDE or %ProgramFiles(x86)%Microsoft Visual Studio2022EnterpriseCommon7IDE.
In the configuration file, find the <system.net> block, and then add this code:
```
<defaultProxy enabled="true" useDefaultCredentials="true">
    <proxy bypassonlocal="True" proxyaddress="http://<yourproxy:port#>"/>
</defaultProxy>
```
You must insert the correct proxy address for your network in proxyaddress="<http://<yourproxy:port#>.

[!NOTE]
For more information, see the <defaultProxy> Element (Network Settings) and <proxy> Element (Network Settings) pages.

::: moniker-end

Error: “Disconnected from Visual Studio” when attempting to report a problem

This error generally occurs when a user connects to the internet through a proxy server. The proxy server then blocks the calls that Visual Studio makes to some network resources.

To fix this proxy error

Find feedback.exe.config (the feedback.exe configuration file) in: %ProgramFiles(x86)%Microsoft Visual StudioInstaller or %ProgramFiles%Microsoft Visual StudioInstaller.
In the configuration file, check whether the following code is present; if the code isn’t present, add it before the last </configuration> line.
```
<system.net>
    <defaultProxy useDefaultCredentials="true" />
</system.net>
```

Error: “The underlying connection was closed”

The underlying connection was closed: An unexpected error occurred on send

To fix this connection error

Enable connections for the following URLs:

https://management.core.windows.net
https://app.vssps.visualstudio.com
https://login.microsoftonline.com
https://login.live.com
https://go.microsoft.com
https://graph.windows.net
https://app.vsspsext.visualstudio.com
*.azurewebsites.net (for Azure connections)
*.visualstudio.microsoft.com
cdn.vsassets.io (hosts content delivery network, or CDN, content)
*.gallerycdn.vsassets.io (hosts Azure DevOps Services extensions)
static2.sharepointonline.com (hosts resources that Visual Studio uses in the Office UI Fabric kit, such as fonts)
*.nuget.org (for NuGet connections)

[!NOTE]
Privately owned NuGet server URLs may not be included in this list. You can check for the NuGet servers that you are using in %APPData%NugetNuGet.Config.

Error: «Failed to parse ID from parent process»

You might encounter this error message when you use a Visual Studio bootstrapper and a response.json file on a network drive. The error’s source is the User Account Control (UAC) in Windows.

To fix this error

Mapped drives aren’t available from an elevated prompt when UAC is configured to «Prompt for credentials» in Windows
Programs may be unable to access some network locations after you turn on User Account Control in Windows operating systems

Error: The product fails to install or update because network share permissions aren’t configured correctly

You need to make sure that the account performing the install or update has sufficient access to the network shares.

Issue	Solution
User account can’t access files	If the user has administrator permissions on the machine and is going to be installing or updating from a layout, then you’ll need to make sure that the network share permissions (ACLs) are configured to grant users read access before the network location is shared.
System account can’t access files	Sometimes the installation or update is run using the system account instead of a user account. This typically happens when Administrator updates are used to keep the machine updated and secure. You’ll need to make sure that the client machines’ system accounts have read permissions to the network file share. You can do this by creating an Active Directory group containing the machine accounts that need access to the share, and then granting that AD group access to the share.

Issue

Solution

User account can’t access files

System account can’t access files

[!INCLUDEinstall_get_support_md]

5 ответов

У меня была такая же проблема, пока я не вызвал своих сетевых администраторов. Мы обнаружили, что наш IPS помечен домен как вредоносное ПО, и мы заблокировали его на уровне нашей внутренней сети.

Как только мы удалили блок, все теперь снова работает.

У нас также были проблемы с получением изображений и css с сайтов проекта codeplex, и это также исправило эту проблему.

Я вижу этот вопрос за корпоративным прокси-сервера с помощью Visual студии 2015, которая использует новые В3 API-интерфейс (https://api.nuget.org/v3/index.json). В моем экземпляре, это связано с поддержкой SSL перехват корпоративного прокси (оживленном), что не знает, как обращаться с новой шифра протокола (например, протокол TLS 1.2, плюс некоторые новые обмен ключами шифра), который обсуждается, что конечную точку API, я считаю.

быстрое исправление для пользователей Visual Studio 2015 заключается в изменении URL-адреса с https на http. У меня такое чувство, что это может не сработать, если пакет имеет файл лицензии https.

или переключитесь на Visual Studio 2013 для установки и обновления пакетов.

проверьте, работает ли подключение к интернету, и ваш прокси-сервер настроен и включен в настройках локальной сети Internet Explorer. В моем случае он пытался загрузить его из интернета и не смог, так как мой прокси был отключен! Надеюсь, это поможет…

введите команду

В Linux
Перед выполнением команды Git выполните в командной строке следующее:

export GIT_TRACE_PACKET=1;export GIT_TRACE=1;export GIT_CURL_VERBOSE=1

На Windows
Перед выполнением команды Git выполните в командной строке следующее:

set GIT_TRACE_PACKET=1 set GIT_TRACE=1 set GIT_CURL_VERBOSE=1

Источник

Здравствуйте!
Помогите понять в чем проблема.
Делаю GET запрос на сайт, используя HttpWebRequest. Запрос не проходит. Возникает WebExeption:
«Базовое соединение закрыто: Непредвиденная ошибка при передаче. System.IO.IOException: Не удается прочитать данные из транспортного соединения: Удаленный хост принудительно разорвал существующее подключение.»
При этом пару недель назад все работало.

            string briefingPath = @"https://www.briefing.com";           
            HttpWebRequest request = (HttpWebRequest)HttpWebRequest.Create(new Uri(briefingPath));
            request.UserAgent = "Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0)";
            request.ContentType = "application/x-www-form-urlencoded";
            request.Accept = "text/html, application/xhtml+xml, */*";
            request.Headers.Add(HttpRequestHeader.AcceptLanguage, "ru-RU");
            request.Headers.Add(HttpRequestHeader.AcceptEncoding, "gzip, deflate");
                  
            
 
            HttpWebResponse myHttpWebResponse = (HttpWebResponse)request.GetResponse();
            ...

Добавлено через 15 часов 59 минут
Надо было добавить в код

Добавлено через 26 секунд
Надо был добавить в код

1	ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls11;

__________________
Помощь в написании контрольных, курсовых и дипломных работ, диссертаций здесь

Источник

Базовое соединение закрыто непредвиденная ошибка при передаче visual studio

Вопрос

Ответы

Все ответы

Troubleshoot network-related errors when you install, update, or use Visual Studio

Error: “Proxy authorization required”

To fix this proxy error

Error: “Disconnected from Visual Studio” when attempting to report a problem

To fix this proxy error

Error: “The underlying connection was closed”

To fix this connection error

Error: «Failed to parse ID from parent process»

To fix this error

Error: The product fails to install or update because network share permissions aren’t configured correctly

See also

Troubleshoot network-related errors when you install, update, or use Visual Studio

Error: “Proxy authorization required”

To fix this proxy error

Error: “Disconnected from Visual Studio” when attempting to report a problem

To fix this proxy error

Error: “The underlying connection was closed”

To fix this connection error

Error: «Failed to parse ID from parent process»

To fix this error

Error: The product fails to install or update because network share permissions aren’t configured correctly

See also

5 ответов

А вот еще интересные материалы: