[en] Configure firewalls for network triggers

La traduction officielle n'est pas encore disponible.

[en] Problem

[en] The term network trigger identifies a trigger that runs in TCP/IP protocol. In Automation, such triggers are TCP/IP trigger, HTTP trigger, and Web Service trigger. These triggers provide network service and are bound to the network interface card, its IP address, and configured port number. When you deploy and start network triggers in Automation Manager, the triggers start listening on the port for inbound traffic.

[en] Firewalls protect computers from unauthorized attempts of incoming connections. NiceLabel installer allows Windows Firewall to establish inbound communication to all ports owned by Automation Service.


[en] Automation Service owns ports configured for TCP/IP triggers, but not ports defined for HTTP trigger and Web Service trigger. These ports are bound to process ID 4 (SYSTEM), not to the Automation Service process.

[en] Solution

[en] Configure the firewall to allow communication to ports configured for HTTP and Web Service triggers.

  1. [en] On the computer that is running NiceLabel Automation, go to the Start > Control Panel > System and Security > Windows Firewall.

  2. [en] Click Advanced settings.

  3. [en] Go to Windows Firewall with Advanced Security > Inbound Rules, and then in the Actions pane, click New Rule.

  4. [en] On the Rule Type tab, select Port, then click Next.

  5. [en] Select Specific local ports, and insert the port number on which your HTTP or Web Service trigger runs.

  6. [en] Click Next.

  7. [en] Select Allow the connection, then click Next.

  8. [en] Select the profiles, then click Next.

  9. [en] Type your name for the rule, then click Finish.

[en] The process is similar for third-party firewalls.