Scan Failed

Hello, @jaypeg

Thanks for getting back.

I’m not seeing that error in your diagnostics at the moment. Can you confirm if you still see it, or if it is intermittent by chance? You can try a new scan scan and go back to the diagnostics page and refresh it a few times to see if you see the error at all.

If you’re not seeing the error anymore, please send over the last 20-30 lines at the time the new scan fails. Its possible something else is stopping the scan or there may still be intermittent connectivity issues causing the scan to fail.

I’ll resolve your other topic and we can proceed in this one.

Thanks,
Scott

Thank you Scott. I just ran it again and it failed again. It doesn’t appear intermittent. It’s every time I run it now. Here are the last of the logs from when it just failed.

[Oct 17 15:38:31] iconv(): Detected an illegal character in input string (8) File: /home/jong5nw19fur/public_html/wp-content/plugins/wpforms-lite/vendor/symfony/polyfill-mbstring/Mbstring.php Line: 409
[Oct 17 15:38:31] Scanning contents: wp-content/plugins/wpforms-lite/assets/images/payments/status/icon-partrefund.svg (Size: 611 B Mem: 139 MB)
[Oct 17 15:38:31] iconv(): Detected an illegal character in input string (8) File: /home/jong5nw19fur/public_html/wp-content/plugins/wpforms-lite/vendor/symfony/polyfill-mbstring/Mbstring.php Line: 409
[Oct 17 15:38:31] Scanning contents: wp-content/plugins/wordpress-seo/migrations/20171228151841_WpYoastPrimaryTerm.php (Size: 1.4 KB Mem: 139 MB)
[Oct 17 15:38:31] Scanning contents: wp-content/plugins/revslider/public/assets/svg/busy-icons-svg/money5.svg (Size: 11.53 KB Mem: 139 MB)
[Oct 17 15:38:31] iconv(): Detected an illegal character in input string (8) File: /home/jong5nw19fur/public_html/wp-content/plugins/wpforms-lite/vendor/symfony/polyfill-mbstring/Mbstring.php Line: 409
[Oct 17 15:38:31] Scanned contents of 2155 additional files at 7.12 per second
[Oct 17 15:38:31] Scanning contents: wp-content/plugins/revslider/public/assets/svg/notification/ic_airline_seat_legroom_extra_24px.svg (Size: 313 B Mem: 139 MB)
[Oct 17 15:38:31] iconv(): Detected an illegal character in input string (8) File: /home/jong5nw19fur/public_html/wp-content/plugins/wpforms-lite/vendor/symfony/polyfill-mbstring/Mbstring.php Line: 409
[Oct 17 15:38:31] Scanning contents: wp-content/plugins/us-core/templates/sidebar.php (Size: 7.45 KB Mem: 139 MB)
[Oct 17 15:38:32] Scanning contents: wp-content/plugins/revslider/public/assets/svg/busy-icons-svg/laptop-diagram.svg (Size: 10.08 KB Mem: 139 MB)
[Oct 17 15:38:32] iconv(): Detected an illegal character in input string (8) File: /home/jong5nw19fur/public_html/wp-content/plugins/wpforms-lite/vendor/symfony/polyfill-mbstring/Mbstring.php Line: 409
[Oct 17 15:38:32] Scanning contents: wp-content/plugins/wpforms-lite/src/Admin/Forms/BulkActions.php (Size: 9.64 KB Mem: 139 MB)
[Oct 17 15:38:32] Scanning contents: wp-content/plugins/revslider/public/assets/svg/busy-icons-svg/arrow-left.svg (Size: 4.43 KB Mem: 139 MB)
[Oct 17 15:38:32] iconv(): Detected an illegal character in input string (8) File: /home/jong5nw19fur/public_html/wp-content/plugins/wpforms-lite/vendor/symfony/polyfill-mbstring/Mbstring.php Line: 409
[Oct 17 15:38:32] Scanning contents: wp-content/plugins/js_composer/include/templates/editors/popups/ai/sad-ai-logo.tpl.php (Size: 23.23 KB Mem: 139 MB)
[Oct 17 15:38:32] iconv(): Detected an illegal character in input string (8) File: /home/jong5nw19fur/public_html/wp-content/plugins/wpforms-lite/vendor/symfony/polyfill-mbstring/Mbstring.php Line: 409
[Oct 17 15:38:32] Scanning contents: wp-content/plugins/jetpack/extensions/blocks/contact-info/phone/editor.js (Size: 185 B Mem: 139 MB)
[Oct 17 15:38:32] Scanning contents: wp-content/plugins/wpforms-lite/templates/admin/settings/email-heading.php (Size: 530 B Mem: 139 MB)
[Oct 17 15:38:32] Scanning contents: wp-content/plugins/jetpack/json-endpoints/jetpack/class.jetpack-json-api-modules-list-endpoint.php (Size: 311 B Mem: 139 MB)
[Oct 17 15:38:32] Scanning contents: wp-content/plugins/wpforms-lite/src/Helpers/CacheBase.php (Size: 11.49 KB Mem: 139 MB)
[Oct 17 15:38:32] iconv(): Detected an illegal character in input string (8) File: /home/jong5nw19fur/public_html/wp-content/plugins/wpforms-lite/vendor/symfony/polyfill-mbstring/Mbstring.php Line: 409
[Oct 17 15:38:32] Scanning contents: wp-content/plugins/jetpack/extensions/blocks/slideshow/slideshow.js (Size: 6.14 KB Mem: 139 MB)
[Oct 17 15:38:32] Scanning contents: wp-content/plugins/jetpack/extensions/blocks/markdown/test/__snapshots__/markdown-renderer.js.snap (Size: 1.75 KB Mem: 139 MB)
[Oct 17 15:38:32] iconv(): Detected an illegal character in input string (8) File: /home/jong5nw19fur/public_html/wp-content/plugins/wpforms-lite/vendor/symfony/polyfill-mbstring/Mbstring.php Line: 409
[Oct 17 15:38:32] Scanning contents: wp-content/plugins/revslider/public/assets/svg/image/ic_exposure_neg_2_24px.svg (Size: 679 B Mem: 139 MB)
[Oct 17 15:38:32] iconv(): Detected an illegal character in input string (8) File: /home/jong5nw19fur/public_html/wp-content/plugins/wpforms-lite/vendor/symfony/polyfill-mbstring/Mbstring.php Line: 409
[Oct 17 15:38:32] Scanning contents: wp-content/plugins/wpforms-lite/vendor/woocommerce/action-scheduler/classes/abstracts/ActionScheduler_Abstract_RecurringSchedule.php (Size: 3.1 KB Mem: 139 MB)
[Oct 17 15:38:32] Scanning contents: wp-content/plugins/jetpack/extensions/blocks/business-hours/editor.js (Size: 182 B Mem: 139 MB)
[Oct 17 15:38:32] Scanning contents: wp-content/plugins/revslider/public/assets/svg/editor/ic_strikethrough_s_24px.svg (Size: 1.07 KB Mem: 139 MB)
[Oct 17 15:38:32] iconv(): Detected an illegal character in input string (8) File: /home/jong5nw19fur/public_html/wp-content/plugins/wpforms-lite/vendor/symfony/polyfill-mbstring/Mbstring.php Line: 409
[Oct 17 15:38:32] Scanning contents: wp-content/plugins/jetpack/_inc/blocks/vendors~map/mapbox-gl.f81f5e1d3c950198407d.js (Size: 651.6 KB Mem: 139 MB)
[Oct 17 15:53:59] Calling Wordfence API v2.26:https://noc1.wordfence.com/v2.26/?k=fca5719f75cda5e48acd424c39d33001eddb5c003493468df291a73f9f8f15e76a6e126dfa47327274aa25beff62b8a07beb5dbd5e9697edafcac8ec83b905b16da7b70e6c63782da54547283c33037f&s=eyJ3cCI6IjYuNi4yIiwid2YiOiI3LjExLjciLCJtcyI6ZmFsc2UsImgiOiJodHRwczpcL1wvc29jaWV0eWZvcmRpc2FiaWxpdGllcy5vcmciLCJzc2x2IjoyNjk0ODg1MTEsInB2IjoiOC4zLjExIiwicHQiOiJsaXRlc3BlZWQiLCJjdiI6IjcuODcuMCIsImNzIjoiT3BlblNTTFwvMS4xLjF3Iiwic3YiOiJBcGFjaGUiLCJkdiI6IjEwLjYuMTgtTWFyaWFEQi1jbGwtbHZlIiwibGFuZyI6ImVuIn0&action=resolve_ips
[Oct 17 15:54:03] Calling Wordfence API v2.26:https://noc1.wordfence.com/v2.26/?k=fca5719f75cda5e48acd424c39d33001eddb5c003493468df291a73f9f8f15e76a6e126dfa47327274aa25beff62b8a07beb5dbd5e9697edafcac8ec83b905b16da7b70e6c63782da5454

