WordPress version 5.6.2
Current theme: genesis customised market child theme by restored 316
Current plugin: Wordfence Security (version 7.4.14)
PHP version 7.3
Hi @cloudeddottedmind, thanks for your question and sorry to see you’re having some trouble with the waf.
It looks to me like there is still a live path specified for the Wordfence WAF so it’s seeking that out when you load the staging site. As the filesystem will be different on your staging site, this is likely the issue. The change needs to be made in .htaccess which explains why it still occurs when Wordfence is disabled. If you open your .htaccess with the file manager/editor of your choice and alter the auto_prepend_file path to /replace/with/staging/site/path/wordfence-waf.php, then this should help resolve the problem.
Thanks,
Peter.
Hi Peter,
thank you – do you mean I should do this on the live website? The staging site is generated through our web host, LiquidWeb, and it simply won’t work at the moment so I wouldn’t be able to do this on it.
Thanks
Hi @cloudeddottedmind,
No, please only change the auto_prepend_file path for the staging site when you are able to. I am working on the assumption that it won’t work due to being a clone or backup of the live site, and the files are in a different directory structure to your live site.
The .htaccess can be changed either via FTP or in the host’s control panel (file manager) and does not need access to the site’s front-end or WordPress dashboard to change.
Thanks,
Peter.
Thanks Peter,
I am in the staging site’s htaccess via FTP, however I can’t see anything from Wordfence or a line with auto_prepend_file.
Thanks
Hi again, I noticed on the scan results there is a server state issue flagged, and when I look at the logs I see this:
[Mar 05 03:05:32:1614931532.238760:1:error] Scan Engine Error: The signature on the request to start a scan is invalid. Please try again.
I’d test this by disabling plugins but cannot do it live. I tried this with the troubleshooting plugin but no luck.
Hi @cloudeddottedmind,
Do you see a .user.ini file containing the auto_prepend_file code rather than .htaccess?
For the scan engine issue, can you do the following so I can get the information I need to help you?
- Kill the existing scan if it is still running (The “Start New Scan” button turns in to a “Stop” button while the scan is running)
- Go to your Scan > Scan Options and Scheduling page and locate the “Performance Options”
Set “Maximum execution time for each scan stage” to 20 on the options page
- Click to “Save Changes”
- Go to the Tools > Diagnostics page
- In the “Debugging Options” section check the circle “Enable debugging mode”
- Click to “Save Changes”.
- Start a new scan
- Copy the last 20 lines from the Log (click the “Show Log” link) or so of the activity log once the scan finishes and paste them in the post.
It may also be helpful to provide us with a diagnostic report to wftest @ wordfence . com. You can find the link to do so at the top of the Wordfence Tools > Diagnostics page. Then click on “Send Report by Email”. Please add your forum username where indicated and respond here after you have sent it.
Note: For the fastest response time, please make sure and add any information or questions directly to this topic and not the email address above unless asked.
Thanks again,
Peter.
Hi Peter,
That worked for the staging site! I found a user.ini file and replaced the path which fixed the problem. Thank you!
For the scan issue, I’ve followed the steps and emailed the scan results. There was no option to link to this thread however…
Quick something I’ve seen on the scan page is this:
[MAR 08 06:02:13] Notice: Undefined index: available in /home/s2/html/wp-content/plugins/ithemes-sync/lib/updater/information.php on line 49 Notice: Undefined index: package-url in /home/s2/html/wp-content/plugins/ithemes-sync/lib/updater/information.php on line 51 Notice: Undefined index: version in /home/s2/html/wp-content/plugins/wordfence/lib/wfScanEngine.php on line 1696 Notice: Undefined index: version in /home/s2/html/wp-content/plugins/wordfence/lib/wfScanEngine.php on line 1716 0
Thank you
Hi @cloudeddottedmind thanks for getting back to me.
I’m glad the staging site is fixed. The other notices you’re seeing are non-fatal so shouldn’t affect the running of your site but I do have some advice.
For the first two (‘available’ and ‘package-url’), you could try reaching out to the ithemes-sync developers to see if there is a known reason for these variable names being undefined.
For the third one related to Wordfence, ‘version’ being an undefined index occurs when Wordfence is checking whether your installed plugin versions match those on the ww.wp.xz.cn repository. Sometimes, plugin developers mistakenly don’t include a version number so Wordfence is unable to check it. If you wish, you can disable all plugins except for Wordfence, then reenable them one-by-one to see when this notice occurs. Once you find the plugin responsible, you could also reach out to their development team to see if they’re aware of the version number being omitted from their latest release.
Thanks again,
Peter.
Thanks Peter, this makes sense!
