• Resolved shayeryan

    (@shayeryan)


    Hello, awesome plugin! I use on several of my sites and has stopped many brute force attacks!

    I’m getting this 500 internal error after activating my root folder. These are the steps I’m taking:

    • Clicking create default.access file magic button
    • Activating Root Folder

    I have tried both the fixes found here that say to comment out #Options -Indexes and #DirectoryIndex index.php index.html /index.php

    The other thing is, that it is working with other sites that are hosted in the same place, Bluehost. It has also been working on my site for many months. I was troubleshooting an issue with a caching plugin and ended up having to start with a fresh .htaccess file. I’ve tried activating the default.access file with a completely blank .htaccess file and still getting this error.

    Any help would be greatly appreciated!

    -Shaye

    https://www.ads-software.com/plugins/bulletproof-security/

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

    (@aitpro)

    This may actually be a problem with your caching plugin since a 500 error is a fairly common error with caching plugins.

    Do these troubleshooting steps in this order:
    1. Delete your root htaccess file.
    2. Check your wp-config.php file for any Cache Constant code and comment it out temporarily.
    3. Login to your site and deactivate your caching plugin.
    4. Go to BPS Custom Code page and cut (not copy) all of your custom code out of all BPS Custom Code text boxes and save it in a Notepad text file on your computer.
    5. Go to the BPS Security Modes page and click the Create secure.htaccess File (not Create default.htaccess File) AutoMagic button and activate Root folder BulletProof Mode.

    If everything is working at this point then activate your caching plugin and check your wp-config.php file to see if the Cache Constant code is still commented out. If it is then uncomment it. Then proceed to setup the cache plugin normally. ie add that plugin’s htaccess cache code to BPS Custom Code.

    Then start adding your custom htaccess code text box by text box to see if you have bad/invalid custom htaccess code somewhere.

    Thread Starter shayeryan

    (@shayeryan)

    Okay that worked, cheers!

    I guess I was hitting default.htaccess File instead of secure.htaccess. I’m pretty sure the notice at the top of WP says to hit default.htaccess File then root folder. I guess that’s what threw me off, thanks again for an amazing plugin and quick support!

    Regards,
    Shaye

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘500 internal server error after activating root folder’ is closed to new replies.