Wordpress LScache Plugin: 500 Error with Elementor
Last Updated on: Wed, 15 Apr 2026 00:00:02 Hello, When I install and activate your plugin on a website Im working on for a client it seems ok. However, when I try to edit any of the pages built with Elementor and open the Elementor page builder it generates a 500 error. Once I deactivate your plugin I can access the Elementor editor as usual. What could be causing this issue? Alex Morgan Hi @tinybluerocket, please try to turn off ESI function on LiteSpeed Plugin, you can find it on ESI tab on setting page. Hello, ESI was off already and this issue is still occurring. Ive not adjusted any of the settings that come from the installation of the plugin, so its the basic setup thats causing this issue. Alex Hi @tinybluerocket, may I confirm is it related to this plugin? https://wordpress.org/plugins/elementor/ Does the bug occur on every theme or specific theme? Yes it is related to Elementor. When I try to use the Elementor page builder I get a 500 error when your plugin is activate. I dont when the plugin is deactivated. It occurs with any theme installed. Hi, Ive tried with few WP default themes but did not see 500 error. 1. could you please try reset LSCWP to default and see how it goes? 2. could you please tell me the exact step how you trigger it ? Best regards, Hello, Ive tried to reset the plugin, but that makes no difference. Ive created a video to show you the problem I am facing: https://youtu.be/553m959zgGg Thanks. Alex Hi @tinybluerocket, thanks for the update, but the youtube video is unavailable, can you upload it again? Sorry. I made the video private rather than unlisted. Heres the link now: https://youtu.be/553m959zgGg I have solved this issue by significantly increasing the wp-config set_time_limit and wp_memory_limit. I have that problem to. Can you tell how much did you increas does limits? Hi. Follow the instructions here: https://premiumaddons.com/docs/im-getting-a-blank-page-on-elementor-after-activating-premium-add-ons/
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference