Scan terminated with error: WpOrg\Requests\Transport\Curl::request()

  • Resolved cc-mail

    (@cc-mail)


    1 year, 11 months ago

    Hi there,
    the Wordfence scan shows the following error after a few seconds:

    [Apr 06 13:51:57:1680781917.697647:2:error] Scan terminated with error: WpOrg\Requests\Transport\Curl::request(): Argument #3 ($data) must be of type array|string, boolean given

    WordPress 6.2
    Wordfence 7.9.2

    I tried the tips from https://www.wordfence.com/help/scan/troubleshooting, also uninstalled Wordfence completely with all tables and data and then reinstalled it.

    Start scan remotely: unchecked / checked

    I’ll send the diagnostic report to [email protected].

    Thank you for help,
    Chris

    The page I need help with: [log in to see the link]

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Support wfjanet

    (@wfjanet)

    Hi @cc-mail,

    Thank you for reaching out.

    If you could do the following steps for me please:

    • 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.

    Let me know if you have any questions!

    Thanks,

    Janet

    Thread Starter cc-mail

    (@cc-mail)

    Hi Janet,
    thanks for your response and support!

    [Apr 09 02:33:21:1681000401.277254:10:info] SUM_KILLED:Previous scan terminated with an error. See below.
[Apr 09 02:33:21:1681000401.277015:2:error] Scan terminated with error: WpOrg\Requests\Transport\Curl::request(): Argument #3 ($data) must be of type array|string, boolean given
[Apr 09 02:33:20:1681000400.560945:4:info] Calling Wordfence API v2.26:https://noc1.wordfence.com/v2.26/?k=64e0127a9c87eb6bcd5bed912798258c450e0dee428e5981fd3cbe17a47e0ef171c6c4f1d5eb7ce12f5cd1dc8b8a1339&s=eyJ3cCI6IjYuMiIsIndmIjoiNy45LjIiLCJtcyI6ZmFsc2UsImgiOiJodHRwczpcL1wvbG91cml6LmRlIiwic3NsdiI6MjY5NDg4MTkxLCJwdiI6IjguMC4yOC1oZS4wIiwicHQiOiJhcGFjaGUyaGFuZGxlciIsImN2IjoiNy42NC4wIiwiY3MiOiJPcGVuU1NMXC8xLjEuMW4iLCJzdiI6IkFwYWNoZSIsImR2IjoiNS43LjQxLTQ0LWxvZyIsImxhbmciOiJkZV9ERV9mb3JtYWwifQ&action=record_scan_metrics
[Apr 09 02:33:20:1681000400.560091:10:info] SUM_ENDERR:Fetching core, theme and plugin file signatures from Wordfence
[Apr 09 02:33:20:1681000400.559490:4:info] Calling Wordfence API v2.26:https://noc1.wordfence.com/v2.26/?k=64e0127a9c87eb6bcd5bed912798258c450e0dee428e5981fd3cbe17a47e0ef171c6c4f1d5eb7ce12f5cd1dc8b8a1339&s=eyJ3cCI6IjYuMiIsIndmIjoiNy45LjIiLCJtcyI6ZmFsc2UsImgiOiJodHRwczpcL1wvbG91cml6LmRlIiwic3NsdiI6MjY5NDg4MTkxLCJwdiI6IjguMC4yOC1oZS4wIiwicHQiOiJhcGFjaGUyaGFuZGxlciIsImN2IjoiNy42NC4wIiwiY3MiOiJPcGVuU1NMXC8xLjEuMW4iLCJzdiI6IkFwYWNoZSIsImR2IjoiNS43LjQxLTQ0LWxvZyIsImxhbmciOiJkZV9ERV9mb3JtYWwifQ&action=get_known_files
[Apr 09 02:33:20:1681000400.559004:10:info] SUM_START:Fetching core, theme and plugin file signatures from Wordfence
[Apr 09 02:33:20:1681000400.553023:2:info] Found 3 themes
[Apr 09 02:33:20:1681000400.552072:2:info] Getting theme list from WordPress
[Apr 09 02:33:20:1681000400.551868:2:info] Found 13 plugins
[Apr 09 02:33:20:1681000400.550064:2:info] Getting plugin list from WordPress
[Apr 09 02:33:20:1681000400.549856:2:info] Including files that are outside the WordPress installation in the scan.
[Apr 09 02:33:20:1681000400.545682:10:info] SUM_ENDOK:Checking for paths skipped due to scan settings
[Apr 09 02:33:20:1681000400.543279:10:info] SUM_START:Checking for paths skipped due to scan settings
[Apr 09 02:33:20:1681000400.537253:10:info] SUM_ENDOK:Checking for future GeoIP support
[Apr 09 02:33:20:1681000400.534999:10:info] SUM_START:Checking for future GeoIP support
[Apr 09 02:33:20:1681000400.529116:10:info] SUM_ENDOK:Checking Web Application Firewall status
    Plugin Support wfjanet

    (@wfjanet)

    Hi @cc-mail,

    Thank you for sending this.
    Can you send 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: It should look as follows – Screenshot of Tools > Diagnostic > Send by Email

    Thanks,
    Janet

    Thread Starter cc-mail

    (@cc-mail)

    Hi Janet,
    I just sent a new diagnostic report to you, you’ve already received a report with my first message.
    Regards,
    Chris

    Plugin Support wfjanet

    (@wfjanet)

    Hi @cc-mail,

    I took a look at the second diagnostic that you shared, and the connectivity to our servers and back to your site looks good.

    From the diagnostic, it looks like the most recent scan was successful today. Can you please confirm?

    Let me know what you find.

    Thanks,

    Janet.

    Thread Starter cc-mail

    (@cc-mail)

    Hi Janet,
    it’s always the same, the scan stops right at the beginning with the error message. The function expects the third argument/variable ($data) to be an array/string, but it returns as boolean(true/false).

    [Apr 13 09:13:49:1681370029.692573:2:error] Scan terminated with error: WpOrg\Requests\Transport\Curl::request(): Argument #3 ($data) must be of type array|string, boolean given
[Apr 13 09:13:48:1681370028.977578:2:info] Found 3 themes
[Apr 13 09:13:48:1681370028.972722:2:info] Getting theme list from WordPress
[Apr 13 09:13:48:1681370028.972490:2:info] Found 13 plugins
[Apr 13 09:13:48:1681370028.969498:2:info] Getting plugin list from WordPress
[Apr 13 09:13:48:1681370028.969258:2:info] Including files that are outside the WordPress installation in the scan.

    What else can I do?
    Thanks,
    Chris

    Plugin Support wfjanet

    (@wfjanet)

    Hi @cc-mail

    Thank you for your patience.

    I had our Dev team look into this. We suspect the issue is being caused by  the U with an umlaut in the custom theme’s Version header, that is not encoded as UTF-8. Wordfence depends on looking up version numbers but text that is not UTF-8 can’t be encoded properly.

    We may have a workaround for this in a future Wordfence version but the simplest solution for now is removing the U from the theme’s Version header, and trying the scan again.

    Let me know how it goes.

    Thanks,

    Janet

    Thread Starter cc-mail

    (@cc-mail)

    Oh wow – I would never have thought of that and have really done intensive troubleshooting…

    Great, thank you very much!! I’m happy!!!

    Plugin Support wfjanet

    (@wfjanet)

    You’re welcome @cc-mail

    Happy to help ??

    Thanks,

    Janet

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Scan terminated with error: WpOrg\Requests\Transport\Curl::request()’ is closed to new replies.