You click “Update” or “Publish” in the WordPress editor and the button just spins. The post never saves. Sometimes you see “Updating failed” or “Publishing failed. The response is not a valid JSON response.”

This is one of the most common WordPress issues. Here’s how to fix it, from quickest to most involved.

Quick Fixes (Try These First)

1. Hard Refresh and Retry

Press Ctrl+Shift+R (Windows) or Cmd+Shift+R (Mac) to bypass the browser cache, then try saving again.

2. Check Your Internet Connection

The WordPress block editor (Gutenberg) communicates with your server via AJAX/REST API calls. If your connection drops even briefly, saves will fail. Try switching from Wi-Fi to a wired connection, or test on a different network.

3. Try a Different Browser

Open your site’s admin in Chrome, Firefox, or Edge. If it works in another browser, a browser extension is likely interfering (see step 5).

REST API Issues

The most common root cause. WordPress needs its REST API to save content, and something is blocking it.

4. Test REST API Access

Visit this URL in your browser (replace with your domain):

  https://yourdomain.com/wp-json/wp/v2/posts
  • If you see JSON data – the REST API is working. Skip to step 5.
  • If you get a 403, 404, or blank page – something is blocking the API. Continue below.

Common REST API Blockers

Security plugins. Wordfence, Sucuri, or iThemes Security may block API requests. Temporarily disable them and test.

ModSecurity rules. Your server’s firewall may be blocking REST API requests. Check cPanel > ModSecurity (if available) and see if there are recent blocks for your IP.

.htaccess rules. Custom redirect or security rules in .htaccess can accidentally block the /wp-json/ path. Try renaming .htaccess temporarily:

  mv .htaccess .htaccess_backup

Then try saving. If it works, you’ll need to review the .htaccess rules to find the conflicting one.

Permalink structure. Go to Settings > Permalinks and click Save Changes (even without changing anything). This regenerates the rewrite rules that make REST API URLs work.

Plugin and Theme Conflicts

5. Disable Browser Extensions

Ad blockers, privacy extensions, and script blockers can break the WordPress editor. Try:

  • Opening the editor in an incognito/private window
  • Temporarily disabling all browser extensions

6. Deactivate All Plugins

If browser extensions aren’t the problem, a server-side plugin may be breaking things:

  1. Connect via SSH or cPanel File Manager
  2. Rename the plugins folder:
      mv wp-content/plugins wp-content/plugins_disabled
  3. Try updating your post
  4. If it works, rename the folder back and reactivate plugins one by one to find the culprit:
      mv wp-content/plugins_disabled wp-content/plugins

7. Switch to a Default Theme

If deactivating plugins doesn’t help, switch to a default theme (Twenty Twenty-Four, Twenty Twenty-Three):

  # Via WP-CLI if available
wp theme activate twentytwentyfour

# Or via database (phpMyAdmin > wp_options table)
# Find 'template' and 'stylesheet' rows, change values to 'twentytwentyfour'

Server-Side Issues

8. Increase PHP Memory Limit

The editor needs enough memory to process save requests. In wp-config.php, add:

  define('WP_MEMORY_LIMIT', '256M');

Or in .htaccess:

  php_value memory_limit 256M

9. Check PHP Error Logs

Enable WordPress debug logging to see what’s going wrong:

  // In wp-config.php
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);

After trying to save, check wp-content/debug.log for error messages.

10. Check Server Resource Limits

On GoZen Host shared plans, check your CloudLinux resource usage in cPanel. If you’re hitting CPU or Entry Process limits, the REST API requests may be getting throttled.

Still Not Working?

If none of the above fixes the problem:

  1. Try the Classic Editor. Install the Classic Editor plugin. It doesn’t rely on the REST API and may work while you diagnose the issue.
  2. Contact support. Open a ticket at GoZen Host support with your domain and a screenshot of the error. Our team can check server logs for you.

Last updated 14 Apr 2026, 08:40 +0300. history

Was this page helpful?