• Resolved prentice

    (@prentice)


    I’ve updated my htaccess coding to block bots. The data I’ve entered should work however, I’m receiving errors. My contact with Fatcow leads me to believe these errors can be corrected. The errors read as follows:

    20141228T223109: cipherproductionsinc.com/wp-content/plugins/calpress-pro-1.7/css/calp-widget.php
    PHP Warning: mysqli_real_connect(): The server requested authentication method unknown to the client [mysql_old_password] in /hermes/walnaweb01a/b1799/moo.cipherproductionsinc/wordpress files II/wp-includes/wp-db.php on line 1379
    PHP Warning: mysqli_real_connect(): (HY000/2054): The server requested authentication method unknown to the client in /hermes/walnaweb01a/b1799/moo.cipherproductionsinc/wordpress files II/wp-includes/wp-db.php on line 1379
    PHP Deprecated: mysql_connect(): The mysql extension is

    20141228T223116: cipherproductionsinc.com/wp-admin/admin-ajax.php
    PHP Warning: mysqli_real_connect(): The server requested authentication method unknown to the client [mysql_old_password] in /hermes/walnaweb01a/b1799/moo.cipherproductionsinc/wordpress files II/wp-includes/wp-db.php on line 1379
    PHP Warning: mysqli_real_connect(): (HY000/2054): The server requested authentication method unknown to the client in /hermes/walnaweb01a/b1799/moo.cipherproductionsinc/wordpress files II/wp-includes/wp-db.php on line 1379
    PHP Deprecated: mysql_connect(): The mysql extension is

    20141228T223127: cipherproductionsinc.com/wp-cron.php
    PHP Warning: mysqli_real_connect(): The server requested authentication method unknown to the client [mysql_old_password] in /hermes/walnaweb01a/b1799/moo.cipherproductionsinc/wordpress files II/wp-includes/wp-db.php on line 1379
    PHP Warning: mysqli_real_connect(): (HY000/2054): The server requested authentication method unknown to the client in /hermes/walnaweb01a/b1799/moo.cipherproductionsinc/wordpress files II/wp-includes/wp-db.php on line 1379
    PHP Deprecated: mysql_connect(): The mysql extension is

    20141228T223128: cipherproductionsinc.com/index.php
    PHP Warning: mysqli_real_connect(): The server requested authentication method unknown to the client [mysql_old_password] in /hermes/walnaweb01a/b1799/moo.cipherproductionsinc/wordpress files II/wp-includes/wp-db.php on line 1379
    PHP Warning: mysqli_real_connect(): (HY000/2054): The server requested authentication method unknown to the client in /hermes/walnaweb01a/b1799/moo.cipherproductionsinc/wordpress files II/wp-includes/wp-db.php on line 1379

Viewing 13 replies - 1 through 13 (of 13 total)
  • Moderator James Huff

    (@macmanx)

    Hm, that shouldn’t be happening.

    Try deactivating all plugins. If that resolves the issue, reactivate each one individually until you find the cause.

    If that does not resolve the issue, try switching to the Twenty Fifteen theme to rule-out a theme-specific issue (theme functions can interfere like plugins).

    Thread Starter prentice

    (@prentice)

    I tried both suggestions. I’m still receiving the same errors.

    Moderator James Huff

    (@macmanx)

    What did you add to your .htaccess file? And, if you remove it, do the error stop?

    Thread Starter prentice

    (@prentice)

    Yes, it works just fine when it’s removed.

    [Large code excerpt removed by moderator per forum rules. Please use the pastebin for all large code excerpts. It works better anyway.]

    Moderator James Huff

    (@macmanx)

    Wow, yeah first a few things:

    1. Blocking by user agent is tedious. Just to give you an example of how tedious, that’s a bit less than 10% of the known bad bots out there.

    2. Blocking by IP is pointless and harmful to real people. Most ISPs give out dynamic IPs, that’s a new IP every time you reconnect. In other words, chances are that the people you were trying to block by IP have long-since moved on and you’re now blocking potential legitimate visitors.

    3. You’re blocking blank referrers, which means anyone who tries to visit your site by simply typing in the domain will be denied.

    4. Now that that’s out of the way, replace what you had with *only* this: https://cloudup.com/cIrl3GIggcW

    Moderator James Huff

    (@macmanx)

    Just noting, the forum messed up the formatting on what I provided, so please paste what’s in the CloudUp link, not what the forum provided a few minutes ago.

    Thread Starter prentice

    (@prentice)

    That code was what I had added first, but I was afraid that it doesn’t include all bots which is my purpose. You suggested that my list only contains 10% of known bad bots. What does the code that you suggest contain?

    Moderator James Huff

    (@macmanx)

    The code I suggest blocks specific *types* of attacks and common attack vectors.

    It’s the difference between saying “no one gets in this gate” vs. listing out the name of each person on the planet. šŸ˜‰

    Smaller .htaccess = a quicker (and in this case safer) site.

    Thread Starter prentice

    (@prentice)

    However, this doesn’t block these bots, does it?

    Moderator James Huff

    (@macmanx)

    It blocks them by blocking what they do, not by blocking them by name. That’s why it’s a much smaller list that you won’t need to update when new bots appear.

    Moderator James Huff

    (@macmanx)

    To clarify, you don’t need to use my .htaccess suggestion, but something in your .htaccess is what’s breaking your site, so I’m suggesting a few .htaccess rules that I know work without issue.

    Thread Starter prentice

    (@prentice)

    Wonderful. I guess that’s all I needed for now. I appreciate all of the effort that you put into helping. That was a noble gesture this holiday season.

    Moderator James Huff

    (@macmanx)

    You’re welcome!

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

The topic ‘line 1379’ is closed to new replies.