Scan Failed – 502

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @danishhaidri, thanks for getting in touch.

    Are you seeing this on a new installaton or has the plugin previously been working and recently started to display this error? Also, have you already tried any steps on the, “Click here for steps you can try” hyperlink in the message? This is just to avoid retreading any troubleshooting steps you’ve already tried.

    Thanks,
    Peter.

    Thread Starter CamZL1

    (@danishhaidri)

    Hi @wfpeter,

    We have just moved to LiteSpeed server + cache and this is the first time we came across this. We have been using WF for years on NGINX and never had any problems. Yes, we did explore the steps and looked at the timeouts.

    • This reply was modified 1 year, 1 month ago by CamZL1.
    Plugin Support wfpeter

    (@wfpeter)

    Hi @danishhaidri,

    With Litespeed, noabort code usually needs to be added to stop communication stopping abruptly – usually during scans: https://www.wordfence.com/help/advanced/system-requirements/litespeed/

    That may remedy what you’ve been seeing. If not, send us a diagnostic report to us at wftest @ wordfence . com directly using the link 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 again,
    Peter.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Scan Failed – 502’ is closed to new replies.