Domain Name Fails with WordFence Installed!

  • Resolved graftedin

    (@graftedin)


    5 years, 9 months ago

    I’ve made this change (I’m sure) with wordfence installed before. It seems you have a rats nest of hard coded domains in various config files that automatic domain changers would miss. I’ve tried just renaming the plugin directory but the hard coded dev domain is still buried in enough places the whole site will not load.

    This is so common to have dev domains I would think you would create a system that can change domains. At the very least have a post that can be found by google telling where all of these spots are.

    Actually…..its the directory that’s hard coded. UGGG!!!!! Who does this?!

Viewing 5 replies - 1 through 5 (of 5 total)

  • Hey @graftedin,

    I’m sorry to hear that you’ve run into an issue.

    If you are moving your site to a new server we recommend that you first remove extended protection. When your site has been migrated, you will then optimize the Firewall again. This is by design as it’s domain specific.

    https://www.wordfence.com/help/advanced/remove-or-reset/#migrate-with-wordfence

    Please let me know if this helps.

    Thanks,

    Gerroald

    Thread Starter graftedin

    (@graftedin)

    This was not a server move. This was moving public_html to bac.my-domain.com and dev.my-domain.com to public_html. The issue was not the domain as I pointed out in my last statement. Its because you have the server path to the site saved in multiple locations.

    However because I thought this was a domain issue and not a path issue I was searching for the wrong solution. Hopefully now with this post others won’t miss this.

    What I don’t understand is how having this path saved in config files makes the site more secure. And if it really doesn’t make the site more secure then its an unnecessary hurdle we have to get over if we have to move sites.

    Hey @graftedin,

    Thanks for the update.

    The php.ini/user.ini files are used to set PHP configurations. We use the auto_prepend function to make sure the Wordfence Application Firewall runs before all code (in case there’s malicious code) on the site. The auto_prepend function needs the path to the root directory where the wordfence-waf.php resides to start the Firewall.

    https://www.wordfence.com/help/firewall/optimizing-the-firewall/

    I hope this helps.

    Thanks,

    Gerroald

    Thread Starter graftedin

    (@graftedin)

    Then is it possible to have this error be reported better so if someone does get caught by surprise by this problem they can quickly fix it.

    Imagine launching a new site for a high profile client only to have it broken for the first hour while you are trying to figure out what went wrong. Not to mention the time I wasted yesterday trying to fix this. What should have been a 5 minute operation to make a site live turned in to an hour+.

    The solution is already posted publicly so what’s the harm of having this error printed to the browser to take the guess work out of the solution?

    Hey @graftedin,

    My apologies for the delayed response.

    I understand how this could be useful and I’ll definitely file a feature request for it.

    Thanks,

    Gerroald

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Domain Name Fails with WordFence Installed!’ is closed to new replies.