• Resolved jonathan50

    (@jonathan50)


    I discovered yesterday that people can’t comment on my site (I’m using Jetpack comments). When I tried myself, although the comment field is showing, after you press “post”, the field returns a “This site can’t be reached 127.0.0.1 refused to connect” error.

    I read somewhere that this might be solved by disabling the firewall in AIOWPS, so that’s what I did—and sure enough, now the comments can be posted OK. But AOIWPS says that the firewall is part of the four minimum security measures that I should enable. Is there a way of protecting the ability to comment while keeping the firewall enabled?

    I’ve temporarily disabled the firewall to enable comments, so there’s no point in giving the page address—and it affects all posts the same way.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor mbrsolution

    (@mbrsolution)

    Hi, start enabling one by one the firewall features and at the same time you enable a feature carry out a test. Do this until you run into the culprit feature.

    Let me know how you go.

    Thank you

    Thread Starter jonathan50

    (@jonathan50)

    Hi that’s really helpful, thank you — I’d forgotten about that tab in the options. I can now retain the minimal firewall without the same problem occurring, which is great. I can’t tell which feature it might have been that caused the problem, because somehow the process of turning the minimum firewall off and on solved the problem first time around.

    I installed a new third-party theme a few months ago, I’m wondering whether some settings got overwritten by the theme in the process of the changeover. Anyway it seems fine now, and I know what my options are for isolating a problem should it happen again, thank you.

    • This reply was modified 4 years, 3 months ago by jonathan50.
    Plugin Contributor mbrsolution

    (@mbrsolution)

    I am glad to know you managed to fix your issue ??

    I am marking this thread as resolved.

    Enjoy the plugin.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Firewall causing “this site can’t be reached” error’ is closed to new replies.