Skip to content

Network and ports

CVEDIA-RT will have to download models from the internet the first time you use them. After that they will be stored in a local cache.

Besides that CVEDIA-RT can provide optional services that may require some specific ports to be open:

Port list

Port Type Description Configuration
1883 TCP MQTT daemon When running within docker with MQTT support, we spawn our own instance; Can be overrided using options on run.sh
3333 UDP broadcast ONVIF discovery Not configurable
3546 TCP HTTP REST API / WEBPANEL Can be configured using options on run.sh or in rtconfig.json
3702 UDP broadcast ONVIF discovery Not configurable
7001 TCP When running VMS: NX Witness / Digital Watchdog / WAVE / Piko / Meta VMS Not configurable
8080 TCP HTTP REST API Can be configured at rtconfig.json or run.sh (on docker)
8086 TCP Tracy Tracy profiler for debugging
8554 TCP/UDP RTSP Used when broadcasing RTSP from CVEDIA-RT, depends on solution / instance export configuration
8889 TCP Remote UI Can be configured at rtconfig.json or run.sh (on docker)
9993 TCP/UDP ZeroTier When support mode is enabled on CVEDIA-RT boxes / images
12349 UDP broadcast CVEDIA-RT discovery Can be configured at rtconfig.json
59997 UDP broadcast CVEDIA-BOX debug alternative channel env, .env setup
59999 UDP broadcast CVEDIA-BOX debug main channel env, .env setup

Domain whitelist

Domain Ports Description Usage
api.cvedia.com 80, 443 CVEDIA internal APIs Essential
bin.cvedia.com 443 Windows installer Only when installing / upgrading
docker.io 443 Linux docker image repository Only when installing / upgrading
apt.cvedia.com 80, 443 Linux deb repository Only when installing / upgrading

Note

Port 80 is used as default, this allows devices without an accurate RTC to work. If you're in a restricted network that enforces HTTPS, check rtconfig.json documentation.