Docker deployment with external proxy doesn't work

Hi

I wanted to deploy the openvidu with the external proxy. I have the proxy installed on another machine, added a new subdomain, and run the installation script with the --external-proxy flag, but it doesn’t work.

The error I have is

Incorrect Usage: flag provided but not defined: -external-proxy

After this, the script lists all options, and no --external-proxy option is listed. How can I deploy it using your installation script?

Below the all messages I have after run the installation script

Docker already installed. Check you have the latest version for best compatibility
Docker Compose already installed. Check you have the latest version for best compatibility
Synchronizing state of docker.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
Executing: /usr/lib/systemd/systemd-sysv-install enable docker
Stopping 'docker.service', but its triggering units are still active:
docker.socket
Waiting for Docker to start...
Docker started successfully.
3.1.0: Pulling from openvidu/openvidu-installer
Digest: sha256:9b8be46ca4953bdea9d15f0069067dcde3cc6ada64470b0d8ac6b75bd66dd9c7
Status: Image is up to date for openvidu/openvidu-installer:3.1.0
docker.io/openvidu/openvidu-installer:3.1.0
Incorrect Usage: flag provided but not defined: -external-proxy

NAME:
   OpenVidu Deployment Installer CLI - Generates commands or files to install OpenVidu

USAGE:
   OpenVidu Deployment Installer CLI [global options] command [command options]

VERSION:
   3.1.0

COMMANDS:
   help, h  Shows a list of commands or help for one command

GLOBAL OPTIONS:
   --no-tty                                  Disable interactive prompts (default: false)
   --install                                 Enables install mode. When set, the system will automatically generate and install OpenVidu. By default (false), it only generates the installation commands without executing them. (default: false)
   --start-after-install                     Start OpenVidu services after installation (default: false)
   --openvidu-pro-offline                    Enable offline license mode (default: false)
   --force-media-node-public-ip              Force the public IP of the media node. You must install the media node with '--public-ip' flag (default: false)
   --deployment-type value                   Which deployment type do you want to use, elastic, ha
   --domain-name value                       Domain name or IP address of your cluster
   --turn-domain-name value                  (Optional) Domain name of your TURN server to allow TLS over TURN
   --certificate-type value                  Select which certificate type to use, selfsigned, letsencrypt, zerossl or owncert
   --zero-ssl-api-key value                  ZeroSSL API Key
   --letsencrypt-email value                 Email address to use with Let's Encrypt
   --owncert-private-key value               Base64 encoded private key of your private certificate (PEM format)
   --owncert-public-key value                Base64 encoded private key of your public certificate (PEM format)
   --turn-owncert-private-key value          Base64 encoded private key of your private certificate for TURN (PEM format)
   --turn-owncert-public-key value           Base64 encoded private key of your public certificate for TURN (PEM format)
   --livekit-api-key value                   LiveKit API Key
   --livekit-api-secret value                LiveKit API Secret
   --redis-password value                    Redis Password
   --minio-access-key value                  Minio Access Key
   --minio-secret-key value                  Minio Secret Key
   --mongo-admin-user value                  Mongo Admin User
   --mongo-admin-password value              Mongo Admin Password
   --mongo-replica-set-key value             Mongo Replica Set Key
   --dashboard-admin-user value              Dashboard Admin User
   --dashboard-admin-password value          Dashboard Admin Password
   --grafana-admin-user value                Grafana Admin User
   --grafana-admin-password value            Grafana Admin Password
   --default-app-user value                  Default app (OpenVidu Call) user
   --default-app-password value              Default app (OpenVidu Call) password
   --default-app-admin-user value            Default app (OpenVidu Call) admin username
   --default-app-admin-password value        Default app (OpenVidu Call) admin password
   --private-ip value                        Private IP of this machine
   --private-network-interface value         Private network interface to use for the private IP detection
   --public-ip value                         Public IP of this node
   --node-role value                         What type of node do you want to install: 'master-node' or 'media-node'
   --environment value                       Environment name
   --openvidu-pro-license value              OpenVidu PRO License
   --openvidu-pro-offline-media-nodes value  Number of 'Media Nodes' to register in the offline license
   --master-node-private-ip value            'Master Node' Private Ip
   --master-node-private-ip-list value       'Master Node' Private Ips separated by commas
   --rtc-engine value                        Select which RTC engine to use, pion or mediasoup
   --enabled-modules value                   Modules to enable, separated by commas
   --external-load-balancer                  Do you want to use an external load balancer? (default: false)
   --help, -h                                show help
   --version, -v                             print the version
flag provided but not defined: -external-proxy
./install.sh: 160: cd: can't cd to /tmp/tmp.hMovZsaiVl/installation-scripts/openvidu/

This feature is not out yet. It is for 3.2.0.

Where did you see the --external-proxy flag? Maybe in the master branch of docs, but it is not present in current stable release.

I’ve seen it here, in the 3.1.0 docs

It should not be there, it is for 3.2.0. I think the main branch has been pushed with recent changes to 3.1.0.