“Page not found” with “Insert Headers and Footers” plugin

  • Resolved rhisflow

    (@rhisflow)


    5 years, 8 months ago

    Hi there,

    I have WF running on 2 different websites, and on one of them, I get the
    “Oops! Something went wrong. Page not found” error when I try to add or edit header or footer scripts via the Insert Headers and Footers plugin.
    Even if I don’t change anything and just hit save.

    Now, the curious thing is that when I do the same thing on the other site, I get that live firewall notification and can whitelist it.
    After having done that, editing things via the IHF plugin works flawlessly again.

    Why do I not get that live firewall alert with the option to whitelist on the other site?

    Shouldn’t it at least show up in the live traffic section as “blocked” (it doesn’t)?

    The strange thing is, even after adding the same firewall whitelist entries which I whitelisted as false-positive on the other site, nothing changes.

    When using a different Header Footer plugin, I can make changes without problems.

    Any suggestions?

    Thank you!

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

  • Hey @rhisflow,

    Can you please switch the Firewall to Learning Mode and let me know if it helps?

    https://www.wordfence.com/help/firewall/learning-mode/

    Please let me know how it goes.

    Thanks,

    Gerroald

    Thread Starter rhisflow

    (@rhisflow)

    Hi Gerroald,

    thanks for your reply and sorry for not mentioning that earlier.
    I did of course try that, even disabling the Firewall completely.
    To no avail.

    Thanks!
    Florian

    Hey @rhisflow,

    Thanks for the update.

    Just to be certain, if you completely disable Wordfence does it resolve the issue?

    Please let me know.

    Thanks,

    Gerroald

    Thread Starter rhisflow

    (@rhisflow)

    Even disabling the WF plugin doesn’t resolve it.

    Thanks,
    Florian

    Hey @rhisflow,

    If disabling Wordfence doesn’t resolve it I believe your issue is going to be elsewhere.

    Can you try temporarily switching to a default theme if you’re not already using one and disabling all other plugins then reactivating them one by one to see if the issue persists?

    To do so I recommend the Health Check & Troubleshooting plugin which allows you to disable all plugins and switch to a default theme, but only for your user.

    Thanks,

    Gerroald

    Thread Starter rhisflow

    (@rhisflow)

    Thanks for your advice.

    That’s actually what I did right away, after first having tried disabling only WF.

    I’m using twenty seventeen anyway.

    Here’s what I did specifically:

    – Enter troubleshooting mode (with the Health Check & Troubleshooting plugin)
    – Enabling only the Insert Headers & Footers plugin
    – Hitting “Save” within IHF plugin (without making any changes)

    Turns out, even with only that single Plugin and a standard theme running, the “page not found” issue still persists.

    I was thinking this is because WF is so deeply integrated, with some “deny all” lines in the .htaccess and so on, that it is still caused by it.

    But I’d rather not completely uninstall it since I appreciate what it does.

    So that’s really odd I think, that there’s obviously no other plugin or theme causing the issue (as a result of that troubleshooting mode test).

    At the same time, the IHF plugin itself cannot be the issue either, since it’s working fine on my other website (as I originally explained).

    Thanks for your help!

    Hey @rhisflow,

    Unfortunately, if disabling Wordfence doesn’t resolve the issue I don’t believe it’s contributing to it.

    I’m not familiar with this plugin. And if disabling all other plugins doesn’t help it’s likely going to be a site/server/plugin configuration issue. My best suggestion is to contact their support for their thoughts.

    Please let me know how it goes.

    Thanks,

    Gerroald

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘“Page not found” with “Insert Headers and Footers” plugin’ is closed to new replies.