Updating failed. The response is not a valid JSON response.

This may be a plugin or theme conflict. Please attempt to disable all plugins, and switch to the default Twenty Twenty-One theme. If the problem goes away, enable them one by one to identify the source of the problem.

If you can install plugins, install Health Check. On the troubleshooting tab, you can click the button to disable all plugins and change the theme for you, while you’re still logged in, without affecting normal visitors to your site.

Hi James,

Thanks for your reply! I’ve tried that already. I also tried changing the permalinks, the SSL settings, restoring an old backup, asking my host for more memory and changing the theme. Nothing seems to be working!

Ok, please make sure that your browser is up to date: https://browsehappy.com/

If it is not, please try updating your browser or switching to a different browser.

If it is, please do these two things:

1. Try clearing your browser’s cache and cookies.

2. Try with all browser extensions or add-ons temporarily disabled.

Please let us know how each step goes for you, and which browser (and version of) you’re using if you’re still having trouble.

I’ve kept on trying it across three browsers and devices since it started happening. I’m using the latest version of Chrome, Safari and Vivaldi. I’ve also tried it on my iPhone WordPress app and I’m still getting the same error. And I also had a couple of other people (one from Beaverbuilder and one from IONOS) log into my site and they saw the same error on their computers.

Do you have the Gutenberg plugin installed and active?

If so, is there an improvement with it deactivated?

^ additionally switch to classic editor see if it can solve the issue

Thanks all! I have tried all of that too. I deactivated and deleted Gutenberg and saw no difference. Have tried the classic editor too. I fear it’s not something I’m going to solve…

Do you have any server-side security things enabled, like mod_security or a web application firewall?

If so, is there any change with those temporarily disabled?

I do see your xmlrpc.php file is blocked by something as well, which depending on how the block is done, could result in something like this.

I’m encountering this same issue. I have a new wordpress multisite installation. I’ve implemented all the tips, changed to default theme, deactivated plugins, updated browsers, still nothing.

Sorry I can’t be of much help. I tried everything. Went to everywhere involved in my site for help… WordPress, all plugin creators, my hosting, my site template, nothing anyone suggested ever helped. I read endless forums and found nothing, except a lot of people saying once this had happened to their website they never fixed it. Unless you hire a developer… I got fed up and couldn’t waste any more time on it so I moved my blog and website over to Squarespace instead ??

I’m fed up with this issue.

Updating failed. The response is not a valid JSON response.

Even trying all these possible solutions, the issue arises again and again.

https://webspeedtools.com/fix-the-response-is-not-a-valid-json-response-wordpress/

This is a problem with the Gutenberg editor, so switching to the Classic Editor is a temporary solution.

A waste-timer.

• This reply was modified 2 years, 11 months ago by ArtGoddess.

The solution is to Re-Install Windows apparently…….lol

z

What if you’re not using the Gutenberg editor?….

I’m in favor of going back to Worpress v4……that at least worked.

z

Well, I guess the gutenberg editor is installed by default…….I downloaded and activated the Classic Editor, and now everything is working.

Btw, this all started with a FORBIDDEN error …. and that happened after I was trying to update a page……that went into eternal spinning….lol….after I went back to the Dashboard, all hell had broken loose.

Anyway, I didn’t like the gutenberg/default editor anyway…..it would never keep my default font size……and if I pasted pre written text into the page, it created a freaking block for every sentence….lol

And every time you hit return, it created a new block…….sigh

Now I gotta go back and fix all the permissions……cause I made a bunch of them 777…..spent an hour on that forbidden crap. Finally deleted the .htaccess file.

z

• This reply was modified 2 years, 10 months ago by zardiw.