Staff replied SP Page Builder Joomla 6 v6.10

Request failed with status code 413 when saving existing SP Page Builder pages

Asked by Sascha Siemann-Pohl 1 week ago Last activity 2 days ago

Hello SP Page Builder Team,

I am running the latest Joomla version and the latest SP Page Builder version.
Since today around noon, I have been experiencing an issue when trying to save changes to existing SP Page Builder pages.

Backend behavior:
Open an existing SP Page Builder page.
Make any change, even a very small one.
Click Save.
The following error is displayed:
Request failed with status code 413
The changes are not saved.

Frontend behavior:
No error message is displayed.
The save/loading icon keeps spinning indefinitely.
The save process never completes.
The changes are not saved.

An important detail is that the issue only affects existing pages that were originally created with the previous SP Page Builder version. Newly created pages can be edited and saved without any problems.
Because of this, I suspect the issue may be related to content or data structures generated by the previous SP Page Builder version and how they are handled after the update.

Has anyone experienced a similar issue or knows of a possible solution?
Thank you in advance for your help.
Best regards,
Sascha

12 replies

Michael

6 days ago

I have the same problem

Oliver

6 days ago

Same with me. I also cant upload images.

Michael

6 days ago · edited

Debug showed that the content-length of my affected page is 296550 Bytes. This is not realy that much. My Joomla is hosted at Strato. There is no expicit content length limit in my hosting package.

Update: I copyed the page and deleted segments until the content-length is only 132060 Bytes than I can save the Page.

Any help is appreciated!

Oliver

5 days ago

The same worked for me. Also strato

Atick Eashrak Shuvo Staff

5 days ago

Hi there!

Thank you for bringing this to our attention, and I sincerely apologize for the inconvenience caused.

To assist you more effectively, may I kindly request temporary administrative access to your site? This will allow me to thoroughly investigate and resolve the issue for you.

Before sharing the credentials, I strongly recommend taking a complete backup of your site to ensure all data remains secure.

Looking forward to your response.

Best regards

Sascha Siemann-Pohl Asked this

5 days ago

Hello,

Thank you for your reply and your offer to investigate the issue.

I would be happy to provide temporary administrator access. However, I cannot find an option to send private messages on this forum.

Could you please let me know the best and most secure way to share the login credentials with you?

Thank you for your assistance. I look forward to your response.

Best regards,
Sascha

Atick Eashrak Shuvo Staff

5 days ago

Hello Sascha,

Thank you for your response.

You can securely share the temporary administrator login credentials using the hidden content area in your forum post. Please refer to the following screenshots to locate and use this feature:

Any information shared in this area will only be visible to the original post author and our support agents, ensuring that your credentials remain private from other forum users.

Once you have shared the credentials, we will investigate the issue and get back to you with our findings.

Thank you for your cooperation.

Best regards

Sascha Siemann-Pohl Asked this

5 days ago

Hello,

Thank you for your willingness to investigate the issue.

I have created a temporary administrator account for you:

The issue appears on several SP Page Builder pages, for example:

Home
Mitglied werden

Please let me know if you need any additional information or if you encounter any problems accessing the site.

Thank you for your support.

Best regards,
Sascha

Atick Eashrak Shuvo Staff

5 days ago

It seems your website may have a country-based access restriction, as I’m unable to log in from my end. Could you please check whether any geographic restrictions or IP-based access rules are preventing access from my location?

Sascha Siemann-Pohl Asked this

5 days ago

Thank you for the information.

I checked the Joomla configuration, .htaccess file, and STRATO security settings. No country-based restrictions or IP filtering rules are configured.

Could you please send me:

a screenshot of the error page
the exact error message
the HTTP status code (403, 404, 500, timeout, etc.)

This will help identify where the connection is being blocked.

Atick Eashrak Shuvo Staff

5 days ago

The login page loads correctly, but after I enter my credentials and submit the login form, the website downloads an index.php file instead of logging me into the control panel. Could you please investigate this issue? The php file code is below

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html><head>
<title>503 Service Unavailable</title>
</head><body>
<h1>Service Unavailable</h1>
<p>The server is temporarily unable to service your
request due to maintenance downtime or capacity
problems. Please try again later.</p>
</body></html>

Sascha Siemann-Pohl Asked this

5 days ago

Hello,

Thank you for your feedback and for providing the error details.

I have investigated the issue on my side. I tested the same administrator account and was able to log in successfully without any problems. The Joomla backend is working correctly, and the credentials you received are valid.

I have also checked:

Joomla configuration
.htaccess rules
STRATO security settings
SiteLock and SiteGuard settings

I could not find any country-based or IP-based restrictions.

To further investigate the issue, I have contacted STRATO hosting support and provided them with your IP address (119.148.4.217) and the details of the HTTP 503 error you are receiving after login. I am currently waiting for their response.

I will keep you updated as soon as I receive additional information from the hosting provider.

Thank you for your patience.

Best regards,
Sascha

Atick Eashrak Shuvo Staff

4 days ago

I was able to log in successfully using a VPN. Could you please let me know the name of the page where you’re experiencing the issue so I can investigate it further?

Sascha Siemann-Pohl Asked this

4 days ago

Hello,

Thank you for your update.

The pages where the issue occurs consistently are:

Home (ID: 33)
Mitglied werden / Become a Member (ID: 4)

Additionally, I observed similar behavior on:

Trainingsort / Training Location (ID: 16)
Trainingszeiten / Training Schedule (ID: 15)

