• WF will not scan on staging site, it is fialing, in the docs I found this

    “Make sure you do not have an “Under Construction” plugin running that is blocking access to the WordPress AJAX handler.?“

    But we must do this because it is a staging site and not publicily accessible?

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

    (@wfpeter)

    Hi @lordsnake,

    Things like scans and rules updates will not complete successfully if the staging site isn’t public-facing as our servers won’t be able to connect in. This can be overcome by allowing specific ports or making firewall allowances at your discretion, depending on the platform where the staging site is running.

    As removing firewall optimization is recommended prior to migrating/cloning (along with registering a new free Wordfence key if the staging domain doesn’t resemble the live site’s domain), many customers disable the plugin when working with staging/local environment where connectivity will be an issue. Just as a note, we are unable to support Wordfence on local or Windows environments but those may not be applicable in your case.

    Thanks,
    Peter.

    Thread Starter lordsnake

    (@lordsnake)

    Hi,

    The staging site is public on the internet, we just use a plugin to restrict access, so you have to login to view it.
    This doesn’t negate the need for Wordfence, any vulnerabilities would still exist and could still be leveraged by a bad actor.
    So disbling wordfence would be bad idea.

    Please advise what these specific ports and firewall allowances are that you said are available to work around this.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘how to scan staging site’ is closed to new replies.