Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you may not be able to execute some actions. Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

I'm trying to get choco push running by using an API-Key however I'm stuck...

PS C:\temp> [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
PS C:\temp> choco push .\notepadplusplus.install.8.5.1.nupkg --source='https://FQDN:444/nuget/choco_test/' --api-key='f034ae62f74d49325da3cb7cb795576f2160bcea' -v
Chocolatey v1.3.1
Attempting to push notepadplusplus.install.8.5.1.nupkg to https://FQDN:444/nuget/choco_test/
PUT https://FQDN:444/nuget/choco_test/
Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host.
PS C:\temp>
I see HTTP 500s in IIS logs
2023-05-23 09:38:08 10.3.120.67 PUT /nuget/choco_test/ - 444 - 10.31.212.194 Chocolatey+Command+Line/1.3.1.0+(Microsoft+Windows+NT+10.0.17763.0) - 500 0 64 128325
... and these errors within ProGet:
Message:An error occurred processing a PUT request to https://FQDN:444/nuget/choco_test/: The client has disconnected
Details: Microsoft.AspNetCore.Connections.ConnectionResetException: The client has disconnected
---> System.Runtime.InteropServices.COMException (0x80070040): The specified network name is no longer available. (0x80070040)
--- End of inner exception stack trace ---
at Microsoft.AspNetCore.Server.IIS.Core.IO.AsyncIOOperation.GetResult(Int16 token)
at Microsoft.AspNetCore.Server.IIS.Core.IISHttpContext.ReadBody()
at System.IO.Pipelines.Pipe.GetReadResult(ReadResult& result)
at System.IO.Pipelines.Pipe.ReadAsync(CancellationToken token)
at System.IO.Pipelines.Pipe.DefaultPipeReader.ReadAsync(CancellationToken cancellationToken)
at Microsoft.AspNetCore.Server.IIS.Core.IISHttpContext.ReadAsync(Memory`1 memory, CancellationToken cancellationToken)
at Microsoft.AspNetCore.Server.IIS.Core.HttpRequestStream.ReadAsyncInternal(Memory`1 buffer, CancellationToken cancellationToken)
at Microsoft.AspNetCore.WebUtilities.BufferedReadStream.EnsureBufferedAsync(Int32 minCount, CancellationToken cancellationToken)
at Microsoft.AspNetCore.WebUtilities.MultipartReaderStream.ReadAsync(Byte[] buffer, Int32 offset, Int32 count, CancellationToken cancellationToken)
at Microsoft.AspNetCore.WebUtilities.StreamHelperExtensions.DrainAsync(Stream stream, ArrayPool`1 bytePool, Nullable`1 limit, CancellationToken cancellationToken)
at Microsoft.AspNetCore.WebUtilities.MultipartReader.ReadNextSectionAsync(CancellationToken cancellationToken)
at Microsoft.AspNetCore.Http.Features.FormFeature.InnerReadFormAsync(CancellationToken cancellationToken)
at Microsoft.AspNetCore.Http.Features.FormFeature.ReadForm()
at Microsoft.AspNetCore.Http.DefaultHttpRequest.get_Form()
at System.Web.HttpFileCollection.get_Count()
at Inedo.ProGet.WebApplication.FeedEndpoints.NuGet.NuGetApi.PutHandler.ProcessPutRequestAsync(HttpContext context, WebApiContext apiContext, RequestData urlData, NuGetFeed feed)
at Inedo.ProGet.WebApplication.FeedEndpoints.NuGet.NuGetApi.ProcessRequestAsync(HttpContext context, WebApiContext apiContext, NuGetFeed feed, String relativeUrl)
at Inedo.ProGet.WebApplication.FeedEndpoints.NuGet.NuGetFeedHandler.ProcessRequestAsync(HttpContext context, WebApiContext apiContext, NuGetFeed feed, String relativeUrl)
at Inedo.ProGet.WebApplication.FeedEndpoints.FeedEndpointHandler.FeedRequestHandler.ProcessRequestAsync(HttpContext context)
Uploading packages via GUI is working fine and I'm also able to connect to that given URL via browser, showing me an XML-answer for packages.
Help is highly appreciated :)
Kind regards
	
Hi @norbert ,
Based on the error messages, the problems is occurring somewhere between the ProGet and choco.
Chocolatey is reporting that the remote connection was forcibly closed.
ProGet is reporting that the client unexpectedly disconnected.
It's the equivalent of someone "cutting the cord" halfway through the communication, and there's no way to know where that happened or why.
You'll need to investigate intermediate equipment. Typically it's a firewall, ,proxy, or other gateway that is misconfigured.
Cheers,

Alana
seems like we're dealing with a loopback issue on the IIS itself. Pushing from other servers on the network works.
Thank you! :)