Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
Nuget connector fails to download Nuget.Frameworks.5.0.0
-
I'm running Proget 5.2.18 and I have a connector to https://www.nuget.org/api/v2 in a Nuget feed.
In a docker container I rundotnet test
. Everything works correctly, but if I run the container for the second time I will receive the following message:The feed 'cache [http://localproget/nuget/cache]' lists package 'NuGet.Frameworks.5.0.0' but multiple attempts to download the nupkg have failed.
Interesting point is that if I run the container for the 3rd time, everything just works find while at the 4th time, I receive the same message again!
-
Hello; unfortunately it's impossible to say based on the information you've provided.
ProGet may have logged some errors (Admin > Diagnostic Center), or you may find errors logged by NuGet somewhere. If you can share those hopefully we can help then
-
I captured these logs from IIS:
-
GET /nuget/taraabar/FindPackagesById() id='NuGet.Frameworks'&semVerLevel=2.0.0&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=e3701d3f-85df-4a96-94a2-f80c43e61240&SERVER-STATUS=200 (this returns 200)
-
GET /nuget/taraabar/package/NuGet.Frameworks/5.0.0+42a8779499c1d1ed2488c2e6b9e2ee6ff6107766 (this returns 404)
-
GET /nuget/taraabar/FindPackagesById() id='NuGet.Frameworks'&semVerLevel=2.0.0&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=dcdb5ed1-bd22-4081-bf24-844766eb0c3d&SERVER-STATUS=200 (this returns 200)
-
-
I can't reproduce this in the latest version of ProGet; however this didn't work in older versions (not sure exactly when fixed).
If you visit
/nuget/taraabar/package/NuGet.Frameworks/5.0.0+42a8779499c1d1ed2488c2e6b9e2ee6ff6107766
in your browser does it work?
-
No it doesn't. I receive 404.
-
Unfortunately, since I can't reproduce this at all, and no other users have reported the problem, you'll need to do a bit more digging on your end.
You can attach ProGet to Fiddler by using the Proxy setting on your PRoGet server, then you can watch the traffic and identfiy exactly what's not working.