405 Method Not Allowed in NuGet Push

Question

My NuGet server is throwing a 405 Not Allowed when I try to make a push. At least, thats what NuGet console says:

Failed to process request. 'Method Not Allowed'.
The remote server returned an error: (405) Method Not Allowed..

But when I look at the actual HTTP response with Fiddler the problem seems to be totally different:

<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<error xmlns="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata">
  <code></code>
  <message xml:lang="en-US">The URL representing the root of the service only supports GET requests.</message>
</error>

Any ideas on what might be going on?

Thanks!

If you get here and are looking at this issue make sure you do as the OP has and check the HTTP response, not all 405s are the same and NuGet doesn't give you the full detail. — Liam, Dec 07 '17 at 14:19

score 56 · Accepted Answer · answered May 09 '13 at 02:06

56

After a few hours working on the issue I was able to find the problem.

When you LIST packages in NuGet server you point to http://nugetserver.com/nuget. However when you are trying to PUSH or DELETE a package you need to point to http://nugetserver.com without the nuget folder in the path.

What happens is that NuGet.exe append /api/v2/package to the URL turning it into http://nugetserver.com/api/v2/package

I think this is far from optimal because it makes you add two different sources to your nuget.exe.config: one for the get/list and another for pushing/deleting packages.

answered May 09 '13 at 02:06

tucaz

6,524
6
37
60

I am hosting the feed in my local dev server. If I just use the url without /nuget it throws error: 404 (Not Found) . I have done all from removing webdev, adding permission etc but still gives me error. – aman Jan 24 '18 at 19:54
Has this changed? I just updated an old NuGet Server and now it fails unless the extra `/nuget` is added to the push source as well. (Before the update the extra `/nuget` was not allowed to be in the push source.) – Peter Feb 05 '18 at 10:28

score 54 · Answer 2 · edited Dec 07 '17 at 11:34

54

In addition to using nuget push -Source http://nugetserver.com, I did this:

<!--Add the following to the beginning of <system.webServer><modules>:-->
<remove name="WebDAVModule" />
<!--Add the following to the beginning of <system.webServer><handlers>:-->
<remove name="WebDAV" />

Source: Nuget issue #1789

edited Dec 07 '17 at 11:34

Liam

27,717
28
128
190

answered Aug 06 '13 at 21:00

Kevin Smyth

1,892
21
22

7

Also make sure the IIS user has write permissions on the Packages folder – juanagui Aug 07 '13 at 17:59
5

As an alternate to modifying the web.config, you can remove WebDAVModule in IIS, at server level, site level, or even app level. In IIS Manager, click the server in the tree (or the site), then open Modules (under IIS), find WebDAVModule near the bottom of the list, then remove it. – biscuit314 Dec 03 '14 at 15:31
this also helped me. Thanks! – DolceVita May 31 '16 at 12:41
Put this where? – tnk479 Jan 08 '22 at 20:38

score 4 · Answer 3 · answered Feb 08 '16 at 18:00

I had the same error - in my case, my NuGet environment variable was pointing to an old v2 version of NuGet, and I was trying to push to a v3 feed.

Repointing my environment variable to a v3 NuGet.exe fixed it.

Silly error, but hopefully that might save someone some time.

score 1 · Answer 4 · answered Apr 22 '15 at 19:26

1

the solution for me - running a local IIS on a Win 8.1 computer -
was to enable "Windows authentication" and "ASP.NET Impersonation"

answered Apr 22 '15 at 19:26

oakman

297
1
8

score 0 · Answer 5 · answered Feb 02 '15 at 10:24

0

The fix for me was in IIS. I disabled windows authentication and enabled anonymous authentication.

I was pushing to my own nuget server.

answered Feb 02 '15 at 10:24

theUser

1,346
3
21
40

WHich is the opposite of what one of the answers above suggests. – tnk479 Jan 08 '22 at 20:47

score 0 · Answer 6 · answered Dec 27 '18 at 16:49

I'm running version 3.1.2. After battling with this problem for a while, the following did it for me:

Give write permissions to the Packages folder on the server
Because I had deleted the previous packages in the Packages folder, I also had to delete the '*.cache.bin' file in the Packages folder.
Ran command as "nuget.exe push {package file} {apikey} -Source {ipaddress:port}/nuget" Note the "/nuget" at the end.

score 0 · Answer 7 · answered Apr 17 '20 at 10:20

0

Solution for me was to use latest Nuget.exe [3.5.0], for some strange reason I had old NuGet.exe (2.8.5 [2017 version]) which was failing with 405 error. Hope this helps someone.

answered Apr 17 '20 at 10:20

Mahesh Nayak

208
4
14

I'm using visual studio 2019. How can I tell what version of Nuget.exe I am using? – tnk479 Jan 08 '22 at 20:27

score 0 · Answer 8 · answered Oct 07 '21 at 11:06

0

If you have IIS 8.0, WebDAV publishing method doesn't allow nuget Push. Uninstall it from IIS and things would work WebDAV uninstall

answered Oct 07 '21 at 11:06

Ankit

1

405 Method Not Allowed in NuGet Push

8 Answers8

Linked