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
..
community	openvidu-deployment: AWS - wait for the Elastic IP before deriving the domain	2026-10-06 16:00:49 +02:00
pro	openvidu-deployment: HA: expose RTMPS Ingress on port 1945 through the load balancer	2026-10-07 02:20:20 +02:00
update.sh	chore: update third-party versions	2026-09-30 15:50:22 +00:00