You write a post, hit Publish, and the block editor throws back “Updating failed” or “Publishing failed.” Your work seems stuck. It’s a frustrating error, but it almost always comes down to the editor being unable to reach the WordPress REST API, and that has a short list of fixable causes.
What’s actually happening
The modern block editor saves your content by talking to the WordPress REST API in the background. When that connection is blocked or failing, the editor can’t save, and you get the “failed” message. So the fix is restoring that connection. Here’s how to track down what’s blocking it.
Check your internet connection first
The simplest cause: your connection dropped mid-edit. If your Wi-Fi hiccupped, the save fails. Confirm you’re online, then try again. It sounds obvious, but it’s genuinely a common cause, especially on unstable connections.
Rule out a security plugin blocking the REST API
The most frequent culprit is a security plugin that blocks or restricts access to the REST API as a hardening measure — inadvertently blocking the editor too. Temporarily deactivate your security plugin and try saving. If it works, look for a setting to allow REST API access for logged-in users rather than disabling the plugin entirely.
Check for other plugin conflicts
Beyond security plugins, other plugins can interfere with the REST API or the editor’s scripts. Deactivate your plugins (rename the plugins folder in File Manager if you can’t reach the dashboard) and test. Reactivate them one at a time to find the offender.
Test the REST API directly
WordPress’s Site Health tool (under Tools) runs a check on the REST API and flags if it’s unreachable. If Site Health reports a REST API problem, that confirms the diagnosis and points you toward the cause — often a plugin or a server rule.
Look at .htaccess and security rules
Occasionally a rule in .htaccess or a server-level security setting blocks the REST API’s URL. If the API is being blocked at the server level, that’s something we can check and adjust. Regenerating a clean .htaccess (by re-saving permalinks) is a good first step.
Try the classic editor as a workaround
If you need to publish urgently while you troubleshoot, the classic editor doesn’t rely on the REST API in the same way. A classic-editor plugin gives you a temporary route to save your work while you sort out the underlying cause.
Don’t lose your draft
Before doing anything drastic, copy your post content somewhere safe so a failed save doesn’t lose your work. Then troubleshoot with peace of mind. If the REST API turns out to be blocked at the server level, send us a ticket and we’ll clear the path.
