Trying to follow the directions to host your own Nuget server
, I ran into a couple small problems when trying to deploy it to a Virtual Application within an Azure WebSite. I was able to successfully deploy this inside the Virtual Application using my previously posted directions
. But I still found these issues:
1. The URL was actually requiring a second nuget appended to the end (i.e. http://www.mydomain.com/nuget/nuget/).
2. When accessing the required URL above, I received this error:
This collection already contains an address with scheme http. There can be at most one address per scheme in this collection.
If your service is being hosted in IIS you can fix the problem by setting 'system.serviceModel/serviceHostingEnvironment/multipleSiteBindingsEnabled' to true
or specifying 'system.serviceModel/serviceHostingEnvironment/baseAddressPrefixFilters'.
The solution was to update the web.config to add this attribute to the element that was already there.
<serviceHostingEnvironment multipleSiteBindingsEnabled="true" aspNetCompatibilityEnabled="true"/>