-
-
Notifications
You must be signed in to change notification settings - Fork 170
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bot blocker not working for Apache/2.4.29 (Ubuntu) #139
Comments
No response. I too am having the same problems. I just installed, actually updated to the newest version as of this date, and I can not get the test responses to reply as they are supposed to. My responses: curl -A "googlebot" https://mydomain.com curl -A "80legs" https://mydomain.com curl -I https://mydomain.com -e http://100dollars-seo.com Granted the URL is forwarded to https:// so I did not expect to get a reply back there, but I did expect to get the expected results when using https:// also. This did not happen. Anybody got any ideas? |
To my log, i have the same for AspiegelBot
I have installed Bad Bot Blocker with this method : https://wiki.visionduweb.fr/index.php?title=Configurer_le_fichier_.htaccess#Bloquer_des_Bots_et_des_URL_ind.C3.A9sirables_avec_Bad_Bot_Blocker My VirtualHost : https://wiki.visionduweb.fr/index.php?title=VirtualHosts_des_domaines_enregistr%C3%A9s |
I was getting same of you, so I try with v2.2 instructions and it's ok now. |
I have add AspiegelBot for my conf ;) Where is the v2.2 instructions ? But, we have Apache 2.4. For my last test, for AspiegelBot, i use the -L option for curl, then i can make the same with 80legs : The curl option -L is the good answer for you and me.
|
Not just an Ubuntu problem, but general Apache 2.4 problem; at least on other POSIX-based OSs (such as stable/up-to-date Slackware GNU/Linux 14.2 w/Apache 2.4.43the same problem: setup instructions' tests for bad bots result in Apache serving pages fine (with normal 200 code.) |
The blocker does work and is tested across 2.2 up to 2.4.23 - see the build log and tests for yourself If you mess up your Apache 2.4 permission structure in any way at all higher up the chain you break everything below it including the blocker.
|
Fine, but I stated same problem except w/more server-focused OSes: any such setup/test logs?
Unclear to me what that means for Apache... can anyone suggest documentation or elaborate how to debug? |
Start off by comparing your apache2.conf with the version used in tests - https://github.com/mitchellkrogza/apache-ultimate-bad-bot-blocker/blob/master/.dev-tools/_test_results/_conf_files_2.4/apache2.conf Specifically these blocks
|
Then also make sure your vhost config follows the same configuration for its main directory block
|
The links above don't work, but found the tests anyway. Only (significant?) change I see is |
I had the same issue but I was whitelisting my own IP, so everything was allowed. Testing from another machine worked well. |
Server version: Apache/2.4.29 (Ubuntu)
I tried following your given steps for Apache2.4 but when i try to test my site using curl, it seems bot blocker is not working.
Curl shows 301 may be because i have http redirect to https ?
But i i use curl -A "80legs" https://example.com
then entire page is loaded, instead of 403 ?
/etc/apache2# cat sites-enabled/000-default.conf
sites-enabled/000-default-le-ssl.conf
The text was updated successfully, but these errors were encountered: