You may find that connections to and from RePro need to be cleared in your IT infrastructure. Here is a list of the clearance that may be required.
SRT Streams (outgoing from set or incoming from RePro other outputs)
When you create a project on RePro it will be assigned to a specific 'video engine' which will have a specific IP and domain. These are generally on a 'repro.stream' domain e.g. lon1.repro.stream as the domain. It will also be assigned a port.
To find the the domain, IP of the video engine you can head to your Project manager section of RePro and then choose 'Programs', select a program from the list and use the view or copy options for each section of the program details. You will find the port for each program too.
SRT streams need to cleared for bi-directional UDP.
Web app domains
Repro's web app is hosted at app.reprostream.com which in some networks may need to be cleared if for TCP on 443.
Guest links are facilitated through view.repro.stream - if your viewers are on a firewall network then this link may need to be cleared for TCP on 443 as well.
Viewing app streams
RePro Web, iOS and tvOS viewing apps receive streams over TCP using web socket wss:// protocols direct from the video engine - so you may need to make sure anyone viewing on you infra are cleared for this.
Whitelabel and self host solutions
If you self host your video engine or have a white label solution with your own domains then refer to the setup instructions given at the time of configuration or speak to RePro support.
Common ports for on-set streaming & viewing
Type | Protocol | Port Range | Notes |
SRT Streams* | UDP srt:// | 10000 to 50000** | Bi-directional |
Viewing Streams* | TCP https:// & wss:// | 443 | Web, iOS, tvOS - domain and IP as per video engine |
RePro Platform | TCP https:// | 443 | app.reprostream.com view.repro.stream |
Streams come directly from the video engine being used so domain and IP can change depending on your project - these can be found for your project for each program as mentioned above. Please also see Commong RePro engines list below.
** This is RePro's broad port range - for maximum security please only whitelist the ports as shown for each program as mentioned above.
Additional firewall requirements for Audio Chat (only if being used)
RePro Audio Chat uses LiveKit Cloud.
If users are connecting from behind a corporate firewall, please allow outbound access to the following:
Purpose | Hostname/Destination | Protocol | Port Range |
Signalling | *.livekit.cloud | TCP | 443 |
TURN over TLS fallback | *.turn.livekit.cloud | TCP | 443 |
TURN / connectivity assistance | *.host.livekit.cloud | UDP | 3478 |
WebRTC media (recommended) | all hosts | UDP | 50000-60000 |
WebRTC TCP fallback (recommended) | all hosts | TCP | 7881-7882 |
Notes re audio chat clearance.
For best audio quality and reliability, outbound UDP
50000–60000should be allowed where possible.If wildcard FQDN rules are not permitted by your firewall policy, LiveKit provides a minimum hostname list based on the project subdomain.
The resolved IPs for LiveKit Cloud hosts should not be treated as permanent. Hostnames and backing IPs may change over time, so FQDN-based allowlisting is preferred over static IP allowlisting.
These Audio Chat firewall rules are separate from RePro video engine streaming/viewing firewall requirements.
Common RePro video engines
Engine | Protocol | IP | Port Range |
LON1 | lon1.repro.stream | 81.144.250.131 | UDP 10000:29999 |
ERA1 | era1.repro.stream | 77.77.177.8 | UDP 35000:44999 |
ERA2 | era2.repro.stream | 77.77.177.9 | UDP 35000:44999 |