FirewallD is my active firewall, however, mxtoolbox tcp:<server_external_ipaddress>:2304 "refused"

1 post / 0 new
#1 Sun, 05/05/2019 - 18:39
adamjedgar

FirewallD is my active firewall, however, mxtoolbox tcp:<server_external_ipaddress>:2304 "refused"

I am trying to see if a port i have opened in firewalld is actually accessible from outside.

The reason for this is because i have had some problems with automatic provisioning modules (Blesta) accessing the server to interract with it for user accounts and webhosting services.

Webmin>Networking>FirewallD>Public (default)

added allowed port "2304"

A check of firewall rules returns the following:

firewall-cmd --list-all
public (active)
  target: default
  icmp-block-inversion: no
  interfaces: ens3 lo
  sources:
  services: ssh dhcpv6-client smtp smtps ftp pop3 pop3s imap imaps http https
  ports: 587/tcp 53/tcp 20/tcp 2222/tcp 10000-10100/tcp 20000/tcp 1025-65535/tcp 53/udp 2304/tcp
  protocols:
  masquerade: no
  forward-ports:
  source-ports:
  icmp-blocks:
  rich rules:

However, if i run a tcp scan using mxtoolbox

tcp:<server_public_ipaddress>:2304

i get "refused"

So my understanding is that there are two reasons for this... 1. the port is blocked 2. nothing is listening on said port

I am running both blesta and whmcs on different virtual sub servers. How can i check whmcs and blesta are able to communicate in or out of the firewall through this port whenv provisioning services on other external systems?