[MeetioParticipant]

Hi guys,

Is there any way to disable that Cornerstone blurps out a cs_render_element request for each and every keydown when editing a page? It literally slows our web server down to a crawl (and then crashing entirely).

Here’s an log excerpt from nginx for a single administrator editing a page:

141.101.81.12 - - [14/Oct/2016:17:02:40 +0200] "POST /wp-admin/admin-ajax.php?action=cs_render_element HTTP/1.1" 200 2721 "https://getmeetio.com/sv/?cornerstone_preview=1" "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36"
141.101.81.12 - - [14/Oct/2016:17:02:41 +0200] "POST /wp-admin/admin-ajax.php?action=cs_render_element HTTP/1.1" 200 2724 "https://getmeetio.com/sv/?cornerstone_preview=1" "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36"
141.101.81.12 - - [14/Oct/2016:17:02:43 +0200] "POST /wp-admin/admin-ajax.php?action=cs_render_element HTTP/1.1" 200 2724 "https://getmeetio.com/sv/?cornerstone_preview=1" "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36"
141.101.81.12 - - [14/Oct/2016:17:02:44 +0200] "POST /wp-admin/admin-ajax.php?action=cs_render_element HTTP/1.1" 200 2723 "https://getmeetio.com/sv/?cornerstone_preview=1" "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36"
141.101.81.12 - - [14/Oct/2016:17:02:44 +0200] "POST /wp-admin/admin-ajax.php?action=cs_render_element HTTP/1.1" 200 2713 "https://getmeetio.com/sv/?cornerstone_preview=1" "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36"
141.101.81.12 - - [14/Oct/2016:17:02:45 +0200] "POST /wp-admin/admin-ajax.php?action=cs_render_element HTTP/1.1" 200 2716 "https://getmeetio.com/sv/?cornerstone_preview=1" "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36"
141.101.81.12 - - [14/Oct/2016:17:02:45 +0200] "POST /wp-admin/admin-ajax.php?action=cs_render_element HTTP/1.1" 200 2716 "https://getmeetio.com/sv/?cornerstone_preview=1" "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36"
141.101.81.12 - - [14/Oct/2016:17:02:46 +0200] "POST /wp-admin/admin-ajax.php?action=cs_render_element HTTP/1.1" 200 2715 "https://getmeetio.com/sv/?cornerstone_preview=1" "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36"
141.101.81.12 - - [14/Oct/2016:17:02:46 +0200] "POST /wp-admin/admin-ajax.php?action=cs_render_element HTTP/1.1" 200 2716 "https://getmeetio.com/sv/?cornerstone_preview=1" "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36"
141.101.81.12 - - [14/Oct/2016:17:02:47 +0200] "POST /wp-admin/admin-ajax.php?action=cs_render_element HTTP/1.1" 200 2721 "https://getmeetio.com/sv/?cornerstone_preview=1" "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36"
141.101.81.12 - - [14/Oct/2016:17:02:47 +0200] "POST /wp-admin/admin-ajax.php?action=cs_render_element HTTP/1.1" 200 2724 "https://getmeetio.com/sv/?cornerstone_preview=1" "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36"
141.101.81.12 - - [14/Oct/2016:17:02:48 +0200] "POST /wp-admin/admin-ajax.php?action=cs_render_element HTTP/1.1" 200 2724 "https://getmeetio.com/sv/?cornerstone_preview=1" "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36"
141.101.81.12 - - [14/Oct/2016:17:02:49 +0200] "POST /wp-admin/admin-ajax.php?action=cs_render_element HTTP/1.1" 200 2728 "https://getmeetio.com/sv/?cornerstone_preview=1" "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36"
141.101.81.12 - - [14/Oct/2016:17:02:49 +0200] "POST /wp-admin/admin-ajax.php?action=cs_render_element HTTP/1.1" 200 2728 "https://getmeetio.com/sv/?cornerstone_preview=1" "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36"
141.101.81.12 - - [14/Oct/2016:17:02:50 +0200] "POST /wp-admin/admin-ajax.php?action=cs_render_element HTTP/1.1" 200 2731 "https://getmeetio.com/sv/?cornerstone_preview=1" "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36"
141.101.81.12 - - [14/Oct/2016:17:02:51 +0200] "POST /wp-admin/admin-ajax.php?action=cs_render_element HTTP/1.1" 200 2735 "https://getmeetio.com/sv/?cornerstone_preview=1" "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36"
141.101.81.12 - - [14/Oct/2016:17:02:52 +0200] "POST /wp-admin/admin-ajax.php?action=cs_render_element HTTP/1.1" 200 2737 "https://getmeetio.com/sv/?cornerstone_preview=1" "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36"
141.101.81.12 - - [14/Oct/2016:17:02:54 +0200] "POST /wp-admin/admin-ajax.php?action=cs_render_element HTTP/1.1" 200 2742 "https://getmeetio.com/sv/?cornerstone_preview=1" "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36"

