How to Fix “Updating Failed / Publishing Failed” Error
WordPress Troubleshooting & Fixes
How to Fix “Updating Failed / Publishing Failed” Error in WordPress
This error appears when WordPress fails to communicate with the REST API, blocking you from updating posts, editing pages, or publishing content. Learn every cause and every fix to resolve the “Updating Failed” or “Publishing Failed” message permanently.
1
Why This Error Happens
It’s caused by interruption between WordPress and the REST API.
The Gutenberg editor and WordPress core rely on the REST API to save and update content.
Common causes include:
- REST API blocked by security plugins
- Incorrect site URL settings
- SSL/HTTPS mixed content issues
- Caching plugins blocking requests
- Firewall / CDN blocking requests (Cloudflare)
- PHP memory limit errors
- Permalink or .htaccess problems
- Maintenance mode stuck
Let’s fix each cause step by step.
2
Step 1: Check If the REST API Is Working
This instantly reveals if the block is API-related.
Open:
https://yourdomain.com/wp-json/
If you see structured data → REST API is working.
If you see an error, or blank page → the API is blocked.
Common API errors:
rest_no_routerest_cannot_access403 Forbidden401 Unauthorized500 Internal Server Error
3
Step 2: Fix Site URL & Home URL
Incorrect address = failed updates.
- Go to Settings → General
- Make sure these match exactly:
- WordPress Address (URL)
- Site Address (URL)
Example (correct):
https://yourdomain.com
Incorrect versions include:
- http instead of https
- www vs non-www mismatch
- Trailing slash mismatch
Fixing URLs solves most REST API issues.
4
Step 3: Disable Security Plugins Blocking REST API
Security plugins often block /wp-json/ calls.
Temporarily disable:
- Wordfence
- iThemes Security
- All In One Security (AIOS)
- Shield Security
- Limit Login Attempts
Then try updating a post again.
For Wordfence:
- Go to Wordfence → Firewall
- Set firewall to Learning Mode
For AIOS:
- Disable REST API rules
5
Step 4: Fix SSL / Mixed Content Issues
Editor fails when insecure HTTP resources load.
Install:
- Really Simple SSL
Or manually fix:
- Force HTTPS in hosting
- Replace all http:// URLs to https:// using Better Search Replace
- Clear cache
A mixed content error will block the saving process.
6
Step 5: Disable Caching & Optimization Plugins
JavaScript minification or caching blocks REST requests.
Disable these plugins temporarily:
- LiteSpeed Cache
- WP Rocket
- W3 Total Cache
- Asset CleanUp
- Hummingbird
- Autoptimize
Then test saving a post again.
JS minification or combining files frequently breaks the editor.
7
Step 6: Disable Cloudflare / CDN Blocks
CDN firewalls often block REST API requests.
If using Cloudflare:
- Turn off “Bot Fight Mode”
- Disable “Under Attack Mode”
- Set Security Level to Low
- Add a Page Rule to bypass /wp-admin/ and /wp-json/
Optional:
Turn off Cloudflare proxy (Grey Cloud) temporarily.
8
Step 7: Regenerate .htaccess File
Incorrect rewrite rules can block REST API routes.
Steps:
- Go to File Manager → public_html
- Rename .htaccess to .htaccess-old
- Go to WP Admin → Settings → Permalinks → Save
This generates a clean .htaccess file automatically.
9
Step 8: Increase WordPress Memory Limit
Low memory can break save/publish actions.
define( 'WP_MEMORY_LIMIT', '512M' );
define( 'WP_MAX_MEMORY_LIMIT', '512M' );
Then restart PHP from your hosting panel.
10
Step 9: Update Everything (Core, Theme, Plugins)
Old versions may not support REST API properly.
- Update WordPress core
- Update active theme
- Update all plugins
- Check for abandoned plugins
11
Step 10: Check Server Firewall & ModSecurity
Hosting firewall may block saving posts.
Ask your host to:
- Whitelist /wp-json/* routes
- Disable ModSecurity for admin temporarily
- Remove rate limits for REST API
- Check for 403 / 503 blocks
Want Error-Free WordPress Editing?
All SiteCrafted ready-made websites come fully optimized with proper REST API access, stable hosting, SSL setup, caching optimization, and security rules pre-configured.
