Badrequest error when pushing nuget package to a linux install

I have a clean new install of proget on a Linux vm in a Hyper-V 2012 system. I can access the proget web page and have set up a nugget feed with a end point of http://servername/nugget/feedname. When I try and push with "nugget.exe push test.1.0.0.nupkg -Source http://servername/nugget/feedname -ApiKey username:password" I get the following response:

Pushing test.1.0.0.nupkg to 'http://servername/nugget/feedname'...
PUT http://servername/nugget/feedname/
BadRequest http://servername/nugget/feedname/ 162ms
Response status code does not indicate success: 400 (Bad Request).

any help would be appreciated.
thanks in advance
Bob

Product: ProGet
Version: 5.0.0

ben

Hello Bob,

You seem to have a typo in the feed URL. http://servername/nugget/feedname should be http://servername/nuget/feedname (with one g).

it was typed correctly - the spell check changed it when I put in the question. Nuget is spelled correctly in the push statement.
Bob

Ben,
here is a copy of the error in proget.

Logged: 11/09/2017 10:27:08
Level: Error
Category: HTTP
Message: An error occurred in the web application: Unable to write data to the transport connection: Connection reset by peer.
Details: URL: http://quark/administration/error-log/entry?messageId=17
Referrer: http://quark/administration
User: Admin
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Edge/15.15063
Stack trace: at Inedo.Web.PageFree.SimplePageBase+<ProcessRequestAsync>d__48.MoveNext () [0x003d2] in <b3c8f625a9674e54b534ab21fc34bde8>:0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <77c9551943624fd18301ba6f78a841e5>:0
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0003e] in <77c9551943624fd18301ba6f78a841e5>:0
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x00028] in <77c9551943624fd18301ba6f78a841e5>:0
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x00008] in <77c9551943624fd18301ba6f78a841e5>:0
at System.Runtime.CompilerServices.TaskAwaiter.GetResult () [0x00000] in <77c9551943624fd18301ba6f78a841e5>:0
at System.Web.TaskAsyncResult.Wait (System.IAsyncResult result) [0x00032] in <d777bf5120224d38839a5bae355ed440>:0
at System.Web.HttpTaskAsyncHandler.System.Web.IHttpAsyncHandler.EndProcessRequest (System.IAsyncResult result) [0x00000] in <d777bf5120224d38839a5bae355ed440>:0
at Inedo.Web.Handlers.AsyncHandlerWrapper.EndProcessRequest (System.IAsyncResult result) [0x00000] in <b3c8f625a9674e54b534ab21fc34bde8>:0
at System.Web.HttpApplication.async_handler_complete_cb (System.IAsyncResult ar) [0x00015] in <d777bf5120224d38839a5bae355ed440>:0

Bob

Ben,
Here is the nuget statement used.

e:\tools\nuget\nuget push x64GigaSoftProEssentials.7.0.2.nupkg -Source http://quark/nuget/RlsTech -ApiKey Admin:test

bob

ben

Could you capture a Fiddler or WireShark trace of the ProGet response? There should be an error message associated with the 400 (either There must be exactly one package., which would indicate a proxy issue or Package validation failed: followed by an error message, although from a quick glance over the source code, I don't see how that could happen for a NuGet package.)

Another possible cause is an IIS module, like WebDav, intercepting the request before it gets to ProGet.