Proxy & VPN Blocker

Hi @mrbrightside1984

It does sound like a conflict with something and I am sorry that you’ll have to go through a process of elimination, I know these can be very frustrating.

I installed Asset Cleanup on my test site and Proxy & VPN Blocker appears to work still so I don’t think it is that.

Perhaps you have another security plugin that may be preventing some of Proxy & VPN Blocker code from running.

Hi @mrbrightside1984

The last few versions have changed nothing relating to VPN detection and it should still function as versions prior to 1.5.2 did, so I’m not sure what your issue could be in this case.

The most recent versions were adding of a settings key in 1.5.2 that if you update the settings it will set a new random key that past Known Good IP caches are rechecked again under the updated settings and then cached again with the new random key. 1.5.3 was a minor fix for that and 1.5.4 cleaned up a little code (Mostly a couple of typos on the settings page) and implemented continents to the country blocking feature since the proxycheck.io API started reporting continent data.

1.5.2 is not generally recommended to use as it broke the cache check in a way that good IP’s were repeatedly rechecked instead of the IP being cached for 30 mins which means higher than normal queries to the proxycheck.io, perhaps not a bad thing if your API Key allows for a lot of daily queries (which is why this issue took almost a couple of weeks to come to light at the time).

I have tested Opera VPN and another VPN on several of the live sites that I administrate and use the current 1.5.4 version of Proxy & VPN Blocker on and it is working as expected.

I checked your page at https://faucetgamers.com/login with OperaVPN and another VPN and both are undetected, is your site on 1.5.2 or still 1.5.4? May I also ask what you are using for the login page currently? It looks like WordPress login but styled, I assume you edited its CSS yourself in this case.

Thanks, Rick.

Hi bookgeek!

Google should never be blocked by the API so I just alerted proxycheck.io to check if this was happening. It was discovered that due to an issue today some Google IP’s were incorrectly detected by the automated detection system, this has now been corrected and proxycheck.io offers their apology for any inconvenience this may have caused you and thanks you for bringing this to attention. Further measures have been taken to prevent this from happening again.

Rick.

Google Adsense shouldn’t be affected by the plugin, it should not affect Google finding your ads.txt as that isn’t related to WordPress and is just a file in your root directory.

Google IP ranges are also not blacklisted by the proxycheck.io API.

I am unsure of what your issue could be.

Sorry I couldn’t be of more help at this stage.

Hi benbrecher,

This is outside of the scope of the plugin right now but you can perhaps try a custom rule on the proxycheck.io dashboard. It should theoretically work.

https://proxycheck.io/api/?cr=1 is the information on the rules system for reference.

You would create a rule like follows:

View post on imgur.com

Depending on what you use for your login page URL (if not the WordPress default) you would have to change the tag in the custom rule to match what you use.

Hopefully this would work for you.

I did some testing and it does appear that the theme is the problem as PVB doesn’t block on specified pages with this theme enabled, It appears to have a lot of features so it could be anything really.

Hi Zeus2222,

I understand that you also asked for support from proxycheck.io over this issue.

I’d like to personally thank you for bringing this issue to my attention! There was a ‘Known Good IP Cache’ issue caused by the last update that could mean higher than usual queries. I am sorry that this happened.

Your site is getting that many hits but the known good IP cache wasn’t functioning properly.

An update has been pushed today that corrects this.

Thank you again,

Rick

Good to hear that it is at least functioning!

I have not heard of conflicts with jetpack before, I will have to investigate this.

wp-login is protected by default by PVB, though I am not sure why this was bounced back to /login unless there’s something else going on. It would either bounce you to the default blocked message page or redirect you to your custom blocked page.

There was recently an issue in the API that may lead to blocking of your own IP address if you manage a lot of WordPress sites from the same IP, it was incorrectly determining that this could be a threat and your risk score would go over 33% and be flagged potentially dangerous. This is perhaps why your own IP has been detected recently.

Hi mrbrightside,

It does appear to not be working currently on your site, either for Opera VPN or the VPN I use for testing of the plugin (which I know gets blocked on other sites as does Opera which is detected as a VPN accurately by proxycheck.io).

You appear to be using a custom login/register pages of Ultimate Member, these do work in general and I am sure you have these pages selected to be blocked in PVB.

Is litespeed cache still disabled?

I believe there is a conflict somewhere but it may be a trial and error thing to find out what it is, usually these issues are caused by cache plugins due to the way they work.

I have done some testing and I am unable reproduce this issue on the latest version of the plugin. All I can think is there is some kind of comflict with something else.

Apoligies for not being of more help at this time.

Hi @sandgroper,

What was the PHP error before you disabled the country array?

Also what version of PHP are you using? This isn’t something I’ve come across before.

Rick

Hi @swinzi,

Apologies for the slow response, I have been away.

Unfortunately this particular use case is not currently supported but is perhaps something I can look in to. Currently the specific pages/posts option is in addition to the other blocking like log in and registration.

Hi Alex,

Thank you for pointing this out, I have fixed this and it will be in the next update!

Rick.

@dottydirectory I got a bit mixed up and thought this was relating to another support question that’s open recently about blocking on specific pages. My bad!

No I don’t think this would cause RAM issues.

@dottydirectory you have WP Super Cache installed

WP Super Cache: by Automattic – 1.6.4

Unfortunately at this time the block on specific pages/posts does not work with caching plugins due to the way caching plugins work, they serve a static version of the site pages to visitors and this happens ahead of where the Proxy & VPN Blocker Plugin would be able to interact with the visitor.

You can experiment with Late Init in some caching plugins, WP Super Cache has this under Advanced in its settings

View post on imgur.com

I don’t see anything relating to why the resource usage would be high in your system status however.

• This reply was modified 5 years, 7 months ago by Proxy & VPN Blocker.
• This reply was modified 5 years, 7 months ago by Proxy & VPN Blocker.