When Breakdance throws an error, the most reliable way to fix it fast is to reproduce the problem, gather the right logs, and loop in your web host (or us). This guide walks you through that process. It also shows how to capture errors easily with WP Debug Toolkit (our partner tool).
Hosts often enforce limits that terminate long-running processes. Two common examples:
max_execution_time in php.ini. Increasing this is a last resort.FcgidIOTimeout governs how long mod_fcgid waits on reads/writes. In many environments, ~90 seconds is sufficient.If you consistently hit timeouts, contact your host to review and raise these limits as appropriate.
500-level responses usually indicate a server or PHP error, or an overloaded environment. For detailed, Breakdance-specific guidance, see our article:
Troubleshooting 500/50x Errors
403s are commonly caused by security layers (WAF, ModSecurity, firewall, CDN rules) blocking legitimate requests. See:
Servers throw numeric error codes when misconfigured or overloaded. A few common ones:
Breakdance Support can’t fix server configuration problems directly. Your host must locate and resolve the underlying issue, which requires the server logs.
To find what’s wrong, check your server error logs and look for possible errors that appear and could be related to the problem. The simplest way to do this is to use our partner tool WP Debug Toolkit, which is gonna display all errors from your server, and you can get it at a discount using the code BDDOC.
If you’re unable to find these errors logs yourself, your host should examine the server’s error logs for entries at the time the error occurred. To help them help you, include the following data when reaching out to your web host support team:
If errors are happening but your host can’t find entries, ask them to ensure logging is enabled and that they’re checking the right places. Errors are typically logged at least in:
If needed, try a different support channel (phone/chat) or ask to be escalated to a higher support tier.
Once you’ve obtianed the error logs, send us the relevant error logs entries via our support channels and we’ll assist you troubleshoot and fix the error.
If your host can’t provide server logs, and WP Debug Toolkit isn’t an option, enable WordPress’s built-in debugging to capture PHP errors. After enabling, reproduce the issue and share the entries from the time it occurred. Note: many logs are in UTC. You can compare time zones at everytimezone.com.
See the official guide: Debugging in WordPress.
// Add (or update) in wp-config.php above "/* That's all, stop editing! */" define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true ); // writes to wp-content/debug.log
define( 'WP_DEBUG_DISPLAY', false ); // keep errors off the front-end @ini_set( 'display_errors', 0 );After reproducing the issue, download wp-content/debug.log and share the relevant lines (around the time of the error).
Sometimes your developer will request temporary file access to diagnose and fix issues.
Submit everything at breakdance.com/support/. The more precise your details, the faster we can help.
WP Debug Toolkit is a simple way to surface hidden PHP/WordPress errors and gather the exact logs our team needs.
We’ve partnered with them to offer a discount; use code BDDOC.
