Sabine Jakubinek

Hi!

Thx for your reply. Well, I’m the “host tech support guys” as it’s my own server ??

Pls correct me if I’m wrong, it’s been a long time I did PHP. Your function is looking for an IP with different methods.
Let’s say a user is using a proxy with a fake XFF and therefore smth like 192.168.1.102. The first two results before “HTTP_X_FORWARDED_FOR” didn’t end up in a valid result. Then your foreach will return 192.168.1.102 as it is valid for “FILTER_VALIDATE_IP” and stops looking for the other keys. While AFAIK Apache is using “REMOTE_ADDR” for its logfiles.

Regards

In your plugin:
172.16.105.* 2017-07-05 10:18:46 (I removed the UserId and Username that was used)

The Apache Log shows the following:
83.209.xxx.xxx – – [05/Jul/2017:10:18:44 +0200] “GET /wp-login.php HTTP/1.1” 200 4069
83.209.xxx.xxx – – [05/Jul/2017:10:18:45 +0200] “POST /wp-login.php HTTP/1.1” 200 4218

There were only two other entries at that day on that blog. But the time between were ~8 hours before and 11 hours later. The Apache log also has no other entries than these three.

Check this and line 1744. Still visible for everyone that I wasn’t talking nonsense.

Strange that I’ve found it in your code and could also mention the line. I do PHP for over 16 years for a living. I know what I’m talking about. Ofc it’s not in your code anymore. It was 4 weeks and propably many versions ago. Nice try ??

Sorry to say, but it’s getting worse. The function ajax_scan() in pikefirewall.php is called when someone gets into the plugin page. Which is AFAIK ok. But pls have a look at line 1744 where a file_put_contents took its place. We don’t have any directory like this. So we get an error: “[28-Nov-2016 10:43:40 UTC] PHP Warning: file_put_contents(/var/www/html/b-press/wp-content/plugins/pike-firewall/time_pre.txt): failed to open stream: No such file or directory in […]”
As the mentioned problem wasn’t fixed and it’s getting worse we’re going to delete your plugin out of our blogs.

Sorry for the late answer.
We have at least 4 sites on our server which are using your plugin and still we’re encountering this error. In none of the access logs we were able to find an IPv6 request. :/

Sorry for my late answer. It seems all is fixed now. Thank you very much!

Thanks for your reply.

I can’t tell you which of the four WordPress sites are having this error. But I was updating all of them yesterday, including your plugin, WordPress itself and other plugins. As in all blogs your plugin was configured with logging on and deleting all entries wasn’t possible (CSRF detected error), I deactivated and after it reactivated all of them. Also I reconfigured them. After this I found the above error appearing from time to time.

I downloaded the .zip from here and extracted it on the server into the right place. It seems to run now. Anyway, it would have been really cool, to be able to update it via WordPress itself, like before.

If it helps: It’s my own server and I have administrator access/role.

No, I removed it via RDP and it’s definately gone. Check that more than once.

Similiar problem, another file:
Die Datei konnte nicht kopiert werden. nextgen-gallery/products/photocrati_nextgen/modules/nextgen_addgallery_page/static/plupload-2.1.1/jquery.plupload.queue/css/jquery.plupload.queue.min.css

Perfect! Thx a lot!

Hi!

I had the same issue and solved the problem by changing the <? to <?PHP in the wpapi.config.php. As my server doesn’t allow the shortform.

Regards