WordFence API error

i have another scan

………
We could not repair any of the files you selected. We encountered the following errors: WordFence API error: An error occured trying to open the requested file.
WordFence API error: An error occured trying to open the requested file.

Hi @khubaibch,

I would first try Learning Mode to see if your issue with editing and creating posts can be resolved this way.

From the Wordfence Dashboard click on Manage WAF. Then you will see Basic Firewall Options > Web Application Firewall Status. Change the option to Learning Mode. Now perform the actions that were causing issues. This will help Wordfence learn that these actions are normal and it will allow them in the future. After you have finished performing the actions, switch the WAF from Learning Mode back to Enabled and Protecting. Now test to see if these actions work correctly.

However, the scan issue does seem like it could be a communication issue between your site and our servers rather than something that can be solved with the above steps. If this is the case, try this:

• Go to the Wordfence > Tools > Diagnostics page
• In the “Debugging Options” section check the circle “Enable debugging mode”
• Click to “Save Changes”.
• CANCEL any current scan and 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 this post.

Wordfence > Tools > Diagnostic > Debugging Screenshot

This will help me see exactly what is happening when the scan fails.

Thanks,

Peter.

Dec 05 15:39:46] Scanned contents of 70008 additional files at 29.72 per second
[Dec 05 15:39:47] Scanned contents of 70059 additional files at 29.73 per second
[Dec 05 15:39:48] Scanned contents of 70098 additional files at 29.73 per second
[Dec 05 15:39:49] Scanned contents of 70145 additional files at 29.74 per second
[Dec 05 15:39:50] Scanned contents of 70184 additional files at 29.74 per second
[Dec 05 15:39:51] Scanned contents of 70240 additional files at 29.75 per second
[Dec 05 15:39:52] Scanned contents of 70291 additional files at 29.76 per second
[Dec 05 15:39:53] Scanned contents of 70328 additional files at 29.76 per second
[Dec 05 15:39:54] Scanned contents of 70372 additional files at 29.77 per second
[Dec 05 15:39:55] Scanned contents of 70437 additional files at 29.78 per second
[Dec 05 15:39:56] Scanned contents of 70483 additional files at 29.79 per second
[Dec 05 15:39:57] Scanned contents of 70547 additional files at 29.80 per second
[Dec 05 15:39:58] Scanned contents of 70604 additional files at 29.81 per second
[Dec 05 15:39:59] Scanned contents of 70662 additional files at 29.83 per second
[Dec 05 15:40:00] Scanned contents of 70719 additional files at 29.84 per second
[Dec 05 15:40:01] Scanned contents of 70776 additional files at 29.85 per second
[Dec 05 15:40:02] Scanned contents of 70824 additional files at 29.86 per second
[Dec 05 15:40:03] Scanned contents of 70877 additional files at 29.87 per second
[Dec 05 15:40:04] Scanned contents of 70931 additional files at 29.88 per second
[Dec 05 15:40:05] Scanned contents of 70972 additional files at 29.88 per second
[Dec 05 15:40:06] Scanned contents of 71001 additional files at 29.89 per second
[Dec 05 15:40:06] Asking Wordfence to check URLs against malware list.
[Dec 05 15:40:06] Checking 5707 host keys against Wordfence scanning servers.
[Dec 05 15:40:06] Done host key check.
[Dec 05 15:40:07] Done file contents scan
[Dec 05 15:40:07] Adding issue: File appears to be malicious or unsafe: wp-includes/jsmm/codemirror/codemirror.min.js
[Dec 05 15:40:07] Adding issue: File appears to be malicious or unsafe: wp-includes/jsmm/dist/block-editor.js
[Dec 05 15:40:07] Adding issue: File appears to be malicious or unsafe: wp-includes/jsmm/dist/block-library.js
[Dec 05 15:40:07] Adding issue: File appears to be malicious or unsafe: wp-includes/jsmm/dist/components.js
[Dec 05 15:40:07] Adding issue: File appears to be malicious or unsafe: wp-includes/jsmm/dist/components.min.js
[Dec 05 15:40:07] Adding issue: File appears to be malicious or unsafe: wp-includes/jsmm/dist/edit-post.js
[Dec 05 15:40:07] Adding issue: File appears to be malicious or unsafe: wp-includes/jsmm/dist/vendor/react-dom.js
[Dec 05 15:40:07] Adding issue: File appears to be malicious or unsafe: wp-includes/jsmm/tinymce/wp-tinymce.js
[Dec 05 15:40:07] Adding issue: File appears to be malicious or unsafe: wp-includes/jsmm/zxcvbn.min.js
[Dec 05 15:40:08] Scanning posts with 1000 left to scan.
[Dec 05 15:40:09] Examining URLs found in posts we scanned for dangerous websites
[Dec 05 15:40:09] Checking 1261 host keys against Wordfence scanning servers.
[Dec 05 15:40:10] Done host key check.
[Dec 05 15:40:10] Done examining URLs
[Dec 05 15:40:10] Starting password strength check on 4 users.
[Dec 05 15:40:18] Examining URLs found in the options we scanned for dangerous websites
[Dec 05 15:40:18] Done examining URLs
[Dec 05 15:40:18] ——————-
[Dec 05 15:40:18] Wordfence used 25.45 MB of memory for scan. Server peak memory usage was: 27.45 MB
[Dec 05 15:40:18] Scan Complete. Scanned 80738 files, 12 plugins, 5 themes, 1273 posts, 0 comments and 61771 URLs in 44 minutes 25 seconds.

Hi @khubaibch,

It looks like that scan completed successfully. Are they working now going forward or are you still receiving errors on the automatic scans?

Thanks,

Peter.