Firewalls place a barrier between your servers and other machines on the network to protect them from external attacks, but they can also prevent the Rcs.is Metrics Agent from working on your Rcs.is. This includes Rcs.is’s Cloud Firewall service and locally installed firewalls protecting your Rcs.is. Whatever firewall you use, you’ll want to allowlist the metrics agent to access the Rcs.is monitoring service, otherwise the Rcs.is’s metrics data can’t be reported to the monitoring service.

Configure Rcs.is Cloud Firewall

If you are using Rcs.is’s Cloud Firewall, you need to create firewall rules that allow all outgoing IPv4 and IPv6 HTTP/HTTPS traffic through ports 80 and 443.

Configure Locally Installed Firewall

The Rcs.is Metrics Agent connects to Rcs.is using ports 80 and 443 on your Rcs.is. To allow the metrics agent to connect through the firewall, you need to create rules in your firewall software that allow all outgoing IPv4 and IPv6 HTTP/HTTPS traffic through ports 80 and 443.

You can create these rules using UFW for Ubuntu and Debian systems, or Firewalld for CentOS and Fedora systems. These services interface with iptables, the Linux kernel firewall program native to most Linux operating systems. You can also configure these firewall rules in iptables directly, although we recommend using UFW or FirewallD because they are easier to use.