Each server module of Gravio’s HubKit, the Update Manager, and the Coordinator use the following ports:
• Inbound (Gravio 5.1)
Service Name / Process Name | Protocol | Port |
——————————————- | ————— | ——— |
Configuration Manager (web application) | HTTP | 8080 |
Coordinator (include Gavio HubKit ) | HTTPS | 443 |
Gravio App Service | HTTPS | 29443 |
Endpoint for IVAR | HTTPS | 29448 |
• Inbound (Gravio 5.0)
Service Name / Process Name | Protocol | Port |
——————————————- | ————— | ——— |
Configuration Manager (web application) | HTTP | 8080 |
Coordinator (web application) | HTTPS | 443 |
Gravio Control Manager | HTTPS | 29442 |
Gravio App Service | HTTPS | 29443 |
Endpoint for IVAR | HTTPS | 29448 |
• Outbound
Service Name | Protocol | Port |
——————— | ————— | ——— |
DNS | UDP/TCP | 53 |
NTP | UDP | 123 |
HTTPS Server | HTTPS | 443 |
When installing HubKit and Gravio Studio on a separate PC, it is necessary to open the port for “Gravio Control Manager – HTTPS: 29442” in the firewall among these port numbers.
When using HubKit and Chrome cast, it is necessary to open the port for “Gravio App Service – HTTPS: 29443” on the PC where HubKit is installed among these port numbers.
Need more help with this?
Join our slack community for help