Thanks for that. It doesn’t look like a scan is starting or getting anywhere at the moment. Are you still seeing a cURL error in the diagnostics? If so, you will need to expand the details, if you see an option, and copy over the entire cURL error. There may be a block at the server level.

If you don’t see a cURL error, please cancel any failed scans, give it a moment, refresh the page, then run a new scan until it fails. At that point, from the Scan page, use the Email activity log option to send that to wftest @ wordfence . com so I can check on the entire log. Also, grab the error log with the most recent date from Wordfence > Tools > Diagnostics > Log Files. After that, please check with GoDaddy or via your hosting panel for the most recent raw access logs and send those over with the error log to the email above.

Thanks,
Scott

Very strange. I don’t see any blocking. I had noticed that the client had purchased the GoDaddy Website Security plan which I immediately thought could be the issue and disabled the Firewall part of it.

I looked back at the cURL issue and there doesn’t appear to be any additional information offered there. No details to expand. I’ll provide images for each of these.

Additionally, I looked in their CPanel to ensure that no IP’s were added to the IP Blocker list.

Thanks for that, @jaypeg

I see your email came through with the diagnostics. The cURL error there is for IPv6, which may not be playing a role here.

Can you enable the Use only IPv4 to start scans option in Wordfence > Scan > Scan Options and Scheduling > Advanced Scan Options and try a scan to see if it gets anywhere?

I did not see the complete scan log come over from the Wordfence > Scan page (using the Email activity log option), just the diagnostics. If you do send those, please confirm here.

Thanks,
Scott

Thank you! That fixed it!

It is failing with the GoDaddy Firewall re-enabled, but that’s a different issue of course. Is it only 35.83.41.128, 52.25.185.95, and 54.148.171.133 that need to be allowed for WordFence?

Thank you,
Thomas

Thanks for confirming, @jaypeg .

That is correct, those are the IPs used for the plugin. Those IPs and our Central IPs can be found here (if you’re having any trouble connecting the site to Central) https://www.wordfence.com/help/advanced/

Keep in mind, in some cases, you may need to allowlist the server IP also to allow the site to connect back to itself. That may not be the case here, however, in some cases you may see cron jobs getting blocked and an issue connecting back to the site (non-IPv6). Making sure the server IP isn’t being blocked by and other firewalls in those cases can help.

Thanks
Scott

Terrific! Thank you very much for the excellent support.

All the best,
-Thomas