openvidu/openvidu-deployment/pro/ha/gcp
Piwccle 687bcdec0e openvidu-deployment: HA: expose RTMPS Ingress on port 1945 through the load balancer
With --external-load-balancer the installer advertises the RTMP Ingress URL as
rtmps://<domain>:1945/rtmp (CADDY_RTMPS_PUBLIC_PORT), but the load balancers only
listened on 1935, so the advertised URL never connected. Verified live on AWS HA:
:1945 timed out, and :1935 reached a target group on Media Node port 1945 where
nothing listens (ingress serves RTMP on 1935).

- AWS: NLB TLS listener 1945 -> Media Node ingress 1935 (target group and SG)
- Azure: LB frontend 1945 -> masters 1945, and the master NSG allows 1945
- GCP: forwarding rule 1945 (a passthrough NLB cannot translate ports)
- OCI: NLB listener, backend set, NSGs and master firewalld on 1945
- DigitalOcean: LB forwarding rule 1945 -> masters 1945
2026-10-07 02:20:20 +02:00
..
output.tf openvidu-deployment: HA deployment GCP done and tested 2025-11-19 10:41:42 +01:00
tf-gpc-openvidu-ha.tf openvidu-deployment: HA: expose RTMPS Ingress on port 1945 through the load balancer 2026-10-07 02:20:20 +02:00
variables.tf openvidu-deployment: make mediasoup the default RTC engine for new PRO deployments 2026-09-29 14:57:15 +02:00
versions.tf openvidu-deployment: HA deployment GCP done and tested 2025-11-19 10:41:42 +01:00