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

Error: Listing directory failed. Method Not Allowed. #8095

Closed
cyberduck opened this issue Jul 18, 2014 · 9 comments
Closed

Error: Listing directory failed. Method Not Allowed. #8095

cyberduck opened this issue Jul 18, 2014 · 9 comments
Assignees
Labels
bug high priority thirdparty Issue caused by third party webdav WebDAV Protocol Implementation

Comments

@cyberduck
Copy link
Collaborator

bef5d08 created the issue

I have been using Cyberduck unlicensed for a few weeks. Today I decided to make a donation, but now I cannot connect to the server where I need to upload files. When I try to connect, I receive an error message stating, Listing directory failed. Method Not Allowed. Help! Cyberduck is useless to me if I cannot access this server.


Attachments

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Please post the transcript from the log drawer (Ctrl-L).

@cyberduck
Copy link
Collaborator Author

@dkocher commented

See also #7227.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

You possibly have to specify an initial Path in the bookmark. Please contact your web hosting service provider for assistance.

@cyberduck
Copy link
Collaborator Author

bef5d08 commented

Sorry, I wasn't available to respond to your comments on this issue over the weekend as I use Cyberduck on my work computer.

I've reviewed them and looked through the linked issues. The only comment that gave me direction was to specify an initial path in the bookmark. I tried this, but it didn't solve the problem. I don't receive the error message, but the directory contents do not list.

I've captured log information from when I connect initially to the WebDav server (which didn't work initially, but started working Friday after I had already logged the bug with Cyberduck). I've also captured the log when I try to open the directory I need to use (where I still get the error). There are significant differences, which no doubt account for the issue, but I'm not technical enough to understand how to fix it. I'm attaching a text file with both issues.

Please note that I am not on Windows 8. My computer is running Windows 7 Professional Service Pack 1. I wish I knew what version of Cyberduck I was using before I decided to make a donation, because that version was working for me.

Regards, Carolyn Milligan

@cyberduck
Copy link
Collaborator Author

@dkocher commented

That is a configuration issue with the web server which does not allow to connect with WebDAV to the path /euf/.

@cyberduck
Copy link
Collaborator Author

bef5d08 commented

Nothing has change on the web server configuration. I was able to connect to the euf directory before I donated to Cyberduck and installed the registration key. Now I can't. Only Cyberduck changed.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:8 milligan]:

Nothing has change on the web server configuration. I was able to connect to the euf directory before I donated to Cyberduck and installed the registration key. Now I can't. Only Cyberduck changed.

I doubt that. Please contact your web hosting service provider for assistance.

@cyberduck
Copy link
Collaborator Author

bef5d08 commented

Replying to [comment:9 dkocher]:

Replying to [comment:8 milligan]:

Nothing has change on the web server configuration. I was able to connect to the euf directory before I donated to Cyberduck and installed the registration key. Now I can't. Only Cyberduck changed.

I doubt that. Please contact your web hosting service provider for assistance.

On Friday, I connected to the WebDAV server and uploaded some image files to a sub-directory under /euf/. When I finished and exited Cyberduck, I decided to use the "Donate Now" option and get a registration key. (A decision based on the fact that I've been using Cyberduck for a couple of months and it was meeting my needs for uploading/downloading files to the WebDAV server for our web support platform. As soon as I applied the registration key, it changed my Cyberduck installation, and I haven't been able to connect to the /euf/ directory since then. I seriously doubt the problem is on our web server.

I'm extremely frustrated - I licensed Cyberduck and it changed from a perfectly useful client that was meeting my needs to a pain in my neck that is totally unusable.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:10 milligan]:

Replying to [comment:9 dkocher]:

Replying to [comment:8 milligan]:

Nothing has change on the web server configuration. I was able to connect to the euf directory before I donated to Cyberduck and installed the registration key. Now I can't. Only Cyberduck changed.

I doubt that. Please contact your web hosting service provider for assistance.

On Friday, I connected to the WebDAV server and uploaded some image files to a sub-directory under /euf/. When I finished and exited Cyberduck, I decided to use the "Donate Now" option and get a registration key. (A decision based on the fact that I've been using Cyberduck for a couple of months and it was meeting my needs for uploading/downloading files to the WebDAV server for our web support platform. As soon as I applied the registration key, it changed my Cyberduck installation, and I haven't been able to connect to the /euf/ directory since then. I seriously doubt the problem is on our web server.

I'm extremely frustrated - I licensed Cyberduck and it changed from a perfectly useful client that was meeting my needs to a pain in my neck that is totally unusable.

The key does not change in any way the problem you are seeing. If you also upgraded to a newer version of Cyberduck in the same time, please install the prior version you had available from https://cyberduck.io/changelog/ and we can compare the transcript.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug high priority thirdparty Issue caused by third party webdav WebDAV Protocol Implementation
Projects
None yet
Development

No branches or pull requests

2 participants