Support » Plugin: NinjaFirewall (WP Edition) - Advanced Security Plugin and Firewall » Which connections need to be allowed for rules updates to work?

  • Resolved Christoph

    (@monigc)


    Thank you for your great product. 🙂

    On our site, the Rules Updates fail with the following error:

    “Error: Unable to connect to the remote server (cURL error 28: Connection timed out after 10000 milliseconds)”

    I understand why this is happening:

    Our Website is placed inside of a DMZ protected by a firewall,
    which is set to deny every outgoing connection except the connections that
    Wordpress asked for, for security upgrades etc.

    While activating the Ninja Firewall plugin the activation failed
    because the connections to “plugins.svn.wordpress.org” was denied.
    After enabling that connection, the activation worked.

    Now I see that the automated firewall rules update fails because
    the IP “88.198.154.149” can’t be reached.
    I’ve seen that this is nintechnet.com.

    Is there a list which states which connections
    need to be allowed for Ninja Firewall to operate?

    Are additional connections required for the premium version?

    Thank you very much in advance.

    Best regards,

    Christoph

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author nintechnet

    (@nintechnet)

    WP and WP+ Edition:
    1. blog.nintechnet.com
    It is used by the “news widget”. But it can be disabled in the Firewall Options page.

    2. updates.nintechnet.com
    Security rules updates.

    3. Your site.
    During the Full WAF installation, the firewall’s sandbox will connect back to your site after the installation to make sure there no fatal error or will undo the modifications.

    WP+ Edition only:
    -wordpress.nintechnet.com
    Plugin update.

    -translate.wordpress.org
    Translation files downloaded from wordpress.org.

    So far all our subdomains use the same load-balancer IP but that may change in the future. Make sure also to whitelist IPv6 too (currently 2a01:4f8:c0c:61cc::1).

    Thread Starter Christoph

    (@monigc)

    Thank you very much for the quick response,
    this has been very helpful. 🙂

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.