Viewing 15 replies - 16 through 30 (of 36 total)
  • Thread Starter verityr

    (@verityr)

    P.S. After I saved, the error message was just for the two directories, instead of five, like you said.

    Plugin Author tokkonopapa

    (@tokkonopapa)

    Do you think that Digital Ocean and Microsoft cloud hits are coming from human beings?

    Unfortunately, I don’t know. But I think we should make our strategy more simple. For example, what is a bad bot do you think? IMO, the bad bot is a bot that make burst accesses in a short period of time (like Brute Force Attack).

    So I’d like to implement to block such a bot in the future.

    By the way, please enable Simulation mode at Front-end target settings (beta). It enables to simulate validation without actual blocking on front-end. Please refer to http://www.ipgeoblock.com/codex/overview.html#simulation-mode

    And please report the results here after a few days. I’m looking foward to it!

    Thanks.

    Plugin Author tokkonopapa

    (@tokkonopapa)

    Hi verityr,

    How are things going?

    I updated 3.0.0 beta (beta 7) so as to be able to control the blocking targets on front-end more flexibly. So please update your version and enable “Block by country” at “Public facing pages“.

    And I’d appreciate if you let me know your progress.

    Thanks.

    Thread Starter verityr

    (@verityr)

    Hi,

    Sorry I forgot to update you earlier. I saw no change in blocking these pesty bots. Where do I go to update? Thank you.

    Plugin Author tokkonopapa

    (@tokkonopapa)

    Wow, the new forum has some issues because the thread where I wrote the link was gone!

    3.0.0b7 download link: https://github.com/tokkonopapa/WordPress-IP-Geo-Block/archive/3.0.0b.zip

    And please download json zip from https://gist.github.com/tokkonopapa/5c297910bfd182a84b27ac634b6afe0f and import ip-geo-block-settings.json from Plugin settings and Save Changes.

    Then you can find followings at Front-end target settings (beta) :

    *#23.96.0.0/16
    *#HOST=amazonaws.com
    *#45.55.128.0/18
    

    This settings is based on your information at https://wordpress.org/support/topic/amazon-bot/#post-7675884
    (If you’re interested in this meaning, please refer to http://www.ipgeoblock.com/codex/ua-string-and-qualification.html).

    Thanks for your cooperation!

    • This reply was modified 8 years, 1 month ago by tokkonopapa.
    Thread Starter verityr

    (@verityr)

    I downloaded both zips. Question – I’m supposed to import json.zip into what?

    Plugin Author tokkonopapa

    (@tokkonopapa)

    I assume you already downloaded json file from https://gist.github.com/tokkonopapa/5c297910bfd182a84b27ac634b6afe0f/archive/8311e2b4d4a3b7de6aa1297a8ea95b96fa5ee72f.zip and unzip, then got ip-geo-block-settings.json which includes a part of this plugin’s settings.

    And you can find “Import settings” button at “Plugin settings” of this plugin’s settings page. Click the button and feed the json file into the file dialog πŸ™‚

    Finally, you need “Save Changes“.

    This json file makes “Simulation mode” enable which doesn’t actually block your targets. But you can find the targets might be blocked on the “Logs” tab. I think you had better to confirm which access can be blocked before those are actually blocked.

    http://www.ipgeoblock.com/codex/overview.html#simulation-mode

    Please feel free to ask anything!

    Thread Starter verityr

    (@verityr)

    What about the new beta plugin zip file? I tried to upload the plugin and got an error message that no valid plugin was found. I’m supposed to deactivate the running plugin first, right?

    I was able to upload the json file to my current plugin, not the new one. I got the same error message as before: Unable to write …/clickandbuilds/wp-content/plugins/.htaccess, …/clickandbuilds/wp-content/themes/.htaccess. Please check permission.

    Before I go any further, I need to get this new plugin downloaded!

    Plugin Author tokkonopapa

    (@tokkonopapa)

    Sorry for your troubles.

    In the previous thread, I wrote this version link which is https://github.com/tokkonopapa/WordPress-IP-Geo-Block/archive/3.0.0b.zip

    I got the same error message as before

    This was fixed in the above version.

    I’m supposed to deactivate the running plugin first, right?

    I usually just overwrite the old plugin without deactivating. But to be on the safe side, YES, please once deactivate and update then re-activate.

    Thanks so much for your cooperation to the beta version test.

    Thread Starter verityr

    (@verityr)

    No problem! When I tried to upload the plugin zip I get an error:

    The package could not be installed. No valid plugins were found. Plugin install failed.

    Plugin Author tokkonopapa

    (@tokkonopapa)

    Hi verityr,

    Did you see the similar page like a picture in this article?

    Then my explain was wrong. Please do not use “Add Plugins” on plugins dashboard to upload the ZIP file, but follow the steps:

    Download 3.0.0b.zip and unzip it on your local PC. You can find ip-geo-block folder in it.

    WordPress-IP-Geo-Block
      β”œβ”€β”€ README.md
      β”œβ”€β”€ deploy.sh
      β”œβ”€β”€ ip-geo-block <-- this one!
      └── test
    

    Then upload ip-geo-block folder by FTP or cPanel file manager to your wp-content/plugins/.

    Plugin Author tokkonopapa

    (@tokkonopapa)

    Or if you compress ip-geo-block folder, then you can upload ip-geo-block.zip via β€œAdd Plugins” on plugin dashboard.

    Good luck!

    Thread Starter verityr

    (@verityr)

    Hi,

    Sorry it took me so long to get back to you. I uploaded the new beta plugin and imported the json file. I got one error message when I saved everything:

    Unable to write /homepages/30/d560012174/htdocs/clickandbuilds/wp-content/plugins/.htaccess, /homepages/30/d560012174/htdocs/clickandbuilds/wp-content/themes/.htaccess. Please check the permission. Or please refer to How to fix permission troubles? to set them manually.

    Plugin Author tokkonopapa

    (@tokkonopapa)

    Hi,

    My explanation was bad. When you disable “Force to load WP core”, then you won’t see the error message. I think we developer should not change the permission because every server has their own security policy with it. So I can’t fix the permission error itself. I understand you want to enable “Force to load WP core”, but let’s solve the topic about blocking bots at first.

    The error you reported had not affected to the “Front-end target settings (beta)”. You can see:

    Front-end target settings (beta)

    If it’s ok, please keep watching at “Logs”:

    Log of Public facing pages

    If the blocking functionality is ok, then try to uncheck “Simulation mode”.

    Thanks.

    Plugin Author tokkonopapa

    (@tokkonopapa)

    Hello @verityr,

    How’s it going? I hope you to try my new version to block bots on front-end. <a href=”http://www.ipgeoblock.com/codex/ua-string-and-qualification.html&#8221; title=”
    UA string and Qualification”>This document may help you.

    Once I close this thread. But please feel free to ask something about your concern.
    Thanks.

Viewing 15 replies - 16 through 30 (of 36 total)
  • The topic ‘Amazon bot’ is closed to new replies.