brand new site can’t scan

  • Resolved Deleyna

    (@deleyna)


    1 year, 1 month ago

    I have a brand new install on a SiteGround server that has nothing on it except Wordfence and SG’s default plugins. SSL is installed. I’ve deleted the install and rebuilt it twice now. This site will not scan. I’m getting cURL error 28. I’ve tried starting all scans remotely. I’m baffled. I have never had a problem with Wordfence + SiteGround before. Brand new site, brand new account. This is my favorite base to start building on, have done hundreds of these. Haven’t seen this before. Help? Thoughts?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter Deleyna

    (@deleyna)

    I’m aware that what I’m about to relay probably isn’t relevant. However, this was what SiteGround support found:

    ————

    I found that the request made from the WordFence scanner is coming from a very old user agent:

    Chrome/33.0.1750.152

    The request is then blocked by our Anti-Bot AI. In this case, please contact the support of WordFence so they can set more modern User Agent.

    ————–

    Meanwhile, they created a staging site that worked fine… just like all of my other SiteGround sites that are running WordFence without any problems. I’d appreciate any help you can give me in sorting this out because there are a couple of email addresses attached to this site and I’d rather not delete it if there’s a way around it.

    Thread Starter Deleyna

    (@deleyna)

    I gave up and just deleted the whole site. Installed a new one. Seems fine. I’d love it if anyone could explain to me what might have happened here.

    Plugin Support wfpeter

    (@wfpeter)

    Hi @deleyna, we usually don’t man the forums during the weekends ourselves, so apologies for the slightly delayed response.

    Our _wfsf=detectProxy?requests do use an old User-Agent as they’ve spotted. In the past we saw hosts blocking User-Agents that don’t look like they were from a real browser. We have a case open to change it to its own unique User-Agent due to these kind of blocks for older browsers being more common now.

    cURL error 28 is usually seen with intermittent connectivity issues, meaning the host’s own block could have been linked. It can also be linked to available resources, so if they’ve restarted your server while looking into the issue, this could’ve also fixed it.

    Thanks,
    Peter.

    Thread Starter Deleyna

    (@deleyna)

    No worries at all. It is just bizarre because I’ve never had problems with this host before, and after deleting the install completely (not just WordPress, but the entire website account), when I created it new, it worked out of the box just like normal.

    So yay for addressing that issue, but I still think there was something else going on with this site install.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘brand new site can’t scan’ is closed to new replies.