• After the WP 5.6 upgrade we were seeing a new Site Health report “Your site could not complete a loopback request.”

    By process of elimination we tracked the source to iThemes. Turning off the Hide Backend function eliminates the warning, though the original purpose of the functionality is lost.

Viewing 5 replies - 1 through 5 (of 5 total)
  • @webcitymedia,

    Glad to know we’re not the only ones experiencing the same issue.

    Issue reported here.

    We have reached out to the iThemes Security plugin support team for assistance.

    Let’s hope they will fix this issue soon.

    Cheers!

    Thread Starter webcitymedia

    (@webcitymedia)

    Jetxpert I wanted to makes sure it got visibility after the resolved status. Looks like you were able to get it removed.

    @webcitymedia,

    We were trigger-happy when we closed the topic.

    We still have the issue as you’ll notice when you read the last two comments in that post. The moderator failed to re-open the topic.

    So, in short, we still need a fix. ??

    Cheers!

    @webcitymedia,

    Please refer to the link provided above for a temporary solution.

    We are still waiting for the plugin developer to address and fix this issue (permanent solution).

    Kudos to @nlpro!

    Cheers!

    Plugin Author Timothy Jacobs

    (@timothyblynjacobs)

    Hi All,

    This is a side effect of a change in WordPress 5.6. You can read more about the issue here: https://core.trac.www.ads-software.com/ticket/52097

    There isn’t a change to be made in iThemes Security at the moment, but we are looking at a change that could be made in WordPress Core.

    This can be considered a false positive, loopbacks to WP Cron continue to function as well as the file editor checks.

    If you see the Site Health error and an issue in iThemes Security’s loopback check in Security Check, then this is likely a separate issue that you should be concerned about.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Hide Backend Issue – WP 5.6 Update’ is closed to new replies.