Nuget.exe Push Error for HTTPS URL

(jian huang) #1

Hi Octopus team,

I used to use ‘http’ to push packages, recently we have a new ‘https’ url to push package, however encountering issue when using this new ‘https’, currently we have 2 build servers, looks like one build server is fine, but another is not.

Build server A:
Windows Server 2012 R2
.Net Framework - 4.7.2
Nuget.exe - 05/12/2016 (not sure which version is this)

When using nuget.exe to push, both ‘http’ and ‘https’ work fine

Build server B:
Windows Server 2012 R2
.Net Framework - 4.5.2
Nuget.exe - 05/12/2016 (not sure which version is this)

When using nuget.exe to push, only ‘http’ works, however getting following error for ‘https’:
‘C:\Octopus\NuGet.exe : The underlying connection was closed: An unexpected error occurred on a send.
Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.’

Please help to identify the problem, thanks.

Jian

(Henrik Andersson) #2

Hi Jian,

What do you see if you try to access your Octopus URL (over https) in a browser from the server that is having issues (Build server B)?

To me, this looks more to be an environmental issue rather than an Octopus issue since it all works fine from Build server A.

Thank you and best regards,
Henrik

(jian huang) #3

Hi Henrik,

If browse Octopus URL (over https) in browser, it works fine. Which it is why this issue looks strange to me. Any way I can further to debug or troubleshoot this issue?

Thanks.

Jian

(Henrik Andersson) #4

Hi Jian,

You could have a look in your Octopus server log after you’ve tried to use nuget.exe to push a package to your server, this may have some more information about what actually went wrong (NuGet.exe is notoriously bad at surfacing errors).

If that doesn’t give any more information, as the only difference between the two build servers seem to be the .NET framework that is installed. Are you in a position where you can update Build server B to 4.7.2 and see if that resolves the issue?

Thanks,
Henrik

(system) closed #5

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.