At one of my customers we are creating our own internal NuGet server. This is very easy to setup thanks to the availability of the NuGet.Server package.
Create a new empty ASP.NET website, add the NuGet.Server package and deploy the solution, that’s all! New packages should be added to the available package folder and are automatically discovered by NuGet.Server. This all worked fine until we tried to download our first package.
We got the following error back:
“The remote server returned an error: (401) Unauthorized.”
We solved the issue by giving everyone read rights on the package folder. Afterwards we were able to download the packages fine.
Anyone with a different/better solution?