• Hello, I just installed WP all in one last night, and set it up according to a web video done by Vinny O’Hare. I only changed settings that he recommended, and none of these were in any of the “advanced” settings.

    This morning when I got up, my site was down, giving me an “Internal Server Error” along with a 500 error. So, I contacted Bluehost chat support, and they fixed it. They told me it was an issue with my htaccess file and gave me the coding that I should have in the file. I copied and pasted this into a MS Word document so that I would have it. Just about an hour ago, my site was again giving me the same error messages, and I went in through my Bluehost cpanel dashboard, clicked into the htaccess file as I’d previously been shown to from Bluehost chat support, and sure enough, my file was full of code starting with #Start WP All in One Security rather than the #start WP that I was told by Bluehost should be there.

    Is there something in the plugin settings that’s making it rewrite my htaccess file? I’ve currently deactivated it (as a test, to see if it goes down once again and to check what the htaccess file looks like if it does), but this plugin is the only one I’ve added in the past couple of days, so I’m just wondering if I’ve set it up improperly?

    https://wordpress.org/plugins/all-in-one-wp-security-and-firewall/

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Contributor mbrsolution

    (@mbrsolution)

    Hi MarkieMadden can you share here the code that Bluehost gave. As long as it is not revealing anything that is private or any security names etc. If it is can you cross it out.

    Thank you

    Thread Starter MarkieMadden

    (@markiemadden)

    Hi! Thanks for responding!

    This is the code that Bluehost says should be in my htaccess file:

    # Use PHP5.4 Single php.ini as default
    AddHandler application/x-httpd-php54s .php

    # BEGIN WordPress

    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>

    # END WordPress

    The code that appeared in my file instead, began with:

    #Begin WP All in One Security

    And went on from there. There was an awful lot of code between that and where I could see:

    #Begin WordPress.

    However, under the All in One Security Code, there was not just one instance of the code I copied above, but hundreds of repeats of the exact same code string. Not sure what happened there, either. I’m like brand new at all this and would appreciate any suggestions.

    Plugin Contributor mbrsolution

    (@mbrsolution)

    Hi MarkieMadden the code above is the default setup for WordPress. That code cannot be deleted or altered unless you know what you are doing. If you corrupt that code you will not have access to your website. You will see some 500 server error or something similar.

    The following is the code created by this security plugin, which is correct. You will see lots of code in between the following headers depending on the features you select in the plugin.

    # BEGIN All In One WP Security
    # END All In One WP Security

    Thread Starter MarkieMadden

    (@markiemadden)

    Yes, I did see that within the htacccess file, but the only time I’ve gotten this 500 Internal Server error was after I installed and ran the plugin.

    Another source wonders if I possibly set it up incorrectly while I was following along on a video of his, setting up the plugin. Do you think this could be the case? And if so, what could I possibly have set that caused it to create this error?

    I’ve not had an issue all day today, with the plugin installed but deactivated. I had the error twice yesterday. Am considering reactivating the plugin but not with the settings I had when I deactivated it, essentially starting from scratch.

    Thoughts?

    Plugin Contributor mbrsolution

    (@mbrsolution)

    Your best bet is to delete the plugin and install a fresh copy.

    Follow the instructions below.

    – FTP to your host and rename this plugin’s folder or delete it.

    – FTP the .htaccess file to your computer and edit and remove all the code between and including the tags:
    # BEGIN All In One WP Security
    # END All In One WP Security

    – Log into phpMyAdmin and locate the dabase for the website you are having problems with. Go to the wordpress “options” table. Look for the row which has the option_name value of aio_wp_security_configs and delete that row.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Plugin Rewriting htaccess file?’ is closed to new replies.