Hi,
Could you please delete this file “/wp-content/wflogs/ips.php” and re-check this issue? the plugin should recreate the file again which should resolve it, possibly a permissions issue prevented this file from being updated correctly during the last update to prevent this issue in first place.
Thanks.
Hi,
seems like the problem fixed it self, no warnings in the log files anymore.
Thanks!
Hi,
hmm, the problem persists. Only logged in users trigger the warning.
Deleting ips.php file didn’t help. The file is only one line.
Any ideas? It is not a serious problem, I could do fresh install of the plugin. There is @ in the code to suppress warnings on the unpack() function call but I’ve got custom error handler to send me mail on all errors that shows it. This is first time I see the error (WF 6.3.3).
Thanks @tmuikku for feedback, I would appreciate if you can update me with the following:
– When you remove the file and it gets recreated again by the plugin, please check the file size, permissions and the owner of the file.
– Which hosting provider are you using?
Thanks.
Hi,
ownership is the same as with other files in the folder and throught the WP installation. Permissions -rw-rw—-, like the config.php in the wflogs folder.
Filesize is 51 bytes it contains only the <?php exit(‘Access denied’); __halt_compiler(); ?> line.
I checked a backup before the plugin update and the ips.php file is 2971 bytes and has data in it after the PHP line. Permissions and ownership in the backup file are the same as with current production file.
This is a self hosted server. The issue appeared when the plugin was updated to version 6.3.3 via WP dashboard, just like many times before 🙂
Thanks for all the information you provided here, this issue has been reported to our dev team (internal reference number: FB4443) and it’s expected to be fixed in the next update.
Thanks.
Cool! I updated another site, from 6.3.2 to 6.3.4 today. Same thing happened.
ips.php file got emptied out on the update or some procedure after the update.
Here is ls few seconds before update and few seconds after update.
# ls -la wp-content/wflogs/
drwxrwxr-x 2 client apache 4096 Mar 17 07:02 .
drwxr-xr-x 14 client apache 4096 Feb 22 09:02 ..
-rw-rw—- 1 client apache 40083 Mar 15 09:24 attack-data.php
-rw-rw—- 1 client apache 425163 Mar 17 07:02 config.php
-rw-rw-r– 1 client apache 133 Jan 25 17:02 .htaccess
-rw-rw—- 1 client apache 691 Mar 15 09:22 ips.php
-rw-rw-r– 1 client apache 87671 Mar 15 17:05 rules.php
-rw-rw—- 1 client apache 39141 Mar 15 17:05 wafRules.rules
# ls -la wp-content/wflogs/
drwxrwxr-x 2 client apache 4096 Mar 17 07:18 .
drwxr-xr-x 14 client apache 4096 Feb 22 09:02 ..
-rw-rw—- 1 client apache 40083 Mar 15 09:24 attack-data.php
-rw-rw—- 1 client apache 425247 Mar 17 07:18 config.php
-rw-rw-r– 1 client apache 133 Jan 25 17:02 .htaccess
-rw-rw—- 1 client apache 51 Mar 17 07:18 ips.php
-rw-rw-r– 1 client apache 87671 Mar 15 17:05 rules.php
-rw-rw—- 1 client apache 39141 Mar 15 17:05 wafRules.rules
