Getting a 404 or 500 error is not typical when editing content with the WPBakery Page Builder. This guide will help you identify and resolve the most common causes behind these errors so you can get back to building your website!
What is a 404 Error?
A 404 error typically means the page or request could not be found. If you’re seeing a 404 error when trying to use the WPBakery Page Builder, it’s a sign that something is misconfigured. This is not normal behavior and usually points to an issue with permalink settings, plugin conflicts, or server rules blocking the editor’s request.
A 404 typically means WordPress is unable to locate the proper admin route to open the page builder, often due to a redirect, rewrite rule, server error or blocked request.
What is a 500 Error?
A 500 Internal Server Error occurs when something goes wrong on the server while processing a request. It’s a generic error message that doesn’t specify the exact problem but typically indicates issues with the server’s software, configuration, or resources.
This could be caused by faulty code, server misconfigurations, or resource limitations. Users generally can’t fix this, and it’s up to the website’s admin to diagnose and resolve the issue.
Common Causes & Solutions
If you’re encountering a 404 error when launching the WPBakery editor, below are the most frequent reasons this issue occurs, along with steps to help you quickly resolve it.
Outdated Software
Running outdated versions of WPBakery, WordPress, or Total can lead to compatibility issues. Make sure everything is up to date.
Known Godaddy Issue (but could happen on other servers)
Godaddy has a known issue that doesn’t always happen but it’s quite common on their non-WordPress dedicated plans.
Fix: Add the following code to your .htaccess file
<IfModule mod_substitute.c>
SubstituteMaxLineLength 10M
</IfModule>Permalink Settings Are Out of Sync
Sometimes WordPress’s internal routing gets confused.
Fix: Go to Settings > Permalinks and click “Save Changes” to refresh your permalink structure. You don’t need to make any changes, just save the settings.
Plugin Conflicts
Other plugins (such as security or caching plugins) can interfere with WPBakery’s functionality..
Fix: Temporarily deactivate all plugins except WPBakery. Check if the error is resolved. Reactivate plugins one by one to find the conflicting one.
ModSecurity or Hosting Firewall
Some hosting environments block WPBakery’s AJAX or admin routes for security reasons.
Fix: Contact your web host and ask them to check if ModSecurity or any firewall is blocking the editor URLs or POST requests to admin-ajax.php.
Server Resource Limits
If your PHP memory or execution time is too low, the builder might not load. You can easily check the server values via the Theme Panel on the right side under “System Status”, you would want to see all green backgrounds on the values instead of red.
Fix: Ask your host to increase PHP memory and execution time. Or add the following to your wp-config.php file if you feel confident enough to edit this file”
define('WP_MEMORY_LIMIT', '256M');
set_time_limit(300);Still Seeing the Error?
If none of the above steps resolve the issue:
- First check your server error logs in case an error has been recorded that can help troubleshoot.
- Try switching temporarily to a default theme (like Twenty Twenty-Four) to confirm if the issue is theme-related.
- If the problem goes away, re-enable the Total theme and double-check WPBakery settings under Role Manager and ensure the builder is enabled for your user role and post type.
- Reach out to our support team for further assistance.