[RadModerator]

Hi there,

Thanks for writing in.

It’s probably related to text element or any element that uses WordPress Editor. And any change you add to them will automatically reflect in the preview window. For now, edit your text content in a text editor (eg. notepad) and paste its content to WP Editor without the need of typing.

Changes are meant to reflect ton the preview in real-time and that includes typing. We’re looking some other way to improve this, please stay tune.

Thanks!

[MeetioParticipant]

If this is correct it makes Cornerstone practically unusable? Why have it?

[RadModerator]

Hi there,

It’s usable, but some hosting provider limit each request especially if you’re on shared hosting. It’s triggered by every change and from the editor, any character change is considered a change. If hosting decided to limit your connection and blog it, then they will do it the same issue with visual composer. It triggers simultaneous connections upon load, the bigger the content, the most connections it will request.

If the builders are going to adapt to hosting’s connection limit, then it will not be as responsive as they are on dedicated hosting, loading is much slower. Though yes, it’s a good idea to have a timeout setting, like toggleable options where a user can switch on when they are on shared hosting. Noted that.

Thanks!

[MeetioParticipant]

Just to clarify, this happens only when using Cornerstone Pagebuilder, not when we use the standard WordPress editor or other pagebuilders.

We are not on a shared hosting, we have a dedicated machine for this which is setup per best practices for LEMP and WordPress. Please let us know what settings we need to do to make this work then as we have full control of the machine.

[RadModerator]

Hi there,

I’m not saying it has same issues with your other page builders. I’m just saying that it can happen to any builder with large contents that triggers connections. Example https://community.theme.co/forums/topic/visual-composer-causes-connection-lost-error/page/2/ that’s old and there are many.

Since you have full control of your machine, is there a way we can tell its connection limit? Or is there any restriction? If it’s really the case, then we should get the same issues on all sites regardless of hosting, but it’s rare.

Browsers have its own simultaneous connection limit, it’s 6 connections I think. Even it the plugin issues 20 connections, the browser will execute them 6 at a time avoiding the overload. That includes all types of request (eg. ajax, images, stylesheet, js files, and etc.), why would your hosting will allow 6 simultaneous connection and may have the total of hundreds, but it can’t allow consecutive connections that only happens to be once at a time (non-simultaneous). My guess is that your hosting has strict security rule and any consecutive connections fall under DDOS category.

Some hosting is able to whitelist specific requests, and since the popularity of visual composer, it becomes the norm making the connection issues on it a rare thing. Another example, once the security detects the presence of an iframe in the content, it will consider it XSS attack and block it even it’s not an attack.

There are many contributing factors and we’re willing to help, but we need to understand its nature first. Do you have any logs other than access logs above? Do you have any active security feature and where you’re hosted? But again, yes, there should be setting in cornerstone that limits consecutive connections even if that will make the builder slower.

Thanks!

[MeetioParticipant]

Hi,

We do not have any rate limiting on the site and we use a standard stack on Ubuntu 16.04.1 running nginx 1.10.0 with php 7.0.8 and mysql 5.7.13.

What logs would you need?

[RadModerator]

Hi there,

Not sure, I just assume that there maybe some logs from security logs if you have. And you may check these http://nginx.org/en/docs/http/ngx_http_limit_conn_module.html and http://serverfault.com/questions/652180/nginx-10k-concurrent-connections

Thanks.

[MeetioParticipant]

Hi,

We do not use the http_limit_conn module, and I’ve just activated microcaching but it only speeds up subsequent identical requests, not the actual editing of a page nor the initial load when the page isn’t in the microcache.

Here is a recent log attached.

[RadModerator]

Hi there,

The access log is okay, intervals are just about 1 – 4 seconds. And I can’t provide more information or recommendation since I’m not sure how your hosting works. Though, I’ll note this for further investigation, for now, please minimize editing through text editor.

Thanks!

[MeetioParticipant]

That is really disappointing, one of the main reason to choosing X theme was the page builder.

[RahulModerator]

We are really sorry to hear that.

We’ve forwarded this request for further investigation and it’s being reviewed. Hopefully, it will be resolved in the next update. Stay tuned for the same.

Thanks for your patience!

[Author]

Posts