• View post on imgur.com

    All my wordpress websites hosted on Hostinger are giving the above mentioned issue. It’s weird because the scan completes fine but only the inital connection to wordfence servers isn’t happening.

    I have 4 websites on hostinger (all have this issue). I have more websites on Bluehost and Godaddy which don’t have the issue. All websites have the same wordfence/cloudflare settings. I’ve tried every possible configuration change at my end to fix it but haven’t been able to so far.

    The moment I clone a perfectly fine Bluehost website to Hostinger this issue occurs again so it definitely is a Host related issue. I tried getting in touch with Hostinger support, they were kind enough to switch the servers of my accounts but even after the switch this issue persists. I bought Hostinger package just 2 weeks ago but so far haven’t been able to get this wordfence issue sorted.

    Any help would be greatly appreciated. Thanks

    • This topic was modified 6 years, 11 months ago by ragzybwp73.
    • This topic was modified 6 years, 11 months ago by ragzybwp73.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Hi @ragzyb
    Please make sure you don’t have any issue in the “Ignored Results” tab in (Wordfence > Scan) page. Also, go to (Wordfence > Tools => Diagnostics) and click on “Send Report by Email” button at the top of the page, you can send the report to “alaa [at] wordfence [dot] com”, make sure to include your forum username, I will take a look at this report and let you know my findings.

    Thanks.

    Thread Starter ragzybwp73

    (@ragzyb)

    Thanks for replying. Thought this was gonna go missed.

    Just sent the report to the above mentioned email ID and made sure that I mentioned my username too. Please look into it. This is driving me crazy since hostinger says that wordfence works fine for everyone else.

    If you want I can send the same report with a brand new wordpress installation too (without any plugins whatsoever).

    Also ignored results says 0 ignored results.

    Edit – I sent the report with another domain on the same hostinger account too but this one uses php 7.1

    Also Please check the below screenshot, whenever I add a new wordpress install to my hostinger account, both these settings show as a red cross. For the new wordfence installation on hostinger, these waf rules files aren’t generated at all since the connection is not being established with your server.

    View post on imgur.com

    I’ve check the permissions of the wflogs several times too since wordfence runs flawlessly on my 10+ Godaddy and 10+ Bluehost websites. All settings are fine but on hostinger these files aren’t made with a fresh install. Since the reports were sent via cloned websites (I used updraftplus) you will find these wfrules file there.

    [ Please do not bump. ]

    • This reply was modified 6 years, 11 months ago by ragzybwp73. Reason: added more info

    Hi @ragzyb

    That’s a little bit strange, these are the scans/checks for issues related to “Server State”:

    – Scanning to check available disk space.
    – Scanning DNS for unauthorized changes.
    – Checking for future GeoIP support (PHP version check).
    – Checking for the most secure way to get IPs.

    To narrow down this issue to one of these scans, could you please start turning off “Scan for misconfigured How does Wordfence get IPs” option under (Scan > Scan Options and Scheduling > General Options) and run a new scan?

    Let me know how it goes,
    Thanks.

    Thread Starter ragzybwp73

    (@ragzyb)

    @wfalaa

    Ok so disabling that “How does wordfence get IPS” option solves the issue!

    Shall I keep it disabled from here on (on my hostinger websites that is) ? Does disabling it pose any security risk? please let me know. Thanks a ton for your help!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Hostinger And Wordfence Issue’ is closed to new replies.