What ports does the agent require?

The agent itself does not listen on any ports, so there is no need to punch any holes in your firewall. However, if your corporate network blocks outbound ports, then a small change is required.

Please note: This is a TLS connection and it is not HTTP-based and therefore cannot be sent through a Proxy Server.

General Traffic Considerations

All ports must allow traffic in two directions. The recommended setup is to configure traffic rules as outbound. An outbound connection starts from the inside and once established, bidirectional traffic is allowed, unlike an outgoing connection, where only traffic going outside is allowed. Bidirectional traffic also enables the communication but is discouraged for cybersecurity reasons.

US Cluster (app.ardexa.com)

Mandatory

The agent needs to contact broker.ardexa.com on TCP port 5671 .

Optional

While the agent is fully functional without the following ports, these dedicated outbound ports enable additional functionality and increased performance.

• SFTP: sftp.ardexa.com port22/tcp

• Tunnel: remote.ardexa.com port 7475/tcp

  • Please note that this URL will change IP depending on your geographic region

• VPN: remote.ardexa.com port 7475/udp

  • Please note that this URL will change IP depending on your geographic region

  • VPN will not work without this outbound port being open

EU Cluster (eur1.ardexa.com)

Mandatory

The agent needs to contact broker-eu.ardexa.com on TCP port 5671.

Optional

While the agent is fully functional without the following ports, these dedicated outbound ports enable additional functionality and increased performance.

• SFTP: sftp-eu.ardexa.com port 22/tcp

• Tunnel: remote.ardexa.com port 7475/tcp

  • Please note that this URL will change IP depending on your geographic region

• VPN: remote.ardexa.com port 7475/udp

  • Please note that this URL will change IP depending on your geographic region

  • VPN will not work without this outbound port being open