You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Opening a new ticket with the same issues as Ticket #8171
I am working with Demandware and have contacted them but they are unable to find anything. I have the latest version of cyberduck but am on a mac which may be the issue. Including all info from previous ticket.
I set up an account on Magento's Big Commerce. Set up the WebDAV connection according to the instructions from Big Commerce. The login is successful, but then I get this error message:
LISTING DIRECTORY FAILED (/)
NOT A VALID DAV RESPONSE
I contacted the support at Big Commerce. They could not duplicate the problem on their end. Any idea of what might be happening and how I can correct this?
Please update to the latest version which is currently 4.7. The transcript shows you are running version 4.4.3. Use Help → Check for Update… to update.
The transcript is from the old ticket. I just added it to the new ticket for reference. I am running the latest version of Cyberduck 4.7 and am still receiving the same error.
Hi, Having similar issue also on version 4.7. Issue seems to be specific to one directory that includes files larger then 10MB. One file is 47MB. Other directories on the same server work fine. Is there a work around to access this folder?
Opening a new ticket with the same issues as Ticket #8171
I am working with Demandware and have contacted them but they are unable to find anything. I have the latest version of cyberduck but am on a mac which may be the issue. Including all info from previous ticket.
I set up an account on Magento's Big Commerce. Set up the WebDAV connection according to the instructions from Big Commerce. The login is successful, but then I get this error message:
LISTING DIRECTORY FAILED (/)
NOT A VALID DAV RESPONSE
I contacted the support at Big Commerce. They could not duplicate the problem on their end. Any idea of what might be happening and how I can correct this?
Below I've copied the event log:
Attachments
2015-06-18_00-13-04.jpg
(94.1 KiB)2015-06-18_00-14-07.jpg
(47.3 KiB)2015-06-18_00-15-02.jpg
(100.4 KiB)The text was updated successfully, but these errors were encountered: