Breaks backend CSS

Hi @catmaniax,

Regarding to Imagify, my estimation in the previous thread was wrong.

I tried adding it as an exception but nothing changed.

You’re right!

Imagify’s automatic compression works as wp cron which is requested by the server itself. So if your server is placed different from your country, the request by wp cron might be blocked.

I’ll resolve this issue in the next release. But for the time being, could you put your server’s IP address into “Whitelist of extra IP addresses prior to country code” at “Validation rule settings” section?

As for Slimstat Analytics, I’ll hold out a little more investigation.

I’d so appreciate @catmaniax. Your cooperation would improve this plugin!

Hi @catmaniax,

By saying my server’s IP you mean my hosting company’s IP that my site is hosted or just my current (dynamic) IP address?

I’m sorry but again, my investigation in the previous thread was wrong. Imagify’s automatic optimization might not be processed by wp cron, but processed by some hooks which would be triggered when you upload images. So please do not mind the IP address(es).

Anyway, I’ll fix the issue of Imagify. I’d appreciate your kind patience until I release the new version.

What I actually want IP Geo Block is for blocking anyone visiting from Russia and Ukraine (since they are big on hacks) and returning a 404 error to them.

Yes I know. But this plugin is not for just “Block by country”. It’s for hardening security. And the issue of Imagify is caused by this point especially when you configure “Prevent Zero-day Exploit” for “Admin ajax/post”.

I’d also appreciate your kind understanding.

Thanks.