[Plugin: Stop Spammer Registrations Plugin] I'm the Admin and it detected me as a spammer and l

If you delete the plugin you can get in.

If you used the 3.1 version and can’t log in, it means that you look like a spammer to the plugin and should either white list yourself or figure out why the Spam databases think you are a spammer.

Keith

Anybody has a clue on this problem? I can even log in my own website!!

Delete the plugin directly using FTP and then login and reinstall with the latest version. It will White List your IP address, even if your are on one of the Spam Databases.

Keith

Hello Keith, I checked the Spam Database and my IP address did not come up.
Exactly how do I go about using the FTP process?
Note: everything was working well with with this plugin until few days ago I updated to the new released version.
Please direct me on how to do it if you don’t mind!
Thanks and have a great day

How do you copy files to your WP install?

You would go to the install location in the wp-content/plugins directory and delete the stop-spammer-registrations-plugin directory. You can do this with FTP if your host is set up for it or you can do it directly if you have access to your server. Some hosts provide a file maintenance app that lets you copy or delete files.

Basically, however you maintain files on your server, you would use this to delete the directory.

Keith

This plugin not work well with web server behind proxy server. For example, in my case, I have varnish as frontend web proxy cache server and nginx with php5-fpm as backend web server. All queue to web server is from varnish. So all IPs send from varnish to nginx will be 127.0.0.1 . Even when I whitelist 127.0.0.1, it blocks every admin dashboard access including myself.

I look for the forwarded headers, but I didn’t think anyone would be running it from a “localhost” configuration.

copy this line and paste it after line 514

substr($ip,0,8)=='127.0.0.1' ||

if your proxy is passing the source IP in the X-FORWARDED-FOR header then it should work.

I will add this to the next release.

It should not keep you out, though. I don’t know what that’s about – unless 127.0.0.1 is on one of the databases.

Keith

Oops! that should be

substr($ip,0,9)=='127.0.0.1' ||

Keith

It is working now, I only need to add some configuration lines in nginx.conf. Below is nginx configuration line to work web server behind proxy server.
#to know original ip from client through cloudflare
set_real_ip_from 204.93.240.0/24;
set_real_ip_from 204.93.177.0/24;
set_real_ip_from 199.27.128.0/21;
set_real_ip_from 173.245.48.0/20;
set_real_ip_from 103.22.200.0/22;
set_real_ip_from 141.101.64.0/18;
set_real_ip_from 108.162.192.0/18;
set_real_ip_from 190.93.240.0/20;
set_real_ip_from 127.0.0.1/32;
real_ip_header CF-Connecting-IP;

I am not sure this is good for all IPs. It still may not stop spammers. If this passes on the X-forwarded headers than it is what you need. Let us know if you catch spammers.

Keith