Firewall Access Rules
If you are behind a firewall that is restricting access to Louper, please ask your network administrator to allow access to the following domains and ports on your network:
Domains
| Domain | Notes |
|---|---|
| *.louper.io | Louper operates critical infrastructure across multiple subdomains of louper.io. To ensure full functionality and uninterrupted service, please allow all subdomains of louper.io on your firewall using a wildcard entry *.louper.io |
| louper.livekit.cloud | Video conferencing and associated functionality |
| *turn.livekit.cloud | Video conferencing and associated functionality |
| *.azure.com | Websockets |
| *backblazeb2.com | S3 file storage |
| *mux.com | Video storage and content delivery |
| bunny.louper.io | Content delivery |
| identitytoolkit.googleapis.com | Sign in and authentication for all users |
| fonts.googleapis.com | Google content delivery network (app fonts) |
| fonts.gstatic.com | Google content delivery network (app fonts) |
There are dynamic subdomains in addition to the above that may be required. We strongly recommend allowing all louper.io subdomains on your firewall (eg. *.louper.io).
Ports
For traffic to and from all domains listed above
- TCP 80
- TCP + UDP 443
- TCP 3334
- TCP + UDP 3478
- TCP 7881
- UDP 7882
- UDP 10006
- UDP 50000-60000
- TCP + UDP 19302
For RTMP streaming from client to *.louper.io
- TCP 1935
For SRT streaming from client to *.louper.io
- UDP 9999
UDP Hole-Punching
Please ensure UDP hole-punching is enabled, or disable symmetric NAT. This helps machines behind the firewall establish a direct connection to Louper servers.
Note
Access can be tested using the Connection Tester. For further help or troubleshooting, contact Louper support.