Htaccess getting corrupted, use database instead?

  • SvanteH

    (@svanteh)


    11 years, 2 months ago

    Is there an option to let the check/banning of IP’s be done using the database instead of the .htaccess file?

    We’ve got trouble on our sites that the .htaccess file randomly getting corrupted by iThemes Security which is bad (obviously). We’d love to be able to use the default .htaccess file for WordPress and then use the database for iThemes if possible.

    https://ww.wp.xz.cn/plugins/better-wp-security/

Viewing 2 replies - 1 through 2 (of 2 total)
  • defmans7

    (@defmans7)

    11 years, 2 months ago

    Same issue here.
    We have a number of sites which I’ve had to set 444 permissions on all .htaccess files once the security is set up properly.

    It’s an extra step that is annoying and shouldn’t be necessary – but will have to do until this issue is addressed.

    ksmac13gill

    (@ksmac13gill)

    11 years, 2 months ago

    That might explain my problem (I am new and trying to figure out what is going on), but all of a sudden we have tonnes of activity by bots and there are using up our bandwidth (Only since January 2015) and our host said that our htcaccess file was changed.

    We are getting tonnes of 404 errors.

    I also turned the xmlrpc to :
    Only Disable Trackbacks/Pingbacks = Your site will not be susceptible to denial of service attacks via the trackback/pingback feature. Other XMLRPC features will work as normal. You need this if you require features such as Jetpack or the WordPress Mobile app.

    But now my errors are all xmlrpc.php

    Should I turn them to completely disable?

    Any help would be so greatly appreciated as I am very stumped and this has been going on for months now with us almost maxing out our bandwidth each month.

    Thank you in advance.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Htaccess getting corrupted, use database instead?’ is closed to new replies.