Nuget.Server can list packages but 404's on package install
<p>So I have an ASP.Net Nuget Server running on a machine on our network. I'm using .Net 4.6 with Nuget.Server version 2.11.2.0 and IIS 8.</p>

<p>This is connected to our automated build system so the packages are automatically created and copied to the ~/Packages directory after a successful build, when I go to the server URL in a browser I can see the splash page and click on the packages link to see the available packages XML page. If I put the package URL into Nuget settings in Visual Studio then it will list the packages available but then 404 when I hit 'Install', see the image below.</p>

<p>Note that it also 404's when I try to push a package using the command on the server splash page.</p>

<p>I've tried using curl to see if the routes are actually available, I get a 404 from api/v2/package and also from nuget/package. The IIS logs showed a 404 on http:///api/v2/package//etc... so I figured I'd at least check that route was available, and it appears it isn't. I don't understand why this would be the case.</p>

<p><a href="https://i.stack.imgur.com/G4vvQ.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/G4vvQ.png" alt="list but fail install"></a></p>

<p>Things I have already tried;</p>

<ul>
<li>nupkg Mime type is set to application/zip in IIS</li>
<li>IIS Application Pool mode is set to integrated</li>
<li>aspnet_isapi.dll exists in both Framework64/Framework folders for .NET 4.5</li>
<li><code>runAllManagedModulesForAllRequests</code> is set to <code>false</code> in the Web.config</li>
</ul>

<p>My question essentially revolves around a few things; </p>

<ul>
<li>are there any internal ports that the server uses that I might not have opened yet? (i.e. I've opened port 51702 which is the default Nuget.Server port, but I'm assuming the http requests will run on port 80 or 443)</li>
<li>Has anyone else had a similar issue besides the things I've already tried?</li>
</ul>