Getting lots of "(500) Internal Server Error." and "Unable to find version ..." nuget package during build.
(500) Internal Server Error.
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

#1 Posted by Steven Thuriot on 18 Oct, 2013 08:24 AM
Just noticed the same thing when I saw my builds failing.
Appears that NuGet.org is down, so it's not AppVeyor related.
#2 Posted by Feodor Fitsner Support staff on 18 Oct, 2013 02:16 PM
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 Posted by Dan on 18 Oct, 2013 03:11 PM
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 Posted by Feodor Fitsner Support staff on 18 Oct, 2013 04:13 PM
I'm looking into this now.
#5 Posted by Feodor Fitsner Support staff on 18 Oct, 2013 04:41 PM
OK, I did some tests:
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 Posted by Steven Thuriot on 18 Oct, 2013 05:21 PM
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 Posted by Feodor Fitsner Support staff on 18 Oct, 2013 05:24 PM
Right.
#8 Posted by mcpken on 22 Oct, 2013 11:06 AM
Back to normal.
mcpken closed this discussion on 22 Oct, 2013 11:06 AM.