We have always used TeamCity NuGet feed to source our packages in Octopus. Recently we migrated our TeamCity instance to a new server.
When we try to deploy we get the following:
The step failed: Activity failed with error 'The package [PACKAGE] v18.104.22.16805-256 could not be downloaded to the package cache from NuGet feed ‘TeamCity Feed’ after making 5 attempts over a total of 104s. Make sure the package is pushed to the feed and try the deployment again. For a detailed troubleshooting guide go to http://g.octopushq.com/TroubleshootMissingPackages
System.Exception: Unable to download package [PACKAGE] v22.214.171.12405-256 from NuGet feed ‘TeamCity Feed’: Error downloading .126.96.36.19905-256 from http://[OUR TEAMCITY SERVER]:443/httpAuth/app/nuget/feed/_Root/default/download/[PROJECT]/43868:id/nupkgs/[PATH]/[PACKAGE].188.8.131.5205-256.nupkg —> System.Exception: Error downloading [PACKAGE].184.108.40.20605-256 from http://[OUR TEAMCITY SERVER]:443/httpAuth/app/nuget/feed/_Root/default/download/[PROJECT]/43868:id/nupkgs/[PATH]/[PACKAGE].220.127.116.1105-256.nupkg —> System.Net.Http.HttpRequestException: Response status code does not indicate success: 400 (Bad Request).
Now, the interesting bit above is that it shows “http://” but specifies port :443 which would cause the 400 bad request.
If I use the link in the error message above directly and we are authenticated with our TeamCity server, we can download the package.
In the External Feeds we specify:
https://[OUR TEAMCITY SERVER]/httpAuth/app/nuget/feed/_Root/default/v2
Where we use “https://” - we have also tried “http://” and supplying the ports in the URL as well, nothing fixes this issue.
If we use the “Test” function, then packages can be searched for, and the correct versions shown.
We have tried deleting the feeds and creating new ones, and this still doesn’t resolve this error.
Any pointers would be great as this is blocking us at the moment.