I get error 413 when saving changes in the frontend editor - Forum | JoomShaper
Awaiting an answer SP Page Builder Joomla 6 v6.10.0

I get error 413 when saving changes in the frontend editor

Asked by MasterMatrix 6 days ago Last activity 1 day ago

I am using Joomla 6.2.0 with Helix Ultimate and SP Page Builder 6.10.0. I have built about 20 sites using this setup.

Today, I encountered this issue for the second time: I can no longer save changes after editing in the frontend. After I click Save, the loading icon spins for a long time, then I get the error: "Request failed with status code 413."

I expect my changes to save successfully. How can I fix this?

9 replies

Atick Eashrak Shuvo Staff

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

MasterMatrix Asked this

Hi there, and thank you for the quick response; I have just provided the access credentials in a hidden format.
Regards,
Lorenzo

Atick Eashrak Shuvo Staff

Could you please share your server access?

MasterMatrix Asked this

Hello Atick, I’m afraid this might be difficult: all the websites are hosted by the German company Strato AG, and I only have customer-administrator access to them.
What exactly is required? Perhaps there’s something I can do to help?

Atick Eashrak Shuvo Staff

Hello,

Thank you for the clarification.

The issue appears to be server-related, so I need to investigate the server configuration and identify what is causing the problem. If you could provide FTP access to the website, that would also be helpful, as it would allow me to inspect the relevant files and investigate the issue further.

Thank you for your cooperation.

MasterMatrix Asked this

OK, thanks a lot—we can get that sorted.
I have provided the access credentials.

Atick Eashrak Shuvo Staff

Hi There,

We've looked into the problem you're having when saving your page, and we
wanted to reassure you first: this is not a fault in your website or in SP
Page Builder. It's a security setting on your hosting server that needs a small
adjustment.

What's happening:
When you save a page, its content is sent to the server in one request. Your
server's security firewall (ModSecurity) limits how many individual items a
single request may contain, and your larger pages are above that limit. So the
firewall blocks the save before it reaches your website, which is why you see
an error such as "Bad Request" or the save simply not completing.

This only affects larger, content-rich pages, and it is purely a server
configuration limit.

What needs to be done:
This has to be adjusted by your hosting provider. Please contact your hosting
provider's support team and forward the request below (or let us know and, with
your permission, we can contact them on your behalf):


Saving pages in SP Page Builder is being blocked by ModSecurity with a "400 Bad
Request". The save request contains a large number of arguments (several
thousand, and over twenty thousand for bigger pages), which exceeds
ModSecurity's "SecArgumentsLimit". Please raise SecArgumentsLimit to at least
50000 for our site, or whitelist the ModSecurity rule for POST requests to:
/index.php?option=com_sppagebuilder&task=page.savePage
Note: this is not PHP's max_input_vars (the request body is JSON, which that
setting does not apply to); it is ModSecurity's argument limit.

Once your hosting provider has made this change, please try saving your page
again. If the problem is still there after the change, let us know and we will
investigate further.

Best regards

MasterMatrix Asked this

Thank you for your support and for verifying the error!
I have just forwarded the issue to the provider, and I will definitely provide an update here.
In the meantime, all of the websites I host with Strato AG have been affected.

MasterMatrix Asked this

I would like to say thank you once again:

I passed the information on to the service provider—on behalf of several other clients who had all encountered the same issue. The response was:

"...We recommend that you contact the developer, Joomshaper, to see if the memory requests made by SP Page Builder can be adjusted or optimized..."

Strangely enough, saving is now working again on all of my clients' websites—just one day after I submitted my written complaint.

In any case, you can now close the ticket, and I hope that the error was only temporary.

Log in to reply.