Error when dotnet nuget push to Teamcity Feed

Answered

We have several developer machines that do not have access to the internet but have access to our internal TeamCity environment. The Teamcity server can access https://api.nuget.org and restores nuget packages as expected.

We are attempting to to push the nuget packages that are restored from nuget to the internal Teamcity nuget feed but keep receiving an error: "Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host.".

Does anyone have some insight how to fix this error and if possible, a step by step guide how to do this correctly?

Thanks

0
1 comment

Hello!

Could I ask you to:
1) enable debug-general logging preset;
2) restart the build which is pushing to internal feed;
3) collect full build log from the UI, teamcity-server.log and teamcity-nuget.log from <TeamCity Server>/logs and upload them to https://uploads.jetbrains.com/;
4) share the upload ID with me? 

0

Please sign in to leave a comment.