However, for pages 15 and 16, the issue only occurs after I add several additional rows of content. With the current amount of content, both pages work correctly. When I previously added more rows, the same problem reappeared.

For pages 33 and 4, the problem occurs immediately.

It seems the issue may be related to the amount or structure of the content being processed on these pages.

Please let me know if you need any additional information or access for further testing.

Best regards,
Sascha

Daniel

4 days ago

Hello JoomShaper Team,

I'm experiencing a very similar issue on our website https://handelsloewen.de, hosted by STRATO.

Since updating SP Page Builder (6.9.1 Pro) on September 30, 2026, none of our existing pages can be saved anymore. The saving icon keeps spinning indefinitely. An update to 6.10 is actually not possible: 403 Forbidden request

Chrome Developer Tools show an HTTP 400 Bad Request response for the SP Page Builder save request.

Newly created pages can be saved without any issues. Only pages created before the update are affected.

The issue also occurs in incognito mode.

Could you please investigate whether this is related to the latest SP Page Builder update or a compatibility issue with STRATO hosting?

Rebuilding all existing pages is not a reasonable solution. We need to be able to edit our existing website.

Thank you!

Atick Eashrak Shuvo Staff

4 days ago

We apologize for the inconvenience.

Please contact your hosting provider and ask them to check the following server configuration values to ensure they meet the requirements:

SecRequestBodyLimit: At least 25 MB
SecRequestBodyNoFilesLimit: At least 25 MB
LimitRequestBody (Apache/LiteSpeed): At least 20 MB

These are among the server requirements for SP Page Builder. You can find the complete list in our SP Page Builder Technical Requirements documentation.

If these values are configured correctly and the issue persists, please let us know so we can investigate further and assist you.

Sascha Siemann-Pohl Asked this

3 days ago

Hello,

I would like to provide an update.

I changed the PHP version on my hosting account from PHP 8.4 to PHP 8.3. After doing so, the affected pages could be edited and saved successfully again.

It appears that the issue may be related to PHP 8.4 compatibility rather than the server request limits.

Could you please confirm whether SP Page Builder 6.9.1 is fully compatible with PHP 8.4?

Thank you.

Best regards,
Sascha

Atick Eashrak Shuvo Staff

3 days ago

Hello Sascha,

Thank you for the update and for sharing your findings.

We understand your concern regarding PHP 8.4 compatibility. However, the HTTP 413 (Content Too Large) error generally indicates that the web server or a security module is rejecting a request because its body exceeds the configured size limit. This typically occurs before the request reaches the PHP application for processing, so it is generally related to server-side request limits rather than PHP version compatibility.

The following server configuration values are important because they determine how much request data the server allows:

SecRequestBodyLimit: Controls the maximum request body size processed by ModSecurity.
SecRequestBodyNoFilesLimit: Controls the maximum size of the request body excluding file contents.
LimitRequestBody (Apache/LiteSpeed): Limits the overall size of the HTTP request body.

SP Page Builder may send a substantial amount of data when saving complex pages. If these limits are too low, the server may reject the request and return a 413 error before the changes can be saved. This is why we recommend checking these values against the SP Page Builder Technical Requirements.

Although switching from PHP 8.4 to PHP 8.3 resolved the issue in your case, this alone does not confirm that the root cause was PHP compatibility. The change may have affected the server configuration or request-processing environment. Further investigation would be needed to establish the exact cause.

Regarding PHP 8.4 compatibility, we recommend first verifying the server request limits and checking the server error logs to identify why the request was rejected. If the issue persists with the required limits correctly configured, please share the relevant server logs and details of the affected page so we can investigate further.

Thank you for your understanding and cooperation.

Best regards

Daniel

2 days ago

Hello JoomShaper Support,

I have investigated the issue further using Chrome Developer Tools and found some important details.

1. Successful save request:

Endpoint: task=page.savePage
HTTP status: 200 OK
Content-Length: 42,353 bytes
Server: Apache 2.4.68
Page with 3 content blocks

2. Failed save request (new page with duplicated block):

Endpoint: task=page.savePage
HTTP status: 400 Bad Request
Content-Length: 51,717 bytes
Server: Apache 2.4.69
I simply duplicated an existing working block on the new page.

--> This confirms that even newly created pages stop saving when more content is added.

Failed save request (large existing page):

Endpoint: task=page.savePage
HTTP status: 400 Bad Request
Content-Length: 314,171 bytes
Server: Apache 2.4.69

--> This confirms that larger existing pages are also affected.

All requests are significantly smaller than the recommended 20–25 MB server limits.

The HTTP 400 response is a generic Apache "Bad Request" HTML page, rather than a normal SP Page Builder error response.

I also noticed that the successful request was handled by Apache 2.4.68, while the failed requests were handled by Apache 2.4.69. Could this indicate different server configurations?

Our hosting provider STRATO has been unable to confirm the actual server request limits or investigate the issue further.

Additionally, attempting to update SP Page Builder Pro using a downloaded ZIP file through Joomla results in HTTP 403 Forbidden.

Could you please investigate whether this is related to an Apache/ModSecurity restriction, a server configuration issue, or a compatibility problem introduced by the recent SP Page Builder update?

Unfortunately, I cannot attach screenshots in this support ticket, but I can provide additional technical details if needed.

Thank you for your assistance!

Atick Eashrak Shuvo Staff

2 days ago

Please create a new forum regarding your issue.