X/Cornerstone causing conflict with WP Bakery, ERR_CONNECTION_CLOSED on page update

Support
#1

Hello,

I previously posted about some Cornerstone errors I was seeing in my error log (this topic: Cornerstone errors in error log). I have some more details but I don’t think it falls under the same category so I am posting a new topic.

I built my website with no problem, but now suddenly I am experiencing the error ERR_CONNECTION_CLOSED when I try to update certain pages. Some pages work, others don’t. When the update fails, my changes are lost.

I am using WP Bakery page builder, which I enabled from the X extensions menu. I have been using X together with WP Bakery on over 15 sites for about 5 years and never had a problem until now.

I tested my site in troubleshooting mode and I discovered that if I keep WP Bakery active and change to the Twenty Twenty theme, I am able to update the pages. I can also update the pages if I disable WP Bakery and keep X active. However of course, with either of these options I lose the formatting on my pages since both are necessary for how the pages were built.

Since there is no problem with WP Bakery when I disable X, I do not think it is a problem with the plugin, but instead some conflict with X/Cornerstone. I don’t know why I would be having this conflict on only one website, when I have several other websites with the same combination that work fine.

Do you know how I might be able to resolve this?

Thank you!

#2

Hello @carlyas,

Thanks for the very detailed post information. I have logged in and investigated your issue. Upon saving the SESSIONS page, I encountered the same error message and hen I checked the console, I got this:

POST https://...../wp-admin/admin-ajax.php net::ERR_CONNECTION_CLOSED

In most case, your hosting provider may have a security rule that was limiting the access to admin-ajax.php. Some security or firewall software on the server (like mod_security) is configured too strictly. For example, it might not like that there are so many URLs in the HTTP request to save the table, and it might (erroneously) think that this is a spamming attack. Then, it blocks the save request and returns the error.

Can you please contact your hosting provider? They should be able to find out more about this error in their server log files. Then, they can relax the configuration of the software.

Please let us know how it goes.

#3

Thank you! I will send them that information.

#4

Hi @carlyas,

You are welcome, please let us know the feedback.

Thanks

#5

Hi again,

I spoke with my hosting company (GoDaddy), they were not able to give me specifics on that setting because they said the security for a shared server cannot be changed. We upgraded to have dedicated resources which they claimed already have a bit more lenient security settings, and we have not experienced the problem again so far. So I didn’t get a specific answer from them if this was the issue, but it definitely seems possible. Thanks again!

#6

@carlyas,

We are glad that you are able to fix your issue.

Thank you.

#7

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.