Signup abuse detection and blocking

Signup abuse detection and blocking [Paid] 1.20.4

No permission to buy ($45.00)
@Xon it would be great if you could implement the following:
  1. Detect VPNs/proxies for each post, not for signup/registration only
This can easily exhaust API calls when using various backend providers.

I have been considering email verification, but simply haven't had time to research these.

  1. Add fingerprinting as another method for multiple accounts detection using FingerprintJS, Evercookie or similar
I've found fingerprinting is very difficult and often doesn't give useful results when identify an exact individual and this add-on is already complex enough without introducing fuzzy matching for possible multiple accounts.
 
Perhaps it is due to the update, or perhaps I changed something myself. I do not know.
I have not had a single registration in a week. The usual average is more than 50 per day.
Is there any setting I should check that might be blocking new registrations?
Normally, all registrations were simply sent to moderation.
 
There is a problem with your latest version.

The add-on is flagging many normal registrations as if they were coming from the same IP address. Even my own test registrations are being identified as having the same IP address as many others.

This IP address is the IP address of my server itself.

a) There is a server problem and/or
b) There is a software problem.

We changed the server a few days ago.
At the same time, we updated your add-on to the latest version.
 
There is a problem with your latest version.

The add-on is flagging many normal registrations as if they were coming from the same IP address. Even my own test registrations are being identified as having the same IP address as many others.

This IP address is the IP address of my server itself.

a) There is a server problem and/or
b) There is a software problem.

We changed the server a few days ago.
At the same time, we updated your add-on to the latest version.
You've got a configuration problem, that's not related to this addon.

I'd go lookup the support issues already raised in the XF support section regarding members showing the same IP addresses and/or those who show up with the server's IP address as you mentioned. You should go back and look at your configuration between the old server and new server to see what's different.
 
I installed your add-on for testing on a client’s forum, and the same problem is happening there.

New registrations are shown with the message Same IP, and the IP shown is the server’s IP.

The add-on was installed without any changes.

This test on a completely different server proves that the problem probably cannot be caused by my new server. The same error happens elsewhere too.

If this is caused by a wrong setting in the add-on, then that wrong setting is the default setting of the add-on.

Either way, there must be a reason why so many users are suddenly shown as if they had registered from the same IP. Whether it is a configuration problem or a bug in the code, it needs to be fixed, please.
 
You can check what IP address is being passed by PHP by looking at the value for $_SERVER['REMOTE_ADDR'] in the PHP info in your admin CP. Click the PHP version number on the admin home page and it will list all the settings for PHP including the session info. The IP shown for $_SERVER['REMOTE_ADDR'] should be your current IP. If it shows as the same value as $_SERVER['SERVER_ADDR'] that would indicate that something is happening between you and PHP; a guess would be some kind of reverse proxy running on the host, e.g. as in the case in this thread - https://xenforo.com/community/threads/all-users-have-the-same-ip.74440/

You can also look at what XenForo sees your IP address as in the current users page or the IP addresses against your user.
 
Thank you, maybe this could be an idea.
But why there was never any problems before the last version of Abuse Detection and/or newest Xenforo version?
I have seen now that some of the registrations have this problem, but not all.
 
The problem most likely comes either from the latest XenForo version or from your latest add-on version.
Given that no other customer of XF or of this add on seems to suffer from this issue this seems a pretty bold statement.
Meanwhile, I have tested a third server, and the same problem occurs there as well.
Given that all the incidents do have in common that you configured the server and/or XF doesn't it seem a realistic possiblity that you did the same config error twice in a row? I know that it's always the others that do make mistakes, never one self. But if you want to solve your issues instead of finger pointing you should probably be a little more realistic in your analysis...
 
  • Like
Reactions: ENF
Back
Top Bottom