(500) Internal Server Error.

Getting lots of "(500) Internal Server Error." and "Unable to find version ..." nuget package during build.

  1. Just noticed the same thing when I saw my builds failing.
    Appears that NuGet.org is down, so it's not AppVeyor related.

  2. It's not only us: https://twitter.com/search?q=nuget&src=typd

    Btw, I'm just wondering - could it be related to the version of NuGet that you have in ".nuget" folder? The latest one is 2.7.

  3. I update the version to the latest. But still the same issues. I think we need to wait till they get the servers up. Thanks @Feodor

  4. I'm looking into this now.

  5. OK, I did some tests:

    • test-console on BitBucket - it's relatively simple console app and pulls NUnit package for tests. Works.
    • test-azure on GitHub - it's Azure CS with worker and web roles - pulls a lot of packages. Ran build 16 times - 7 succeeded, 9 failed with 404 for random package.

    Definitely, there is something strange. I've seen NuGet team were talking about switching DNS - maybe it's kinda round robin between new and old environments :-/

  6. I read that the Northern US azure server had issues earlier today. That combined with NuGet's dns' issues, are pretty sure the cause of this.

    I think it's best if we just wait this one out. Chances are very slim it's AppVeyor's fault.

  7. Right.

  8. Back to normal.

  9. mcpken closed this discussion on 22 Oct, 2013 11:06 AM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac