Outbound network requirements
If your pods are on premise and you block outbound connections, you will need to allow the ports in the first table.
The second table is required for all clients of the Premium Parsec connection service whether on premises or hosted.
Inevidesk connections (all customers)
| Host | Port | Description |
|---|---|---|
| api.inevitech.uk | 443 | API used for all components |
| q.inevitech.uk | 9672 | AMQP(s) (rabbitmq) used by node, vdesk, AD agents |
| q.inevitech.uk | 51833 | MQTT(s) used for all components |
| q.inevitech.uk | 25675 | MQTT(s) (over WSS) in browser (admin portal) |
| ssh.inevitech.uk | 2525 | SSH tunnel for support and maintenance |
| ssh.inevitech.uk | 2526 | SSH tunnel for support and maintenance |
| access.inevidesk.uk | 3222 | On-demand SSH tunnel for vdesk maintenace mode |
| monitor.inevitech.uk | 10051 | Pod monitoring |
Parsec connections (Parsec customers only)
| Host | Port | Description |
|---|---|---|
| kessel-ws.parsec.app | 443 | Parsec WS API |
| kessel-ws.parsec.app | 443 | Parsec API |
| builds.parsec.app | 443 | Parsec Updates |
| builds.parsecgaming.com | 443 | Parsec Updates |
| stun.parsec.app | 3478 (UDP) | STUN |
| stun6.parsec.app | 3478 (UDP) | 3478 (UDP) |