Server Inbound/Outbound Connections Required to Install and Run AlgoTrader

The server on which AlgoTrader runs, needs to be installed/run should be allowed to initialize connections to anywhere on the internet to be able to

• Install the application (download artifacts etc.)
• Run the application (connect to exchanges/brokers, validate licenses etc.)

 We could list the outbound IPs required to operate AlgoTrader but when it comes to exchange/broker connectivity, it is out of our control and they could easily change their IPs.

Inbound Access to AlgoTrader should be allowed at least for the ports below from any IP that needs to be able to access AlgoTrader (API access and/or browser connection):

• 443 - (required) HTTPS, Browser access (via SSL)
• 80 - HTTP, Browser access (typically only required for test environments)
• 9090 - HTTP, Standard Algotrader browser access setting (typically only required for test environments)
• 61613 - (required) TCP, ActiveMQ Secure WebSocket Port
• 61614 - TCP, ActiveMQ WebSocket Port (typically only required for test environments)
• 8444 - (required) HTTPS, KeyCloack auth (via SSL)
• 8081 - HTTP, KeyCloack auth (typically only required for test environments)
• 3000 - (required) HTTP, Grafana dashboards browser access
• 9880 - FIX API
• 61617 - TCP, ActiveMQ Stomp Port (typically only required for test environments)
• 61618 - TCP, ActiveMQ Secure Stomp Port 
• 3306 - TCP, MySQL Database (typically only required for test environments)
• 8086 - TCP, InfluxDB Database (typically only required for test environments)
• 1198 - TCP, RMI Service Port
• 1199 - TCP, RMI Remote Port

For distributed strategy usage, Hazelcast cluster members must see each other's subnets (meaning any port should be accessible for them i.e., a VPN needs to be set up or all ports opened).