Hello,

Thanks for reaching out to us. Could you please share temporary administrator access to your Joomla backend? You can provide the credentials securely in the hidden content section. Also, please take a full backup of your site before we make any changes.

Once I have access, I’ll investigate further and see what’s causing the issue. Let me know once you’ve shared the details!

Best regards,

I am sending approaches.

Best regards, Milan

Hello,

I apologize for the delay in getting back to you and working on your issues.

Could you please re-check the provided credentials? It seems that the login details are not working on our end.

Once you update the credentials, please let us know, and we'll continue investigating the issue.

Thank you!

Hello,

cannot edit homepage, yesterday I tried to solve it with ChatGPT and I am sending info.

Best regards Milan

After investigating the issue, I found the following:

• The problem occurs only on one hosting provider. The same Joomla installation, database and SP Page Builder version work correctly on another server.
• The Contact page can be saved successfully.
• The Home page cannot be saved.
• The Home page JSON stored in the database is approximately 57 KB, so the request is not unusually large.
• When saving the page, SP Page Builder sends an AJAX request to:

index.php?option=com_sppagebuilder&task=page.savePage&id=202

• The request is sent correctly from the browser, but the server immediately responds with:

HTTP/1.1 400 Bad Request

• The response is the default Apache error page:

<title>400 Bad Request</title>
<h1>Bad Request</h1>
Your browser sent a request that this server could not understand.
Apache/2.4.67 (Debian)

• The request is rejected after approximately 50 ms, before Joomla or PHP can process it.
• There are no Joomla or PHP error messages because the request never reaches the application.

From my investigation, it appears that the request is being rejected by Apache, ModSecurity, or another Web Application Firewall (WAF) rather than by SP Page Builder itself.

Could there be anything in the JSON generated by SP Page Builder that is known to trigger Apache or ModSecurity to return HTTP 400 Bad Request?

Hi,

Could you please upload the Akeeba Backup ZIP file to Google Drive and share the download link with me?

Thank you!

Hello,

I had a technician check the web server logs. The error code 400 (Bad Request) occurs due to a violation of the ModSecurity web application firewall rule that they use on the servers. The REQUEST-200-ERRORS rule was violated, where the request body is analyzed. This rule has been deactivated for the subcarpathia.cz domain and saving is now working.

Best regards, Milan