• Resolved cmaddux

    (@cmaddux)


    I was using Wordfence, but I’m redesigning my entire website under a staging website, and Envato Elements isn’t working due to Wordfence. I spoke to my hosting who said they can’t delete the Wordfence file because it creates an HTTP Error 500 on the website, which results in me having absolutely no access to the site, front end or back end. How can I go about removing the file safely?

Viewing 1 replies (of 1 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @cmaddux,

    Before moving Wordfence to a staging site, many people will disable Wordfence (if the site won’t be visible the outside world to prevent failing scans and updates) or just remove Extended Protection like they would during a migration.

    Extended Protection being left enabled is normally the cause of 500 errors when a site is moved because auto_prepend_file in .htaccess or .user.ini points to the precise path of wordfence-waf.php. This isn’t ever likely to be the same elsewhere as it is on your live site, and removing wordfence-waf.php won’t solve the issue as this line of code will still be looking for it.

    Removing the auto_prepend_file reference to wordfence-waf.php in your .htaccess/.user.ini should cause the 500 errors to go away.

    Thanks,
    Peter.

Viewing 1 replies (of 1 total)
  • The topic ‘Wordfence Interferring with Envato Elements’ is closed to new replies.