Elementor doesn’t work

Hi, I hope we can help you get this working again. Of course, you can always roll back to the previous version if you need to by going to Elementor > Tools > Version Control and click the Rollback button.

But there are other things you can try as well. Check out the possible solutions at https://docs.elementor.com/article/184-cant-edit-with-elementor to see if they help.

Have you checked your Memory?
tiger721.com/frozen

The hosting said WP memory is 256MB

wp-config.php line is define(‘WP_MEMORY_LIMIT’, ‘512M’)

Would it be problem of “Litespeed”? The server uses Litespeed.

Litespeed shouldn’t be a problem. Did you go through each of the suggestions in the doc I shared? Did you switch the loader method? Did you deactivate all other plugins to check for a conflict?

Yes, I have already enabled loader method.
I have many plugins installed. Can’t disable all. Also, I didn’t install new plugins recently as I remember. I just moved to a new hosting server.

Hi everyone,

I’ve been almost the whole day trying everything you indicate here: https://docs.elementor.com/article/184-cant-edit-with-elementor
But it doesn’t work.

I am still having the same issue in different browsers and different computers:
“This webpage is not available… ERR_SPDY_PROTOCOL_ERROR”

Any ideas???

Here is my system status: https://pastebin.com/LyfAPRbw

Thanks in advance!

• This reply was modified 5 years, 10 months ago by jorgelomas.

I wonder if Elementor has any updated version of the plugin to solve the issue.

I got this error when trying to edit a page with Elementor.

post.php?post=4007&action=elementor:1 Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.
VM3891:5 Settings loaded…
intercept.js:1 Filter Running…
post.php?post=4007&action=elementor:1 Failed to load resource: the server responded with a status of 500 ()

@jorgelomas if you google “ERR_SPDY_PROTOCOL_ERROR” you’ll find some help for that problem. That’s generally a browser issue. But if you still have problems later, please start your own thread, so we can help you separately.

@wpbetsy I see you received a 500 error. That’s a general server error. There is a doc that might help at https://docs.elementor.com/article/300-500-error-while-using-elementor but it’s still fairly important that you follow all the possible debugging steps, including temporarily deactivating plugins. Luckily, just today, Elementor released a new version that includes a new feature called Safe Mode. Safe Mode automatically runs your site (just for you) with plugins deactivated. (Users still see the site with all plugins working). This makes it really easy to see what might be causing your issue. So update to the latest, and run your site in Safe Mode (for a short time, not forever) to see if that helps. Here’s more info on Safe Mode. https://docs.elementor.com/article/480-what-is-safe-mode

Just going to put my 2 cents in. I did a check across all my plugins and found the culprit to be the SG (SiteGround) Optimizer plugin. Ironic that is is supposed to speed up the site but actually renders Elementor dysfunctional.

Could be that it is a combination of too much memory being used – but this is also happening on my Laravel Valet local environment! I just updated to latest SG Optimizer version (5.0.12).

Haven’t dug down yet to find the actual cause of the issue. Anyways, I’m getting tired of using this plugin when there are so many better alternatives out there.

As I already replied to you, the Optimizer plugin works great with Elementor. It is something else. Plus, the SG Optimizer would not even work on your local environment throwing all sorts of errors. It is designed to work only on live SiteGround servers.

If you’re getting 502s, add this to your .htaccess file, that should do the trick:

<IfModule mod_substitute.c>
SubstituteMaxLineLength 10M
</IfModule>

• This reply was modified 5 years, 10 months ago by Hristo Pandjarov.

Thanks , roll back works , now I am able to do “Edit with elementor”

Same problem. Tried everything in this thread and nothing works. Just get “loading” and a white screen.

I figured it out. It was a problem with Debian packaging. I completely uninstalled all Debian wordpress packages and then installed WordPress 5.2 via the download tarball from www.ads-software.com. Everything works fine now. Not the first time the Debian packagers munged something up. Hopefully anyone else scuffling with wordpress under Debian will come across this post.

• This reply was modified 5 years, 6 months ago by nbi1.