504 error caused by corrupted content

We previously had an issue with CloudFlare, where Elementor editor got a 403-error when saving. When debugging this, trying to save the page over and over again, it led to a situation, where the Elementor content for the page was possibly corrupted somehow.

After the CloudFlare-issue was resolved and saving in Elementor editor was working again, we noticed that we are getting a 504 error on the front page. All documentation points to issues on the server so we spend hours debugging it. Meanwhile all other pages were working just fine, also the ones built with Elementor. No error messages were logged in server logs anywhere.

I switched to home page to an empty page and it worked, that’s when I started thinking about a possibility of corrupted content. Not sure if it was in the actual Elementor content in the database or something in the page content, but when I restored an earlier version of the page in the WordPress editor, the front page started working.

So this problem is resolved, but I am writing this so others know that it is possible that a corrupted page content can result in a 504-error and all documentation points to server overload for various reasons and none of them mention corrupted content.

• This topic was modified 10 months, 3 weeks ago by Sivustonikkari.

The page I need help with: [log in to see the link]