Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot push packages #487

Closed
FHanji opened this issue Apr 24, 2012 · 3 comments
Closed

Cannot push packages #487

FHanji opened this issue Apr 24, 2012 · 3 comments

Comments

@FHanji
Copy link

FHanji commented Apr 24, 2012

Hello,

I didn't find any solution to my issue. It looks like to issues on this tracker (like this one #409 or this one #290) but I can't fix it yet.

My problem is I can't push packages except on the web site (Inexplicably, it works perfectly through a browser). If I try with the command line or the NPE, it fails. This is what I tried and what i get :

Command line :

nuget push $my_package $my_api_key -Source http://$my_root_url/
Failed to process request. 'Methode Not Allowed'.
The remote server returned an error: (405) Method Not Allowed..

So I tried to add s to http :

nuget push $my_package $my_api_key -Source https://$my_root_url/
The underlying connection was closed: The connection was closed unexpectedly. (I am not sure this is the true error because my message is in french and says something more like "The underlying connection was closed: An unexpected error happened during the sending", but this is a litteral translation and I think this is the same error)

I also tried some combination in the URL, adding "/api/v2", "/api/v2/package", with s or not to http, etc. I always get the same errors.

I tried with NPE too :

Publish URL : http://$my_root_url/
Publish key : $my_api_key
Unable to process request. 'Methode Not Allowed'.
The remote server returned an error: (405) Method Not Allowed..

And I tried with adding 's' to 'http' : It didn't fail but it looks it turns into an infinit loop.

Again, I tried some combination in the URL, adding "/api/v2", "/api/v2/package", etc, with s or not to http, etc. I always get the same errors.

I am using this version of the Gallery : 345ea25 and running on Win Server 2008 R2. I disable the https on logon because we don't need it, but it failed even before i did that. We also are under a proxy.

Help me please T_T.

Thanks

@FHanji
Copy link
Author

FHanji commented Apr 26, 2012

We cleaned the server and we install the gallery a new time and it works almost.

For some users, they can push packages, there is no problem. But for the others (including the first user who is also the only one administrator), we get a new error :

Failed to process request. 'The specified API key does not provide the authority to push packages.'.
The remote server return an errror : (403) forbidden..

@matthewskelton
Copy link

This is probably a result of WebDAV being installed in IIS - it seems to interfere with the settings required for NuGet Gallery.

We certainly saw a similar issue with 405 errors, and uninstalling the WebDAV module fixed the problem.

@azzlack
Copy link

azzlack commented Jun 4, 2012

Instead of uninstalling WebDAV, you can do what is described here: #514

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants