WordPress: Updating failed. You are probably offline.
The block editor’s save request to the REST API failed — network blip, REST API blocked, or the server returned an error/HTML.
Updating failed. You are probably offline.Publishing failed. You are probably offline.You are probably offline Meaning
The editor saves via /wp-json/. Security plugins, Cloudflare/WAF rules, REST disabled for some users, expired login or server errors show this generic message.
Common causes
- REST API blocked (security plugin, WAF, host)
- Login session expired
- Server error (500) during save
- Actual network interruption
⚡ Quick fix
- Check the Network tab for the failed /wp-json/ request and its response
- Test Site Health → REST API
- Whitelist /wp-json/ in security/WAF rules
Detailed fix by platform
Shell
curl -s https://example.com/wp-json/ | head -c 200
How to diagnose
- Request — Status and body of the failed save
- REST — Site Health status
- Session — Still logged in?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- Not a valid JSON response WordPress: Updating failed. The response is not a valid JSON response.
- rest_cookie_invalid_nonce WordPress REST API: {"code":"rest_cookie_invalid_nonce","message":"Cookie check failed"} (403)
- rest_forbidden WordPress REST API: {"code":"rest_forbidden","message":"Sorry, you are not allowed to do that."} (401/403)
Most viewed in WordPress
- Critical error WordPress: There Has Been a Critical Error on This Website
- Call to undefined function create_function() WordPress on PHP 8: Fatal error: Uncaught Error: Call to undefined function create_function() / each()
- Installation failed: Could not create directory WordPress: Installation failed: Could not create directory (plugin/theme install or update)
Other ways to find it
Where this error sits
Origin: Application & API. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 14 Oct 2026