Whitelist Monitoring IP

This Security Log entry does not look like it is related to blocking cURL. Typically cURL code to monitor something will use a HEAD Request method. So I will assume what is being blocked is a HEAD Request. To allow/whitelist all HEAD Request see this forum topic: https://forum.ait-pro.com/forums/topic/whitelist-bots-allow-good-bots-to-make-a-head-request/

If this does not solve the problem then I need to see the cURL code you are using to make the Request.

Is this issue/problem resolved?

Thread Start Date: 2-10-2015 to 2-11-2015
Current Date: 2-12-2015

Is this issue/problem resolved?

Thread Start Date: 2-10-2015 to 2-11-2015
Current Date: 2-16-2015

Issue is resolved. I named my bot and then used the code here to resolve:
https://forum.ait-pro.com/forums/topic/whitelist-bots-allow-good-bots-to-make-a-head-request/

Thank you.

Great. Thanks.

I’ve been reading a lot of info on allowing head 403 requests in this forum on solution to remove all HEAD 403 Request blocks.
But I currently do get requests from bad addresses, and would like to keep blocking them. Can I use the following code in Custom to allow a specific IP?

# REQUEST METHODS FILTERED
# If you want to allow HEAD Requests use BPS Custom Code and
# remove/delete HEAD| from the Request Method filter.
# Example: RewriteCond %{REQUEST_METHOD} ^(TRACE|DELETE|TRACK|DEBUG) [NC]
# The TRACE, DELETE, TRACK and DEBUG Request methods should never be removed.
RewriteCond %{REQUEST_METHOD} ^(HEAD|TRACE|DELETE|TRACK|DEBUG) [NC]
RewriteCond %{REMOTE_ADDR} !^(74.86.158.107) [NC] <– Could I just change this to the correct address?
RewriteRule ^(.*)$ – [F]

as you posted here: https://forum.ait-pro.com/forums/topic/split-uptimerobot-whitelist-uptimerobot-bot/page/2/#post-7168

Thank you,

Yes. That should work. The rules work together to create this “and” condition: if the Request Method is HEAD or TRACE or DELETE or TRACK or DEBUG and the IP address is NOT xxx.xxx.xxx.xxx then block/forbid the Request.