The WordPress editor reports “Updating failed” or “Publishing failed” because the response is not valid JSON.
You do not have to become a server administrator because one part of your website stopped cooperating. Start with the checks that stay inside WordPress. If the problem moves into hosting or server configuration, I will show you where the risk begins—and where it may make more sense to hand the headache to me.
Start with the checks inside WordPress
- Write down the exact action that produces the message: saving a post, editing a page, or updating a plugin.
- Go to Settings → Permalinks and click Save Changes once without changing the structure.
- Open Tools → Site Health and look for a REST API warning.
After each change, test the same action again. Change one thing at a time so you know what helped and what did not.
A good place to pause
When this leaves normal WordPress editing
A valid JSON error often means WordPress expected a clean response but received an error page, redirect, security block, or extra output instead. Once the basic permalink check fails, the problem usually leaves ordinary page editing and moves into WordPress configuration or the server response.
If you inherited the website, took over after parting ways with a developer, or normally use WordPress only to add photographs and text, you may have never opened cPanel before. That is normal, but if you are new to backend server configuration, you need to proceed with caution. This is where you can break your site.
You also do not need to end up with more damage than you bargained for just to solve one aggravating problem. The standard repair is $149.00 if you would rather hand it off.
If you are comfortable with backend server configurations, continue with the technical steps below.
Technical checks
- Confirm that the WordPress Address and Site Address use the correct domain and the same HTTPS format.
- Inspect the REST API request and response for redirects, PHP notices, HTML error pages, or blocked requests.
- Check security plugins, the hosting firewall, and rewrite rules for anything blocking /wp-json/ or admin requests.
- Review the PHP and server error logs at the exact time the save fails.
Proceed with caution
Do not paste random rewrite rules into .htaccess or disable every security layer at once. One wrong rule can take down more than the editor.
Test the repair without making a second problem
- Keep a note of the original setting or filename before you change it.
- Make one change, clear only the relevant cache, and repeat the exact test.
- Check both the public page and the WordPress dashboard.
- If the error changes, stop and record the new message before continuing.
You can hand this off
If these checks have taken you beyond the part of WordPress you normally use, you can stop. I can trace the cause, make the repair, test the site, and tell you what was changed without turning one problem into your new full-time job.