The details below are directly from this article.
To ensure that your Wowza ClearCaster operates as intended, review the following details with your network administrator to verify access to required servers and services through expected ports.
Note: All connections are initiated through an outbound request.
Wowza ClearCaster delivers data to the following ports.
|Port 443||RTMPS and HTTPS delivery|
|Port 80||HTTP delivery|
|Port 1935||RTMP delivery|
|Port 1884||MQTT messaging for all ClearCasters v126.96.36.199 and later|
|Port 123||Time synchronization services (NTP)|
Wowza ClearCaster uses the following outgoing services and ports.
|Service||Port / URI||Functionality|
|clearcaster.wowza.com||TCP port 443||Remote administration interface|
|connect.clearcaster.wowza.com||TCP port 1884||MQTT messaging|
|*.entrypoint.cloud.wowza.com||TCP port 1935||Sending broadcasts to Wowza Streaming Cloud|
|graph.facebook.com||TCP port 443||Communication with the Facebook Graph API|
|clearcaster.c2.wowza.com||TCP port 443||Communication with the Wowza ClearCaster GraphQL API|
|ntp.ubuntu.com||UDP port 123||Time synchronization services (NTP)|
|wowzalicense1.wowzamedia.com||TCP port 80||Wowza license server 1|
|wowzalicense2.wowzamedia.com||TCP port 80||Wowza license server 2|
|wowzalicense3.wowzamedia.com||TCP port 80||Wowza license server 3|
|wowzalicense4.wowzamedia.com||TCP port 80||Wowza license server 4|
ClearCaster checks in with the Wowza licensing server on a regular basis. If you have an enterprise proxy, you will need to pass through these communications without authentication. If you have firewall devices such as WatchGuard or Barracuda in place, there may be a factory built-in rule called Webblocker category: streaming, which is known to block the licensing validation process. For questions regarding licensing server communications, contact the Wowza Support team.