XSS attack – Go Daddy Firewall

Hello, would you be able to inspect what the network tab says in your browser’s developer tools? An “Update Failed” message can mean a number of things, and the network tab can provide some insights on to why this is happening.

Not sure why GoDaddy is detecting it as an XSS attach though. There shouldn’t be any much difference in terms of saving whether your page contains Stackable blocks or not. Does the issue appear if there are no Stackable blocks

Please see the bottom of this entry in our docs for more info on how to check the network tab: https://docs.wpstackable.com/troubleshooting/common-issues/im-getting-the-error-updating-failed.-the-response-is-not-a-valid-json-response

Hi Benjamin, Thank you so much for your response. I had our website contractor look into it and this is what he said:

This is most definitely a server issue from what I can see. I read through the article at https://wpstackable.com/blog/how-to-fix-the-block-editor-error-updating-failed-error-message-the-response-is-not-a-valid-json-response/ and knew pretty easily that none of those options would cause the issue you’re getting on your site. Which lead me to their last point for “if none of the other solutions work”. So I opened the page, and added a Stackable block to the page and opened up the inspector as they suggested. Everything looked good until I hit publish, which is when the following 403 error does occur:

Upon clicking the error note it brings up the exact cause which is something to do with GoDaddy. The firewall is blocking it as a XSS attack.

From the screenshot he sent, looks like it says XSS014 on the GoDaddy error note. He suggested I reach out to you all first since you probably have tons of people on GoDaddy to see if you had heard of this issue before or knew what we need to tell GoDaddy.

I’ve never seen the issue appear on a page that doesn’t have a Stackable block. And it’s not always. At first, I thought the issue was only with accordion folders but then it did it with the buttons too. I thought maybe it was with newly created pages vs updated existing pages, but I couldn’t find a pattern there either. We did migrate our server earlier this spring, and I think that’s when I began noticing this issue.

Thank you!

Thanks for the clarification. We haven’t encountered this before for GoDaddy.

However, since you’re getting a 403 error, perhaps it’s a software-firewall doing the blocking. Are you by any chance using WordFence? Or maybe a similar plugin that provides website protection? If you are, then you might have to whitelist the action you’re performing, or put your firewall to “learning mode” then edit your pages again.

Let me know if that helps. If it doesn’t, then we can help dig deeper into this if we can log into the site just to check things out. For this you’ll have to contact us directly via [email protected]