New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nuget API v2 & v3 Fails To Pull Packages with 503 Error #7333

Closed
sahgilbert opened this Issue Sep 27, 2018 · 9 comments

Comments

Projects
None yet
7 participants
@sahgilbert

sahgilbert commented Sep 27, 2018

Details about Problem

Deploying an Asp.Net MVC solution, via AppVeyor, using Paket and Nuget API v2.

NuGet product used (NuGet.exe | VS UI | Package Manager Console | dotnet.exe):
AppVeyor & Paket 5.181.1 & .Net 4.7.1

NuGet version (x.x.x.xxx):
https://www.nuget.org/api/v2

Worked before? If so, with which NuGet version:
Always, without issue, same as current setup.

Detailed repro steps so we can see the same problem

Create an Asp.Net Mvc project.
Add "recaptcha-aspnet" library.
Run Paket install.
Deploy via appveyor.io
Observe failure to pull packages in.

Other points to note

It fails for almost all packages, and fails using nuget/api/v3 also.

Appveyor Screenshots

screenshot 2018-09-27 13 29 23

screenshot 2018-09-27 13 31 19 copy

Additional (Partial) Log When Running Paket Install Locally...

20180927_NugetApiV2_503.txt

20180927_NugetApiV3_503.txt

Opening Line From V2 Paket Install

Trial1 (NuGet.GetVersions) did not yield any results, trying again.

@FeodorFitsner

This comment has been minimized.

Show comment
Hide comment
@FeodorFitsner

FeodorFitsner Sep 27, 2018

I've been able to "catch" 503 on my local machine by constantly refreshing in the browser the following URL: https://www.nuget.org/api/v2/Packages(Id='microsoft.aspnet.razor',Version='3.2.6')

image

FeodorFitsner commented Sep 27, 2018

I've been able to "catch" 503 on my local machine by constantly refreshing in the browser the following URL: https://www.nuget.org/api/v2/Packages(Id='microsoft.aspnet.razor',Version='3.2.6')

image

@FeodorFitsner

This comment has been minimized.

Show comment
Hide comment
@FeodorFitsner

FeodorFitsner Sep 27, 2018

cc @skofman1, @loic-sharma - guys, could you please take a look? Thank you!

FeodorFitsner commented Sep 27, 2018

cc @skofman1, @loic-sharma - guys, could you please take a look? Thank you!

@ipjohnson

This comment has been minimized.

Show comment
Hide comment
@ipjohnson

ipjohnson commented Sep 27, 2018

+1

@skofman1

This comment has been minimized.

Show comment
Hide comment
@skofman1

skofman1 Sep 27, 2018

nuget.org availability is degraded. We are investigating. To unblock you from restoring packages please use our V3 protocol and use feed https://api.nuget.org/v3/index.json
We will keep updating https://status.nuget.org with new information.

skofman1 commented Sep 27, 2018

nuget.org availability is degraded. We are investigating. To unblock you from restoring packages please use our V3 protocol and use feed https://api.nuget.org/v3/index.json
We will keep updating https://status.nuget.org with new information.

@JVimes

This comment has been minimized.

Show comment
Hide comment
@JVimes

JVimes Sep 27, 2018

@skofman1 Is there a way to use the v3 server for nuget update -self? It's in my CI build script. Doesn't seem to use the -Source parameter.

PS> .\nuget.exe update -self -Source https://www.nuget.org/api/v3/
Checking for updates from https://www.nuget.org/api/v2/.
The remote server returned an error: (503) Server Unavailable.

JVimes commented Sep 27, 2018

@skofman1 Is there a way to use the v3 server for nuget update -self? It's in my CI build script. Doesn't seem to use the -Source parameter.

PS> .\nuget.exe update -self -Source https://www.nuget.org/api/v3/
Checking for updates from https://www.nuget.org/api/v2/.
The remote server returned an error: (503) Server Unavailable.
@joelverhagen

This comment has been minimized.

Show comment
Hide comment
@joelverhagen

joelverhagen Sep 27, 2018

Member

@JVimes, unfortunately, nuget.exe update -self is hard-coded to use the V2 source URL (https://www.nuget.org/api/v2). This short-coming is tracked here: #4197.

As a work-around, you could download nuget.exe from our download site using something like Invoke-WebRequest ... -Path nuget.exe. The "latest" URL is here:
https://dist.nuget.org/win-x86-commandline/latest/nuget.exe

The version there is currently nuget.exe 4.7.1. You can find specific versions here:
https://www.nuget.org/downloads

Member

joelverhagen commented Sep 27, 2018

@JVimes, unfortunately, nuget.exe update -self is hard-coded to use the V2 source URL (https://www.nuget.org/api/v2). This short-coming is tracked here: #4197.

As a work-around, you could download nuget.exe from our download site using something like Invoke-WebRequest ... -Path nuget.exe. The "latest" URL is here:
https://dist.nuget.org/win-x86-commandline/latest/nuget.exe

The version there is currently nuget.exe 4.7.1. You can find specific versions here:
https://www.nuget.org/downloads

@IlyaFinkelshteyn

This comment has been minimized.

Show comment
Hide comment
@IlyaFinkelshteyn

IlyaFinkelshteyn Sep 27, 2018

@skofman1 https://status.nuget.org/ seems green and states that it is no longer degraded. And I cannot repro this anymore. Though this issue is still open. Can we consider this resolved and update AppVeyor status?

IlyaFinkelshteyn commented Sep 27, 2018

@skofman1 https://status.nuget.org/ seems green and states that it is no longer degraded. And I cannot repro this anymore. Though this issue is still open. Can we consider this resolved and update AppVeyor status?

@skofman1

This comment has been minimized.

Show comment
Hide comment
@skofman1

skofman1 Sep 27, 2018

@IlyaFinkelshteyn , the problem is mitigated. Closing this issue.

skofman1 commented Sep 27, 2018

@IlyaFinkelshteyn , the problem is mitigated. Closing this issue.

@skofman1 skofman1 closed this Sep 27, 2018

@sahgilbert

This comment has been minimized.

Show comment
Hide comment
@sahgilbert

sahgilbert Sep 28, 2018

Fantastic! Big thanks to everyone involved!

sahgilbert commented Sep 28, 2018

Fantastic! Big thanks to everyone involved!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment