i put this rule to cloudflare (cf.client.bot and ip.geoip.asnum ne 2635) then block
it simply blocks all bots except wordpress’s bots so jetpack’s features still running, jetpack image cdn still works.
Monitored for enough time, problem solved, 30 accesses blocked by firewall so far and most of them were unnecessary, i don’t even know where are they from.
notes for future readers,
to block every bot use the jetpack’s cdn, use this rule (cf.client.bot and ip.geoip.asnum ne 2635) then block
to block every bot but want to use jetpack’s cdn and allow google bot (cf.client.bot and ip.geoip.asnum ne 2635) or (cf.client.bot and ip.geoip.asnum ne 15169) then block
allot google bot Jetpack and pinterest (cf.client.bot and ip.geoip.asnum ne 2635) or (icf.client.bot and p.geoip.asnum ne 15169) or (cf.client.bot and not http.user_agent contains "Pinterestbot") then block
What “ping” do you mean? “ping” is a program to send ICMP messages which can be used to test whether a server is available on the network and to measure network latency. Our servers block “ping” because it unnecessarily exposes network information and isn’t required for websites to work.
If you’re using Cloudflare, then Cloudflare is returning the pings for your website. If that ping shows high latency, then it’s the connection between you and Cloudflare that’s bad. It doesn’t say anything about your hosting account or the website on it.
i meant “sunucunun ilk yanıtı” i think its called “the first response from server” or something like.
since i put the firewall rule i had 0 problem.
right now
this latency is minimum 178ms without cloudflare (on volume 1_1)
and with cloudflare, with yellow cloud, its minimum 221ms, for me and without php jobs,