OpenVidu configuration directly affects video quality, session stability, and security.
Use explicit media/network settings before inviting production users.
Primary deployment file is usually .env consumed by OpenVidu services.
Example:
DOMAIN_OR_PUBLIC_IP=openvidu.example.com
OPENVIDU_SECRET=replace-with-long-random-secret
CERTIFICATE_TYPE=letsencrypt
LETSENCRYPT_EMAIL=admin@example.com
OPENVIDU_RECORDING=true
OPENVIDU_RECORDING_PATH=/opt/openvidu/recordings
OPENVIDU_STREAMS_VIDEO_MAX_RECV_BANDWIDTH=2000
OPENVIDU_STREAMS_VIDEO_MIN_RECV_BANDWIDTH=300
¶ Network and TURN/STUN considerations
- Ensure required ports are reachable for signaling/media.
- If users are behind strict NAT/firewalls, configure TURN for relay fallback.
- Keep DNS stable and certificate renewal monitored.
- Validate round-trip latency from key user regions.
¶ Session and recording policy
- Use short-lived backend-issued tokens for session joins.
- Restrict recording rights to moderator roles.
- Set retention for recordings and purge on schedule.
- Encrypt storage where compliance requires it.
¶ Backup and recovery
Back up:
.env and deployment manifests- recording directory
- custom certificates (if not automated)
Recovery test:
- Restore config and recordings to test host.
- Start one test session with publish/subscribe streams.
- Validate recording playback and download.
- Certificate renewal works.
- Media quality metrics monitored.
- Failed session joins and reconnect rates alerting enabled.
- Upgrade and rollback runbook documented.
Feel free to contact us. Find all contact information on our contact page.