Nuget connection attempt failed “Unable to load the service index for source”
While trying to connect to Nuget, 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 to https://api.nuget.org/v3/index.json
on my browser.
It is not a duplicate. The other answers doesn't solve my problem.
c# .net visual-studio nuget
add a comment |
While trying to connect to Nuget, 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 to https://api.nuget.org/v3/index.json
on my browser.
It is not a duplicate. The other answers doesn't solve my problem.
c# .net visual-studio nuget
Possible duplicate of VS2015 nuget package manager not finding packages
– DaImTo
Dec 16 '16 at 13:29
Since you have post the same issue on another thread (stackoverflow.com/questions/41157069/nuget-not-connecting), please continue this issue on your previous thread. And I also will follow this issue on your previous thread.
– Weiwei Cai - MSFT
Dec 19 '16 at 1:42
Do you have proxy configured on your machine? Or "http_proxy" variable configured in environment variable?
– Eddie Chen - MSFT
Dec 20 '16 at 2:54
Yes I have multiple proxies running on my machine. When I installed fiddler. I was able to access to nuget. I have corp proxy.
– DarthVader
Dec 20 '16 at 10:30
@DarthVader, if Eddie's reply help you resolve this issue, would you please mark it as the answer? Have a nice day:)
– Jack Zhai-MSFT
Dec 30 '16 at 3:49
add a comment |
While trying to connect to Nuget, 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 to https://api.nuget.org/v3/index.json
on my browser.
It is not a duplicate. The other answers doesn't solve my problem.
c# .net visual-studio nuget
While trying to connect to Nuget, 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 to https://api.nuget.org/v3/index.json
on my browser.
It is not a duplicate. The other answers doesn't solve my problem.
c# .net visual-studio nuget
c# .net visual-studio nuget
edited May 23 '18 at 16:53
Marcelo Machado
586520
586520
asked Dec 16 '16 at 13:24
DarthVaderDarthVader
22.8k58163264
22.8k58163264
Possible duplicate of VS2015 nuget package manager not finding packages
– DaImTo
Dec 16 '16 at 13:29
Since you have post the same issue on another thread (stackoverflow.com/questions/41157069/nuget-not-connecting), please continue this issue on your previous thread. And I also will follow this issue on your previous thread.
– Weiwei Cai - MSFT
Dec 19 '16 at 1:42
Do you have proxy configured on your machine? Or "http_proxy" variable configured in environment variable?
– Eddie Chen - MSFT
Dec 20 '16 at 2:54
Yes I have multiple proxies running on my machine. When I installed fiddler. I was able to access to nuget. I have corp proxy.
– DarthVader
Dec 20 '16 at 10:30
@DarthVader, if Eddie's reply help you resolve this issue, would you please mark it as the answer? Have a nice day:)
– Jack Zhai-MSFT
Dec 30 '16 at 3:49
add a comment |
Possible duplicate of VS2015 nuget package manager not finding packages
– DaImTo
Dec 16 '16 at 13:29
Since you have post the same issue on another thread (stackoverflow.com/questions/41157069/nuget-not-connecting), please continue this issue on your previous thread. And I also will follow this issue on your previous thread.
– Weiwei Cai - MSFT
Dec 19 '16 at 1:42
Do you have proxy configured on your machine? Or "http_proxy" variable configured in environment variable?
– Eddie Chen - MSFT
Dec 20 '16 at 2:54
Yes I have multiple proxies running on my machine. When I installed fiddler. I was able to access to nuget. I have corp proxy.
– DarthVader
Dec 20 '16 at 10:30
@DarthVader, if Eddie's reply help you resolve this issue, would you please mark it as the answer? Have a nice day:)
– Jack Zhai-MSFT
Dec 30 '16 at 3:49
Possible duplicate of VS2015 nuget package manager not finding packages
– DaImTo
Dec 16 '16 at 13:29
Possible duplicate of VS2015 nuget package manager not finding packages
– DaImTo
Dec 16 '16 at 13:29
Since you have post the same issue on another thread (stackoverflow.com/questions/41157069/nuget-not-connecting), please continue this issue on your previous thread. And I also will follow this issue on your previous thread.
– Weiwei Cai - MSFT
Dec 19 '16 at 1:42
Since you have post the same issue on another thread (stackoverflow.com/questions/41157069/nuget-not-connecting), please continue this issue on your previous thread. And I also will follow this issue on your previous thread.
– Weiwei Cai - MSFT
Dec 19 '16 at 1:42
Do you have proxy configured on your machine? Or "http_proxy" variable configured in environment variable?
– Eddie Chen - MSFT
Dec 20 '16 at 2:54
Do you have proxy configured on your machine? Or "http_proxy" variable configured in environment variable?
– Eddie Chen - MSFT
Dec 20 '16 at 2:54
Yes I have multiple proxies running on my machine. When I installed fiddler. I was able to access to nuget. I have corp proxy.
– DarthVader
Dec 20 '16 at 10:30
Yes I have multiple proxies running on my machine. When I installed fiddler. I was able to access to nuget. I have corp proxy.
– DarthVader
Dec 20 '16 at 10:30
@DarthVader, if Eddie's reply help you resolve this issue, would you please mark it as the answer? Have a nice day:)
– Jack Zhai-MSFT
Dec 30 '16 at 3:49
@DarthVader, if Eddie's reply help you resolve this issue, would you please mark it as the answer? Have a nice day:)
– Jack Zhai-MSFT
Dec 30 '16 at 3:49
add a comment |
11 Answers
11
active
oldest
votes
You need to add proxy settings into Nuget.Config file. Refer to this link for details: Nuget Config Section & Nuget Proxy Settings.
For me it was that I had a http_proxy environment variable set up that was wrong.
– Martin Brown
Mar 13 '17 at 13:34
1
I had that problem too, and removed it in the command line, but now the problem is back but I have no proxy set currently. Any idea what could still be going wrong?
– Dan Csharpster
Aug 8 '17 at 14:28
1
stuck with the same issue
– Rıfat Erdem Sahin
Jul 16 '18 at 16:01
add a comment |
Go to
Settings ( Global Settings of your PC ) > Network and Internet > Proxy > Automatic Proxy Setup > and set Automatically detect settings to off.
add a comment |
The error can be caused by just temporary network issue, and disappear, if try again.
add a comment |
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" />
add a comment |
Something may have change your proxy setting, like Fiddler. Close Fiddler, then close Visual Studio and open it again.
add a comment |
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 servicesDocker Engine
andDocker for Windows Service
are running.
At last, you must check your Nuget.config file from
C:UsersSibeeshAppDataRoamingNuGet
. For me, the content of that file was as below.
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<packageSources>
<add key="nuget.org" value="https://api.nuget.org/v3/index.json" />
</packageSources>
<packageRestore>
<add key="enabled" value="True" />
<add key="automatic" value="True" />
</packageRestore>
<bindingRedirects>
<add key="skip" value="False" />
</bindingRedirects>
<packageManagement>
<add key="format" value="0" />
<add key="disabled" value="False" />
</packageManagement>
</configuration>
Hope this helps.
add a comment |
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
add a comment |
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:WindowsSystem32configsystemprofileAppDataRoamingNuGetNuGet.Config
file which looks like the following:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<config>
<add key="http_proxy" value="http://proxy_hostname_or_ip:3128" />
<add key="https_proxy" value="http://proxy_hostname_or_ip:3128" />
</config>
<packageSources>
<add key="nuget.org" value="https://api.nuget.org/v3/index.json" protocolVersion="3" />
</packageSources>
</configuration>
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_nugetnuget.exe restore "path_to_solutiontheSolution.sln"
add a comment |
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.
add a comment |
Go to -> Tools -> Extensions and Updates and uninstall NuGet package manager.. restart visual studio and reinstall it.... every thing will set to normal
add a comment |
In my case i had had Fiddler running which had changed my proxy settings
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f41185443%2fnuget-connection-attempt-failed-unable-to-load-the-service-index-for-source%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
11 Answers
11
active
oldest
votes
11 Answers
11
active
oldest
votes
active
oldest
votes
active
oldest
votes
You need to add proxy settings into Nuget.Config file. Refer to this link for details: Nuget Config Section & Nuget Proxy Settings.
For me it was that I had a http_proxy environment variable set up that was wrong.
– Martin Brown
Mar 13 '17 at 13:34
1
I had that problem too, and removed it in the command line, but now the problem is back but I have no proxy set currently. Any idea what could still be going wrong?
– Dan Csharpster
Aug 8 '17 at 14:28
1
stuck with the same issue
– Rıfat Erdem Sahin
Jul 16 '18 at 16:01
add a comment |
You need to add proxy settings into Nuget.Config file. Refer to this link for details: Nuget Config Section & Nuget Proxy Settings.
For me it was that I had a http_proxy environment variable set up that was wrong.
– Martin Brown
Mar 13 '17 at 13:34
1
I had that problem too, and removed it in the command line, but now the problem is back but I have no proxy set currently. Any idea what could still be going wrong?
– Dan Csharpster
Aug 8 '17 at 14:28
1
stuck with the same issue
– Rıfat Erdem Sahin
Jul 16 '18 at 16:01
add a comment |
You need to add proxy settings into Nuget.Config file. Refer to this link for details: Nuget Config Section & Nuget Proxy Settings.
You need to add proxy settings into Nuget.Config file. Refer to this link for details: Nuget Config Section & Nuget Proxy Settings.
answered Dec 21 '16 at 8:43
Eddie Chen - MSFTEddie Chen - MSFT
24.5k22346
24.5k22346
For me it was that I had a http_proxy environment variable set up that was wrong.
– Martin Brown
Mar 13 '17 at 13:34
1
I had that problem too, and removed it in the command line, but now the problem is back but I have no proxy set currently. Any idea what could still be going wrong?
– Dan Csharpster
Aug 8 '17 at 14:28
1
stuck with the same issue
– Rıfat Erdem Sahin
Jul 16 '18 at 16:01
add a comment |
For me it was that I had a http_proxy environment variable set up that was wrong.
– Martin Brown
Mar 13 '17 at 13:34
1
I had that problem too, and removed it in the command line, but now the problem is back but I have no proxy set currently. Any idea what could still be going wrong?
– Dan Csharpster
Aug 8 '17 at 14:28
1
stuck with the same issue
– Rıfat Erdem Sahin
Jul 16 '18 at 16:01
For me it was that I had a http_proxy environment variable set up that was wrong.
– Martin Brown
Mar 13 '17 at 13:34
For me it was that I had a http_proxy environment variable set up that was wrong.
– Martin Brown
Mar 13 '17 at 13:34
1
1
I had that problem too, and removed it in the command line, but now the problem is back but I have no proxy set currently. Any idea what could still be going wrong?
– Dan Csharpster
Aug 8 '17 at 14:28
I had that problem too, and removed it in the command line, but now the problem is back but I have no proxy set currently. Any idea what could still be going wrong?
– Dan Csharpster
Aug 8 '17 at 14:28
1
1
stuck with the same issue
– Rıfat Erdem Sahin
Jul 16 '18 at 16:01
stuck with the same issue
– Rıfat Erdem Sahin
Jul 16 '18 at 16:01
add a comment |
Go to
Settings ( Global Settings of your PC ) > Network and Internet > Proxy > Automatic Proxy Setup > and set Automatically detect settings to off.
add a comment |
Go to
Settings ( Global Settings of your PC ) > Network and Internet > Proxy > Automatic Proxy Setup > and set Automatically detect settings to off.
add a comment |
Go to
Settings ( Global Settings of your PC ) > Network and Internet > Proxy > Automatic Proxy Setup > and set Automatically detect settings to off.
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 '17 at 6:43
VISHAL TANKVISHAL TANK
4218
4218
add a comment |
add a comment |
The error can be caused by just temporary network issue, and disappear, if try again.
add a comment |
The error can be caused by just temporary network issue, and disappear, if try again.
add a comment |
The error can be caused by just temporary network issue, and disappear, if try again.
The error can be caused by just temporary network issue, and disappear, if try again.
answered Nov 16 '17 at 1:55
Michael FreidgeimMichael Freidgeim
13k688111
13k688111
add a comment |
add a comment |
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" />
add a comment |
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" />
add a comment |
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" />
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 '17 at 2:43
jitin14jitin14
664
664
add a comment |
add a comment |
Something may have change your proxy setting, like Fiddler. Close Fiddler, then close Visual Studio and open it again.
add a comment |
Something may have change your proxy setting, like Fiddler. Close Fiddler, then close Visual Studio and open it again.
add a comment |
Something may have change your proxy setting, like Fiddler. Close Fiddler, then close Visual Studio and open it again.
Something may have change your proxy setting, like Fiddler. Close Fiddler, then close Visual Studio and open it again.
answered Jun 1 '18 at 22:36
Sylvain RodrigueSylvain Rodrigue
3,21543753
3,21543753
add a comment |
add a comment |
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 servicesDocker Engine
andDocker for Windows Service
are running.
At last, you must check your Nuget.config file from
C:UsersSibeeshAppDataRoamingNuGet
. For me, the content of that file was as below.
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<packageSources>
<add key="nuget.org" value="https://api.nuget.org/v3/index.json" />
</packageSources>
<packageRestore>
<add key="enabled" value="True" />
<add key="automatic" value="True" />
</packageRestore>
<bindingRedirects>
<add key="skip" value="False" />
</bindingRedirects>
<packageManagement>
<add key="format" value="0" />
<add key="disabled" value="False" />
</packageManagement>
</configuration>
Hope this helps.
add a comment |
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 servicesDocker Engine
andDocker for Windows Service
are running.
At last, you must check your Nuget.config file from
C:UsersSibeeshAppDataRoamingNuGet
. For me, the content of that file was as below.
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<packageSources>
<add key="nuget.org" value="https://api.nuget.org/v3/index.json" />
</packageSources>
<packageRestore>
<add key="enabled" value="True" />
<add key="automatic" value="True" />
</packageRestore>
<bindingRedirects>
<add key="skip" value="False" />
</bindingRedirects>
<packageManagement>
<add key="format" value="0" />
<add key="disabled" value="False" />
</packageManagement>
</configuration>
Hope this helps.
add a comment |
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 servicesDocker Engine
andDocker for Windows Service
are running.
At last, you must check your Nuget.config file from
C:UsersSibeeshAppDataRoamingNuGet
. For me, the content of that file was as below.
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<packageSources>
<add key="nuget.org" value="https://api.nuget.org/v3/index.json" />
</packageSources>
<packageRestore>
<add key="enabled" value="True" />
<add key="automatic" value="True" />
</packageRestore>
<bindingRedirects>
<add key="skip" value="False" />
</bindingRedirects>
<packageManagement>
<add key="format" value="0" />
<add key="disabled" value="False" />
</packageManagement>
</configuration>
Hope this helps.
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 servicesDocker Engine
andDocker for Windows Service
are running.
At last, you must check your Nuget.config file from
C:UsersSibeeshAppDataRoamingNuGet
. For me, the content of that file was as below.
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<packageSources>
<add key="nuget.org" value="https://api.nuget.org/v3/index.json" />
</packageSources>
<packageRestore>
<add key="enabled" value="True" />
<add key="automatic" value="True" />
</packageRestore>
<bindingRedirects>
<add key="skip" value="False" />
</bindingRedirects>
<packageManagement>
<add key="format" value="0" />
<add key="disabled" value="False" />
</packageManagement>
</configuration>
Hope this helps.
edited Jul 23 '18 at 7:16
answered Jul 21 '18 at 13:21
Sibeesh VenuSibeesh Venu
5,30432549
5,30432549
add a comment |
add a comment |
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
add a comment |
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
add a comment |
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
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
edited Oct 9 '18 at 5:56
Nadeem_MK
6,06073349
6,06073349
answered Oct 3 '18 at 10:47
Shradha ShilvantShradha Shilvant
111
111
add a comment |
add a comment |
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:WindowsSystem32configsystemprofileAppDataRoamingNuGetNuGet.Config
file which looks like the following:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<config>
<add key="http_proxy" value="http://proxy_hostname_or_ip:3128" />
<add key="https_proxy" value="http://proxy_hostname_or_ip:3128" />
</config>
<packageSources>
<add key="nuget.org" value="https://api.nuget.org/v3/index.json" protocolVersion="3" />
</packageSources>
</configuration>
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_nugetnuget.exe restore "path_to_solutiontheSolution.sln"
add a comment |
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:WindowsSystem32configsystemprofileAppDataRoamingNuGetNuGet.Config
file which looks like the following:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<config>
<add key="http_proxy" value="http://proxy_hostname_or_ip:3128" />
<add key="https_proxy" value="http://proxy_hostname_or_ip:3128" />
</config>
<packageSources>
<add key="nuget.org" value="https://api.nuget.org/v3/index.json" protocolVersion="3" />
</packageSources>
</configuration>
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_nugetnuget.exe restore "path_to_solutiontheSolution.sln"
add a comment |
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:WindowsSystem32configsystemprofileAppDataRoamingNuGetNuGet.Config
file which looks like the following:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<config>
<add key="http_proxy" value="http://proxy_hostname_or_ip:3128" />
<add key="https_proxy" value="http://proxy_hostname_or_ip:3128" />
</config>
<packageSources>
<add key="nuget.org" value="https://api.nuget.org/v3/index.json" protocolVersion="3" />
</packageSources>
</configuration>
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_nugetnuget.exe restore "path_to_solutiontheSolution.sln"
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:WindowsSystem32configsystemprofileAppDataRoamingNuGetNuGet.Config
file which looks like the following:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<config>
<add key="http_proxy" value="http://proxy_hostname_or_ip:3128" />
<add key="https_proxy" value="http://proxy_hostname_or_ip:3128" />
</config>
<packageSources>
<add key="nuget.org" value="https://api.nuget.org/v3/index.json" protocolVersion="3" />
</packageSources>
</configuration>
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_nugetnuget.exe restore "path_to_solutiontheSolution.sln"
edited Jan 1 at 16:48
answered Dec 31 '18 at 12:23
AlexeiAlexei
11k116067
11k116067
add a comment |
add a comment |
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.
add a comment |
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.
add a comment |
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.
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.
edited Sep 20 '17 at 1:47
Phani Kumar M
3,8191723
3,8191723
answered Sep 20 '17 at 0:47
Charles MosesCharles Moses
1
1
add a comment |
add a comment |
Go to -> Tools -> Extensions and Updates and uninstall NuGet package manager.. restart visual studio and reinstall it.... every thing will set to normal
add a comment |
Go to -> Tools -> Extensions and Updates and uninstall NuGet package manager.. restart visual studio and reinstall it.... every thing will set to normal
add a comment |
Go to -> Tools -> Extensions and Updates and uninstall NuGet package manager.. restart visual studio and reinstall it.... every thing will set to normal
Go to -> Tools -> Extensions and Updates and uninstall NuGet package manager.. restart visual studio and reinstall it.... every thing will set to normal
answered Jan 1 at 12:19
Kadeer MughalKadeer Mughal
569
569
add a comment |
add a comment |
In my case i had had Fiddler running which had changed my proxy settings
add a comment |
In my case i had had Fiddler running which had changed my proxy settings
add a comment |
In my case i had had Fiddler running which had changed my proxy settings
In my case i had had Fiddler running which had changed my proxy settings
answered Feb 4 at 13:06
DooieDooie
73572142
73572142
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f41185443%2fnuget-connection-attempt-failed-unable-to-load-the-service-index-for-source%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Possible duplicate of VS2015 nuget package manager not finding packages
– DaImTo
Dec 16 '16 at 13:29
Since you have post the same issue on another thread (stackoverflow.com/questions/41157069/nuget-not-connecting), please continue this issue on your previous thread. And I also will follow this issue on your previous thread.
– Weiwei Cai - MSFT
Dec 19 '16 at 1:42
Do you have proxy configured on your machine? Or "http_proxy" variable configured in environment variable?
– Eddie Chen - MSFT
Dec 20 '16 at 2:54
Yes I have multiple proxies running on my machine. When I installed fiddler. I was able to access to nuget. I have corp proxy.
– DarthVader
Dec 20 '16 at 10:30
@DarthVader, if Eddie's reply help you resolve this issue, would you please mark it as the answer? Have a nice day:)
– Jack Zhai-MSFT
Dec 30 '16 at 3:49