NO BUG: ModSecurity causes long builder save time

Browser: Arc 1.46
OS: macOS
URL: in dev

As requested in this thread (SOLVED: Very slow saving behavior), I’m starting a new thread as follows:

I just wanted to add that I am still experiencing this on my sites, using Bricks 1.9.9. I switched off ModSecurity in cPanel and things loaded very quickly. When ModSecurity is switched on, it can take 15 - 20 seconds for the page to save. It doesn’t appear to be triggering any rule blocks, but there must be something in there, and I’m not sure where to look. I’ve checked for error logs, I’ve checked the ModSecurity Tools Hits List and no blocks there.

@charaf, you’ve asked for admin access to the dev environment - do you need Wordpress Admin access, or do you need cPanel access?

Hey ! I initially started the other thread.

Just jumping in to say that I don’t get these slow saving times since end of last year when I reported it. I am not sure why, how… ModSec is on again now for these projects, and when I have to intervene in the builder, the saving times are normal 2-3 seconds.

Can’t say why, sorry. So just to mention that the issue might be somewhere else (hosting ?).

Hi @jkbweb,

Thank you for creating a new thread!

If ModSecurity is causing this issue, it might be related to a specific configuration (unlike the more general issue discussed in @AnLip’s original thread).

We’ll need access to the WordPress site as well as SSH or cPanel access to debug the issue. You can share these access details via help@bricksbuilder.io, including a link to this forum thread for reference.

It would also be helpful if other users experiencing the same issue could share their access details so we can compare configurations and identify common factors.

1 Like

Hi @jkbweb,

We have received further insights from another user and their hosting provider regarding the issue. It turns out that the problem is related to ModSecurity directives, specifically: SecRequestBodyLimit, SecRequestBodyNoFilesLimit, and SecRequestBodyLimit. They were able to resolve the issue by increasing these variables.

We recommend reviewing and adjusting these directives on your server to see if it resolves the issue.

1 Like

Thank you very much, I will look into this further and get back to you if it fixes things.

1 Like