Nuget The Remote Server Returned An Error 502 Bad Gateway
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site nuget unable to connect to the remote server About Us Learn more about Stack Overflow the company Business Learn more about
Nuget Bad Gateway 502
hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss
The Remote Server Returned An Error (502) Bad Gateway. C#
Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Which port is
Nuget Set Proxy
used by NuGet while downloading package through Visual Studio up vote 3 down vote favorite I am using VS 2010 (Package Manager Console) to download NuGet (2.5.40416.9020/Latest) packages. It uses URL https://nuget.org/api/v2/. It gives me error as below. Install-Package : An error occurred while loading packages from'https://nuget.org/api/v2/': The remote name could not be resolved: 'nuget.org' At line:1 char:16 + Install-Package <<<< Rx-Main + CategoryInfo : the remote name could not be resolved api nuget org NotSpecified: (:) [Install-Package], InvalidOperationException + FullyQualifiedErrorId : NuGetCmdletUnhandledException,NuGet.PowerShell.Commands.InstallPackageCommand But when i access the same URL via browser then i am able to browse the site. I am on corporate network so firewall might block the port (Other than 80 and 443). So which port is used by NuGet while downloading packages via Package Manager Console (VS 2010)? visual-studio-2010 nuget nuget-package share|improve this question asked Jun 6 '13 at 8:08 vijay 933612 add a comment| 3 Answers 3 active oldest votes up vote 2 down vote accepted https://nuget.org/api/v2/ means port 443 (the standard port for HTTPS) If you're on a corporate network, port 80 and 443 are usually bounced through a proxy server. Most likely, NuGet is not using your proxy settings for some reason, so it cannot find the proxy server and are stopped by the corporate firewall. share|improve this answer answered Jun 6 '13 at 8:10 Joachim Isaksson 116k11135171 But 443 is not blocked on firewall and i am able to browse the nuget.org site, but it gives me error when i run command through Package Manager Console. –vijay Jun 6 '13 at 8:12 @vijay I'm fairly sur
on September 10th, we deployed a fix to address those issues. Errors Experienced Depending on how you were publishing your package, you would have experienced the errors in a few different ways. Upload Package page on nuget.org If you were uploading your the remote server returned an error 504 gateway timeout package through the nuget.org website’s Upload Package page, the package would have initially uploaded nuget package restore failed okay, but you would have gotten an error when submitting the verified package details. The error would have been our standard “Error: nuget server Oh no, we broke something!” response page. Push with nuget.exe If you were using nuget.exe push to upload your package to the gallery, you would have gotten a different, and misleading error. That error was http://stackoverflow.com/questions/16956852/which-port-is-used-by-nuget-while-downloading-package-through-visual-studio coming back as “The remote server returned an error: (502) Bad Gateway.” Publish through NuGet Package Explorer NuGet Package Explorer has the ability to publish packages directly. Attempting to publish packages with portable dependencies would lead to a vague error about a “bad request.” Broken Scenarios It took us a few days to really get to the root cause of this issue, because we were observing a couple of different behaviors. When http://blog.nuget.org/20130910/portable-package-issues.html we finally had it figured out, here’s what it turned out to be. Scenario 1: Packages with portable libraries In the scenario of a package containing portable libraries, there were a few details necessary to hit the error. The \lib folder of the package contained a subfolder for a portable library profile. Example: \lib\portable-net4+sl4+wp71+win8 The nupkg file was created using nuget.exe pack. The nupkg file was being uploaded either through the Upload Package page on the gallery, or from nuget.exe push. If the nupkg file was created with NuGet Package Explorer, or just opened and saved in it, then the package could be uploaded successfully. If the nupkg file was published to the gallery directly from NuGet Package Explorer, that would also succeed. What we learned from this scenario was that even though NuGet Package Explorer uses the same endpoint as nuget.exe push, packages created within it were immune to the error. Scenario 2: Packages with portable dependencies Some package authors were bypassing scenario 1 by using NuGet Package Explorer to create their package, but they were still getting the errors. In this scenario, we found the packages had dependencies that only applied for portable libraries. For instance, a dependency on Microsoft.Bcl.Async which only applies for portable library projects. NuGet Package Explorer would sav
Sign in Pricing Blog Support Search GitHub This repository Watch 117 Star 793 Fork 454 NuGet/NuGetGallery Code Issues 230 Pull requests 9 Projects 0 Wiki Pulse Graphs https://github.com/NuGet/NuGetGallery/issues/1556 New issue Package verification fails #1556 Closed objorke opened this Issue Sep 6, 2013 · 4 comments Projects None yet Labels None yet Milestone 9/20 QA (10/9 pro... http://pcsupport.about.com/od/findbyerrormessage/a/502error.htm Assignees johnataylor 3 participants objorke commented Sep 6, 2013 I keep getting "Sorry, an error occurred while processing your request." when submitting a package on the "Verify details & Submit" the remote page. This is a new version of the package. Title, summary, copyright and release notes are empty, but I get the same error if I fill these fields. I have also tried uploading the package with the nuget.exe console application (running on a virtual machine): Failed to process request. 'Bad Gateway'. The remote server returned an error: (502) Bad Gateway.. The package was the remote server uploaded successfully last time August 28, nothing was changed related to the nuget package after that. https://www.nuget.org/packages/OxyPlot.Core/ Other packages for the same library are uploaded successfully: https://www.nuget.org/packages/OxyPlot.Wpf/ NuGet member anurse commented Sep 6, 2013 There is a known issue relating to this that we're working on. Sorry for the inconvenience, we'll keep you posted on this issue thread. NuGet member anurse commented Sep 6, 2013 Could you either post a copy of your NuPkg somewhere and send a link or email me a copy at [my GitHub username]@microsoft.com ? That would help us to verify the fix we're working on. johnataylor referenced this issue Sep 10, 2013 Merged Portable libs #1564 NuGet member anurse commented Sep 10, 2013 We should have a fix going to our staging service soon. I would expect a fix to reach production in the next couple of days. johnataylor was assigned Sep 10, 2013 anurse referenced this issue Sep 10, 2013 Closed Exception thrown for GetUpdates() for packages that has portable library as target framework #1555 NuGet member anurse commented Sep 24, 2013 This should be fixed now. anurse closed this
Macs iPad iPhone Internet & Network Digital Cameras Home Theater Getting More Help Buy Buying Guides Product Reviews Software & Apps Do More Web & Search Social Media Gaming New & Next Fix Internet & Network Understanding and Fixing 502 Bad Gateway Errors Tactics to Fix a 502 Bad Gateway Error Share Pin Email 502 Bad Gateway Error. © THORDOG Internet & Network Error Messages Basics by Tim Fisher Updated October 02, 2016 The 502 Bad Gateway error is an HTTP status code that means that one server received an invalid response from another server.The Bad Gateway error can be customized by each website. While fairly uncommon, different web servers do describe this error differently. Here are some common ways you might see it.How the 502 Error Appears"502 Bad Gateway""502 Service Temporarily Overloaded""Error 502""Temporary Error (502)" "502 Proxy Error""502 Server Error: The server encountered a temporary error and could not complete your request""HTTP 502""502. That's an error""Bad Gateway: The proxy server received an invalid response from an upstream server""HTTP Error 502 - Bad Gateway"The 502 Bad Gateway error displays inside the Internet browser window, just as web pages do.Twitter's famous "fail whale" error that says Twitter is over capacity is actually a 502 Bad Gateway error (even though a 503 Error would make more sense).A Bad Gateway error received in Windows Update generates a 0x80244021 error code or the message WU_E_PT_HTTP_STATUS_BAD_GATEWAY.When Google services, like Google Search or Gmail, are experiencing a 502 Bad Gateway, they often show Server Error, or sometimes just 502, on the screen.502 Bad Gateway errors are completely independent of your particular setup, meaning that you could see one in any browser, on any operating system, and on any device. Cause of 502 Bad Gateway ErrorsOften, Bad Gateway error