Plugin causing “HTTP ERROR 500”

  • Resolved startechmarketing

    (@startechmarketing)


    1 year, 3 months ago

    We are moving the websites to webgo managed SSD vServer

    When I enable Wordfence plugin, or with Wordfence disabled and bulletproof security enabled I get http 500 server errror, I cant access front or back end

    I was able with Bulletproof security activated (but not their .htaccess file) to select delete settings on uninstall

    With your plugin I can’t go to settings and do that.

    Checking other cases, I tried in user.ini the correct path to the wordfence-waf.php file, I also deleted the entry in the user.ini file and deleted the wordfence-waf.php

    But I still get 500 server error, I have to manually in ftp move or delete wordfence plugin folder and files.

    I also get the same behavior with Bulletproof security, and only way to get rid of 500 server error is to delete the directories.

    I mention both plugins because may is something I need required in my server config ?

    Below is my user.ini file I appreciate your help to get this fixed 

    allow_url_fopen = Off
file_uploads = On
max_execution_time = 200
max_input_time = 300
max_input_vars = 1000
memory_limit = 512M
post_max_size = 128M
upload_max_filesize = 256M

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author AITpro

    (@aitpro)

    I checked the description for webgo Managed SSD vServer on the webgo website and it is fully managed, which means webgo has created customized security for your hosting account. What I have seen with other hosts that offer a managed hosting solution is they restrict access to particular folders, create their own customized security solutions, etc. You will need to check with webgo to find out the limitations/restrictions for your managed hosting account.

    • This reply was modified 1 year, 3 months ago by AITpro.
    Thread Starter startechmarketing

    (@startechmarketing)

    Thanks .. I have checked with them, they did not know. I can email what you told me.

    However I did get it to work for now. I deleted all custom code after manually deleting tables and reactivating

    now seems to work we see how long

    Plugin Author AITpro

    (@aitpro)

    Glad to hear that. So yeah some .htaccess code must have been causing the 500 error then.

    Plugin Author AITpro

    (@aitpro)

    Marking as resolved.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Plugin causing “HTTP ERROR 500”’ is closed to new replies.