Solving BigCommerce WebDAV Upload Errors: Cyberduck Version Compatibility Fix

Solving BigCommerce WebDAV Upload Errors: Cyberduck Version Compatibility Fix

As e-commerce merchants and developers, efficiently managing files on your BigCommerce store is crucial. Whether it's uploading digital product files, updating theme assets, or managing other store resources, WebDAV (Web Distributed Authoring and Versioning) clients like Cyberduck are indispensable tools. However, encountering unexpected errors can halt your workflow. This community insight dives into a common WebDAV upload error and provides a confirmed solution from the BigCommerce community.

The Challenge: WebDAV Upload Frustrations

A BigCommerce user, Susan Burgoyne, reported a persistent issue when attempting to upload a 5.5MB PDF file via Cyberduck. The specific error message displayed was: "Cannot retry request with a non-repeatable request entity." Initially, Susan suspected a new BigCommerce file size restriction, especially since she had successfully uploaded much larger files in the past. This kind of error can be particularly frustrating as it prevents essential file management tasks.

Initial Troubleshooting & Misconceptions

The community quickly jumped in to offer assistance. Sri Vathson clarified that such an error is more often related to the WebDAV client or the connection itself, rather than a BigCommerce file size limit. This is a crucial distinction, as it shifts the focus of troubleshooting from platform restrictions to client-side or network issues. Sri Vathson provided a comprehensive list of initial troubleshooting steps:

  • Verify the PDF isn't corrupted by opening it locally.
  • Try uploading a different PDF of similar size to isolate if the issue is file-specific.
  • Restart Cyberduck and reconnect to the WebDAV server.
  • Update Cyberduck to the latest version.
  • Test from a different network or temporarily disable any VPN/proxy, as interrupted uploads can sometimes trigger this error.
  • If the problem persists, consider opening a support ticket with BigCommerce.

While these steps are excellent general troubleshooting practices, the core issue in this specific case lay elsewhere.

The Breakthrough: Cyberduck Version Compatibility

The decisive solution came from Freetail Commerce, who shared a critical piece of information based on their past experience with BigCommerce support. They revealed that the error could be bypassed by downgrading to an older, specific version of Cyberduck. Specifically, they recommended trying Cyberduck version 8.6.3, noting that this version was often referenced on BigCommerce's own WebDAV support pages.

This insight highlighted a common pitfall in software ecosystems: sometimes, the latest version isn't always the most compatible, especially when dealing with specific protocols or server implementations.

The Confirmed Solution

Susan Burgoyne confirmed that Freetail Commerce's advice was the exact fix needed. She had recently upgraded to Cyberduck version 9.5.0, which was causing the upload failures. By reverting to the recommended older version, 8.6.3, she was able to successfully upload files larger than 5.1MB again. This direct confirmation underscores the importance of community-shared knowledge and specific version compatibility when troubleshooting technical issues.

Key Takeaways for BigCommerce Users

This thread offers valuable lessons for anyone managing files on BigCommerce via WebDAV:

  • Don't always suspect file size limits first: Many upload errors stem from client-side software, network, or connection issues rather than platform restrictions.
  • Start with basic troubleshooting: Verify file integrity, test with different files, and restart your client and connection.
  • Consider software version compatibility: If you encounter persistent issues with a specific client like Cyberduck, especially after an update, investigate if an older, more stable version is recommended or known to work better with BigCommerce's WebDAV service.
  • Leverage community knowledge: The BigCommerce community forums are a goldmine for specific workarounds and solutions that might not be immediately obvious.

For BigCommerce merchants and developers, ensuring smooth file uploads is fundamental. This specific workaround for Cyberduck users facing the "Cannot retry request with a non-repeatable request entity" error is a prime example of how targeted community solutions can save significant time and effort.

Start with the tools

Explore migration tools

See options, compare methods, and pick the path that fits your store.

Explore migration tools