Firewall Configuration
This document outlines the network port requirements for Reality Hub Server and Reality Engine installations. Proper firewall configuration is essential for the Reality 5.6 ecosystem to function correctly.
Firewall Configuration Summary
For Reality Hub Server
- Allow Incoming: TCP 80, 443 (if SSL), 6001
- Allow Outgoing: TCP 50052, 30020, 30030 (to engines), TCP 443 (to hub.zerodensity.tv)
For Reality Engines
- Allow Incoming: TCP 50052, 30020, 30030
- Allow Outgoing: TCP 6001, 9090, 80, 443 (to Reality Hub Server), UDP dynamic ports (to Reality Hub UI hosts)
Port Requirements
| Location / Context | Port(s) | Protocol | Direction | Purpose / Description |
|---|---|---|---|---|
| Reality Hub Server | TCP 80 (443 if SSL is configured) | TCP | Incoming | Browser access |
| Reality Hub Server | TCP 6001 | TCP | Incoming | Reality Loader connection |
| Reality Hub Server | TCP 50052, 30020, 30030 | TCP | Outgoing | Communication to Reality Engines |
| Reality Hub Server → WAN | TCP 443 (hub.zerodensity.tv) | TCP | Outgoing | License server connection |
| On Engines | TCP 50052 | TCP | Incoming | Nodos API port |
| On Engines | TCP 30020 | TCP | Incoming | Reality Engine Remote Control API |
| On Engines | TCP 30030 | TCP | Incoming | Motion Design API |
| On Engines | TCP 6001 | TCP | Outgoing | Communication to Reality Hub Server (from Reality Loader) |
| On Engines | TCP 9090 | TCP | Outgoing | Communication to Reality Hub Server |
| On Engines | UDP (dynamic ports) | UDP | Outgoing | Required for APM communication to hosts running Reality Hub UI |
| On Engines | TCP 80 (443 if SSL is configured) | TCP | Outgoing | Access to Reality Hub Server browser/API interface |
info
The Reality Hub Server must be able to establish outgoing connections to all Reality Engines on ports 50052, 30020, and 30030. These connections are essential for engine control and communication.
important
UDP Dynamic Ports: Reality Engines require UDP communication on dynamic ports for APM functionality. Ensure your firewall allows outbound UDP traffic to hosts running Reality Hub UI.
Troubleshooting
Common Issues
- Engine Connection Failures: Verify that Reality Hub Server can reach engines on ports 50052, 30020, and 30030.
- Reality Loader Disconnection: Check that port 6001 is open for incoming connections on Reality Hub Server.
- APM Not Working: Ensure UDP dynamic ports are allowed for outbound traffic from engines to Reality Hub UI hosts.
- License Issues: Verify that Reality Hub Server can reach hub.zerodensity.tv on port 443.