HTTP500 after Install

  • Hello LC,

    Just installed LC and immediately received HTTP500. I’m on a Yahoo server. This same thing happened yesterday with the “WordPress Landing Pages” plugin.

    In wp-content/plugins renamed your plugin to live-composer-bad-load and was then able to get back into my WP without a 500.

    Think it’ll be ok to just leave the renamed plugin there? It’s no longer showing in the WP plugins list.

    Thank you,
    James

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author LiveComposer

    (@livecomposer)

    Hi James,
    Since you are getting the same 500 error with different plugins, it means that you have issues with server configuration. To find a reason we should check your server log files. These files available in your server admin panel.

    Our plugin installed on 20k+ servers. It’s not honest to rate it 1 star because of the problems on your server. Please, kindly change your rating and we will be happy to help you via our one to one support channel: https://livecomposerplugin.com/support/support-request/

    Thank you.

    Plugin Author LiveComposer

    (@livecomposer)

    James, I didn’t see you message on our support mailbox. Any chance to provide more details or change your rating?

    The reason for “500 Internal Server Error” is MOD SECURITY, meaning that it’s hosting related, nothing to do with LC..

    ModSecurity: Output filter: Response body too large (over limit of xxxxx, total not specified) – this is what’s causing plugin to freeze or end up with “500 Internal Server Error” or “404 Error” – you should contact your hosting tech support and ask them to increase the allowance via Apache config file or just disable MOD SECURITY until they sort it out for you.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘HTTP500 after Install’ is closed to new replies.