May 31, 2012 at 3:21 PM
Edited May 31, 2012 at 4:10 PM
My team has an internal Nuget.Server feed that we set up a couple of months ago. It was working correctly with Nuget 1.6, but it's failing now.
I'm able to view the landing page in a browser and see a list of packages in Visual Studio, but attempting to install one results in a vague error:
Operation failed. Unable to connect to the remote server
We've updated our package manager extesions to 1.8, which is probably what caused the problem. I've since updated the feed to the latest Nuget.Server version, but we're still seeing the issue.
UPDATE: I did some snooping around with Fiddler, and it looks like the issue is being caused by our use of a load balancer to handle the incoming traffic. Our site is configured to use SSL (no authentication), but the load balancer decrypts the traffic and
passes it along to IIS. Nuget.Server looks at the incoming request, sees http and uses that in the URLs that it generates for the packages.
Is there a convenient way to force the server to use https when formatting the URLs?