BigCommerce WebDAV Upload Errors: The Cyberduck Version Compatibility Fix

Mastering BigCommerce File Management: Solving the Persistent Cyberduck WebDAV Upload Error

As an e-commerce expert at Big Migration, we understand that efficient file management is the backbone of a thriving online store. Whether you're a merchant uploading product images, a developer deploying custom theme assets, or managing crucial digital product files, tools like Cyberduck, leveraging WebDAV (Web Distributed Authoring and Versioning), are indispensable for interacting with your BigCommerce store's file system. However, encountering unexpected errors can bring your workflow to a grinding halt. This article delves into a specific, frustrating WebDAV upload error and provides a confirmed, community-driven solution that can save you hours of troubleshooting.

The error in question, "Cannot retry request with a non-repeatable request entity," has puzzled many BigCommerce users. It often appears when attempting to upload files, especially larger ones, leading to the assumption of new file size restrictions. Let's explore the problem, common misconceptions, and the definitive fix.

The Challenge: A Mysterious Upload Blocker

A BigCommerce user, Susan Burgoyne, reported a persistent issue when trying to upload a 5.5MB PDF file via Cyberduck. The specific error message was the cryptic: "Cannot retry request with a non-repeatable request entity." Her immediate concern, and a common initial thought for many, was that BigCommerce had introduced a new, stricter file size limit. This was particularly perplexing given her past success with uploading much larger files.

This scenario highlights a critical point for anyone managing an e-commerce store: unexpected errors can quickly derail essential tasks, from updating product catalogs to deploying critical theme changes. Such errors can impact everything from SEO (due to missing images) to customer experience (unavailable digital products).

Initial Troubleshooting: Separating Fact from Fiction

The BigCommerce community, ever helpful, quickly offered insights. Sri Vathson clarified a crucial distinction: this error is typically related to the WebDAV client itself or the network connection, rather than a new BigCommerce platform file size restriction. This shifts the focus from platform limitations to client-side or network-related issues, which are often more within the user's control to troubleshoot.

Sri Vathson provided a comprehensive list of initial troubleshooting steps, which are excellent general practices for any WebDAV issues:

• Verify File Integrity: "Verify the PDF isn't corrupted by opening it locally." A corrupted source file can lead to upload failures regardless of the client or server.
• Isolate the Issue: "Try uploading a different PDF of similar size to see if the issue is file-specific." This helps determine if the problem lies with a particular file or is a broader client/connection issue.
• Client Restart & Reconnection: "Restart Cyberduck and reconnect to WebDAV." A fresh start can resolve temporary glitches in software or network connections.
• Software Updates: "Update Cyberduck to the latest version if you're not already running it." While counter-intuitive to the eventual fix, keeping software updated is generally a good practice for security and bug fixes.
• Network Diagnostics: "Test from a different network or temporarily disable any VPN/proxy, as interrupted uploads can trigger this error." Network instability, VPNs, or proxies can interfere with data transfer, leading to incomplete or failed requests.

These steps are fundamental for any developer or merchant facing integration challenges, providing a systematic approach to problem-solving before escalating to platform support.

The Breakthrough: Version Compatibility is Key

Despite thorough troubleshooting, the problem persisted for Susan. This is where community wisdom truly shines. Freetail Commerce shared a critical insight: they had encountered this issue previously, and BigCommerce support had advised them to downgrade to an older version of Cyberduck. Specifically, they recommended trying Cyberduck version 8.6.3.

This revelation points to a common challenge in software development and integrations: compatibility. New versions of client software, while bringing new features, can sometimes introduce breaking changes or incompatibilities with existing APIs or protocols, even if those protocols (like WebDAV) are standard. BigCommerce's WebDAV implementation, while robust, might have specific nuances that newer Cyberduck versions temporarily struggle with.

The Confirmed Solution: Downgrading Cyberduck to 8.6.3

Susan Burgoyne, who had recently upgraded to Cyberduck version 9.5.0, followed Freetail Commerce's advice. The result was immediate and positive: downgrading to Cyberduck version 8.6.3 fixed the problem entirely. She was once again able to upload files larger than 5.1MB without encountering the "Cannot retry request" error.

This confirmed solution underscores the importance of version management in your development and integration toolkit. While keeping software updated is generally recommended, sometimes a specific older version offers the stability required for particular integrations. BigCommerce often lists recommended client versions on its official WebDAV support pages, which are invaluable resources for merchants and developers.

Broader Implications for BigCommerce Merchants & Developers

This incident offers several key takeaways for anyone working with BigCommerce:

• Version Control Matters: Always be mindful of the software versions you're using, especially for critical integration tools. Keep a record of what works.
• Community is Gold: The BigCommerce community forums are a treasure trove of shared experiences and solutions. Don't hesitate to search or ask for help.
• Systematic Troubleshooting: Follow a logical sequence of steps (file, client, network) before assuming platform-level issues.
• BigCommerce Support: If community solutions don't work, provide BigCommerce support with detailed information: exact error messages, client versions, steps taken, and screenshots.
• Migration Context: For businesses undergoing a BigCommerce migration, ensuring all file transfer mechanisms (like WebDAV) are fully functional and compatible with existing assets is paramount. Big Migration specializes in pre-empting and resolving such integration challenges to ensure a smooth transition of all your digital assets.

In conclusion, while the "Cannot retry request with a non-repeatable request entity" error can be frustrating, the solution for BigCommerce users often lies in a simple, yet critical, step: ensuring you're using a compatible version of your WebDAV client, such as Cyberduck 8.6.3. By understanding these nuances, you can maintain a seamless workflow for your BigCommerce store's file management.