Media Node and OpenVidu Pro server is not starting in on-premises deployment

My goal is to use this OpenVidu Pro so that I can record and upload video stream to aws s3.

I followed steps given in OpenVidu Docs for deploying OpenVidu server Pro node and media node on premise for testing purposes.

And both OpenVidu Pro server node and media_node are having some issues.

here is where media_node is stuck:

./media_node start
Creating network "kms_default" with the default driver
Creating kms_media-node-controller_1 ... done
Attaching to kms_media-node-controller_1
media-node-controller_1  | Creating dir for beats
media-node-controller_1  | Copying beat config files
media-node-controller_1  | [Nest] 11   - 07/15/2021, 4:23:06 AM   [NestFactory] Starting Nest application...
media-node-controller_1  | [Nest] 11   - 07/15/2021, 4:23:07 AM   [InstanceLoader] DiscoveryModule dependencies initialized +53ms
media-node-controller_1  | [Nest] 11   - 07/15/2021, 4:23:07 AM   [InstanceLoader] ConfigHostModule dependencies initialized +0ms
media-node-controller_1  | [Nest] 11   - 07/15/2021, 4:23:07 AM   [InstanceLoader] ScheduleModule dependencies initialized +1ms
media-node-controller_1  | [Nest] 11   - 07/15/2021, 4:23:07 AM   [InstanceLoader] ConfigModule dependencies initialized +0ms
media-node-controller_1  | [Nest] 11   - 07/15/2021, 4:23:07 AM   ======== MEDIA NODE CONTROLLER CONFIGURATION ========== +1ms
media-node-controller_1  | [Nest] 11   - 07/15/2021, 4:23:07 AM   RECORDINGS_SYSTEM_PATH: /opt/openvidu/recordings +0ms
media-node-controller_1  | [Nest] 11   - 07/15/2021, 4:23:07 AM   LOGS_DIRECTORIES: /opt/openvidu/kurento-logs +0ms
media-node-controller_1  | [Nest] 11   - 07/15/2021, 4:23:07 AM   ======================================================= +0ms
media-node-controller_1  | [Nest] 11   - 07/15/2021, 4:23:07 AM   [InstanceLoader] AppModule dependencies initialized +1ms
media-node-controller_1  | [Nest] 11   - 07/15/2021, 4:23:07 AM   [RoutesResolver] DockerController {/media-node}: +6ms
media-node-controller_1  | [Nest] 11   - 07/15/2021, 4:23:07 AM   [RouterExplorer] Mapped {/media-node/dockerGatewayIp, GET} route +3ms
media-node-controller_1  | [Nest] 11   - 07/15/2021, 4:23:07 AM   [RouterExplorer] Mapped {/media-node/getContainerIp/:containerIdOrName, GET} route +1ms
media-node-controller_1  | [Nest] 11   - 07/15/2021, 4:23:07 AM   [RouterExplorer] Mapped {/media-node/getRunningContainers, GET} route +0ms
media-node-controller_1  | [Nest] 11   - 07/15/2021, 4:23:07 AM   [RouterExplorer] Mapped {/media-node/isContainerRunning/:containerNameOrId, GET} route +1ms
media-node-controller_1  | [Nest] 11   - 07/15/2021, 4:23:07 AM   [RouterExplorer] Mapped {/media-node/getContainerIdByName/:containerName, GET} route +1ms
media-node-controller_1  | [Nest] 11   - 07/15/2021, 4:23:07 AM   [RouterExplorer] Mapped {/media-node/getContainerByNameOrId/:containerNameOrId, GET} route +1ms
media-node-controller_1  | [Nest] 11   - 07/15/2021, 4:23:07 AM   [RouterExplorer] Mapped {/media-node/getLabelsFromContainerNameOrId/:containerNameOrId, GET} route +0ms
media-node-controller_1  | [Nest] 11   - 07/15/2021, 4:23:07 AM   [RouterExplorer] Mapped {/media-node/checkImageExists, POST} route +1ms
media-node-controller_1  | [Nest] 11   - 07/15/2021, 4:23:07 AM   [RouterExplorer] Mapped {/media-node/pullDockerImage, POST} route +0ms
media-node-controller_1  | [Nest] 11   - 07/15/2021, 4:23:07 AM   [RouterExplorer] Mapped {/media-node, POST} route +1ms
media-node-controller_1  | [Nest] 11   - 07/15/2021, 4:23:07 AM   [RouterExplorer] Mapped {/media-node/waitContainer/:containerNameOrId, POST} route +0ms
media-node-controller_1  | [Nest] 11   - 07/15/2021, 4:23:07 AM   [RouterExplorer] Mapped {/media-node/stopContainer/:containerNameOrId, DELETE} route +1ms
media-node-controller_1  | [Nest] 11   - 07/15/2021, 4:23:07 AM   [RouterExplorer] Mapped {/media-node/removeContainer/:containerNameOrId, DELETE} route +1ms
media-node-controller_1  | [Nest] 11   - 07/15/2021, 4:23:07 AM   [RouterExplorer] Mapped {/media-node/runCommandInContainer/:containerNameOrId, POST} route +1ms
media-node-controller_1  | [Nest] 11   - 07/15/2021, 4:23:07 AM   [RoutesResolver] ConfigController {/media-node}: +0ms
media-node-controller_1  | [Nest] 11   - 07/15/2021, 4:23:07 AM   [RouterExplorer] Mapped {/media-node/status, GET} route +1ms
media-node-controller_1  | [Nest] 11   - 07/15/2021, 4:23:07 AM   [RouterExplorer] Mapped {/media-node/cpu, GET} route +0ms
media-node-controller_1  | [Nest] 11   - 07/15/2021, 4:23:07 AM   [RouterExplorer] Mapped {/media-node/getRequestIp, GET} route +1ms
media-node-controller_1  | [Nest] 11   - 07/15/2021, 4:23:07 AM   [RouterExplorer] Mapped {/media-node/getEnvVariable/:envVariable, GET} route +0ms
media-node-controller_1  | [Nest] 11   - 07/15/2021, 4:23:07 AM   [RouterExplorer] Mapped {/media-node/waitForFile, POST} route +1ms
media-node-controller_1  | [Nest] 11   - 07/15/2021, 4:23:07 AM   [RouterExplorer] Mapped {/media-node/recordings/:recordingId/:recordingFile, DELETE} route +1ms
media-node-controller_1  | [Nest] 11   - 07/15/2021, 4:23:07 AM   [NestApplication] Nest application successfully started +7ms

Here, is where openvidu pro server is stuck
This part repeats after "8 common framer omitted"

openvidu-server_1  | 
openvidu-server_1  | [INFO] 2021-07-15 04:12:41,634 [main] io.openvidu.server.pro.OpenViduServerPro - Starting OpenViduServerPro on kali with PID 18 (/opt/openvidu/openvidu-server.jar started by root in /opt/openvidu)
openvidu-server_1  | [INFO] 2021-07-15 04:12:41,635 [main] io.openvidu.server.pro.OpenViduServerPro - No active profile set, falling back to default profiles: default
openvidu-server_1  | [INFO] 2021-07-15 04:12:41,672 [main] io.openvidu.server.config.OpenviduConfig - Configuration properties read from file /opt/openvidu/.env
openvidu-server_1  | [INFO] 2021-07-15 04:12:41,682 [main] io.openvidu.server.pro.OpenViduServerPro - Started OpenViduServerPro in 0.151 seconds (JVM running for 4.24)
openvidu-server_1  | [INFO] 2021-07-15 04:12:41,683 [main] io.openvidu.server.pro.OpenViduServerPro - OpenVidu Pro is deployed in 'on_premise' environment
openvidu-server_1  | [WARN] 2021-07-15 04:12:41,683 [main] io.openvidu.server.pro.OpenViduServerPro - OpenVidu Pro cluster mode is 'manual'. There will be no automatic instances management
openvidu-server_1  | [INFO] 2021-07-15 04:12:41,689 [main] io.openvidu.server.pro.OpenViduServerPro - Cluster identifier not configured in OPENVIDU_PRO_CLUSTER_ID. Using DOMAIN_OR_PUBLIC_IP as cluster identifier: 127.0.0.1
openvidu-server_1  | [INFO] 2021-07-15 04:12:41,690 [main] io.openvidu.server.pro.OpenViduServerPro - Provisioning media-node localhost if containers are not running
openvidu-server_1  | [ERROR] 2021-07-15 04:12:41,728 [main] io.openvidu.server.pro.OpenViduServerPro - Can't provision autodiscovered node. Probably media-node-controller is not running: localhost
openvidu-server_1  | io.openvidu.client.OpenViduException: Media Node controller http://localhost:3000/ is not reachable. Code: 999
openvidu-server_1  | 	at io.openvidu.server.pro.infrastructure.mncontroller.MediaNodeControllerDockerManager.checkAvailability(MediaNodeControllerDockerManager.java:65)
openvidu-server_1  | 	at io.openvidu.server.pro.infrastructure.mncontroller.MediaNodeProvisioner.checkAvailability(MediaNodeProvisioner.java:101)
openvidu-server_1  | 	at io.openvidu.server.pro.infrastructure.InfrastructureManager.checkMediaNodeAvailability(InfrastructureManager.java:880)
openvidu-server_1  | 	at io.openvidu.server.pro.OpenViduServerPro.provisionMediaNodesByUris(OpenViduServerPro.java:686)
openvidu-server_1  | 	at io.openvidu.server.pro.OpenViduServerPro.main(OpenViduServerPro.java:450)
openvidu-server_1  | 	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
openvidu-server_1  | 	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
openvidu-server_1  | 	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
openvidu-server_1  | 	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
openvidu-server_1  | 	at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:49)
openvidu-server_1  | 	at org.springframework.boot.loader.Launcher.launch(Launcher.java:107)
openvidu-server_1  | 	at org.springframework.boot.loader.Launcher.launch(Launcher.java:58)
openvidu-server_1  | 	at org.springframework.boot.loader.PropertiesLauncher.main(PropertiesLauncher.java:467)
openvidu-server_1  | [INFO] 2021-07-15 04:12:41,855 [main] io.openvidu.server.pro.OpenViduServerPro - Starting OpenViduServerPro on kali with PID 18 (/opt/openvidu/openvidu-server.jar started by root in /opt/openvidu)
openvidu-server_1  | [INFO] 2021-07-15 04:12:41,861 [main] io.openvidu.server.pro.OpenViduServerPro - No active profile set, falling back to default profiles: default
openvidu-server_1  | [INFO] 2021-07-15 04:12:41,904 [main] io.openvidu.server.config.OpenviduConfig - Configuration properties read from file /opt/openvidu/.env
openvidu-server_1  | [INFO] 2021-07-15 04:12:41,915 [main] io.openvidu.server.pro.OpenViduServerPro - Started OpenViduServerPro in 0.179 seconds (JVM running for 4.474)
openvidu-server_1  | [INFO] 2021-07-15 04:12:41,917 [main] io.openvidu.server.pro.OpenViduServerPro - Checking KMS_URIS [ws://localhost:8888/kurento]
openvidu-server_1  | [INFO] 2021-07-15 04:12:41,917 [main] io.openvidu.server.config.OpenviduConfig - Waiting for KMS instance ws://localhost:8888/kurento to be ready for a maximum of 120 seconds (maximum 120 connection attempts with a wait interval of 1000 ms between them)
openvidu-server_1  | [INFO] 2021-07-15 04:12:41,952 [JsonRpcClient-hearbeatExec-e1-t0] org.kurento.jsonrpc.client.JsonRpcClientNettyWebSocket - [KurentoClient]  Connecting native client
openvidu-server_1  | [INFO] 2021-07-15 04:12:41,957 [JsonRpcClient-hearbeatExec-e1-t0] org.kurento.jsonrpc.client.JsonRpcClientNettyWebSocket - [KurentoClient]  Creating new NioEventLoopGroup
openvidu-server_1  | [INFO] 2021-07-15 04:12:42,260 [nioEventLoopGroup-2-1] org.kurento.jsonrpc.client.JsonRpcClientNettyWebSocket - [KurentoClient]  Initiating new Netty channel. Will create new handler too!
openvidu-server_1  | [INFO] 2021-07-15 04:12:42,452 [main] io.openvidu.server.config.OpenviduConfig - KMS with URI ws://localhost:8888/kurento is now ready after 1 seconds at connection attempt 1
openvidu-server_1  | [WARN] 2021-07-15 04:12:42,515 [JsonRpcClient-hearbeatExec-e1-t0] org.kurento.jsonrpc.client.JsonRpcClient - [KurentoClient]  Error sending heartbeat to server. Exception: [KurentoClient]  Interrupted while waiting for a response
openvidu-server_1  | [WARN] 2021-07-15 04:12:42,517 [JsonRpcClient-hearbeatExec-e1-t0] org.kurento.jsonrpc.client.JsonRpcClient - [KurentoClient]  Stopping heartbeat and closing client: failure during heartbeat mechanism
openvidu-server_1  | [WARN] 2021-07-15 04:12:42,547 [main] org.kurento.jsonrpc.client.AbstractJsonRpcClientWebSocket - [KurentoClient]  Exception sending close message. org.kurento.jsonrpc.JsonRpcErrorException:'params' is requiered. Code: -32602. Data: {"type":"INVALID_PARAMS"}
openvidu-server_1  | [INFO] 2021-07-15 04:12:42,548 [nioEventLoopGroup-2-1] org.kurento.jsonrpc.client.JsonRpcClientNettyWebSocket - [KurentoClient]  channel closed
openvidu-server_1  | [WARN] 2021-07-15 04:12:42,553 [main] org.kurento.jsonrpc.client.AbstractJsonRpcClientWebSocket - [KurentoClient]  Exception sending close message. org.kurento.jsonrpc.JsonRpcClientClosedException:Trying to send a message in a client closed explicitly. When a client is closed, it can't be reused. It is necessary to create another one
openvidu-server_1  | [WARN] 2021-07-15 04:12:42,553 [main] org.kurento.jsonrpc.client.JsonRpcClientNettyWebSocket - [KurentoClient]  Trying to close a JsonRpcClientNettyWebSocket with channel == null
openvidu-server_1  | [WARN] 2021-07-15 04:12:42,553 [main] org.kurento.jsonrpc.client.JsonRpcClientNettyWebSocket - [KurentoClient]  Trying to close a JsonRpcClientNettyWebSocket with group == null
openvidu-server_1  | [WARN] 2021-07-15 04:12:42,563 [main] io.openvidu.server.pro.OpenViduServerPro - You have set property server.port (or SERVER_PORT). This will serve OpenVidu Server Pro on your host at port 5443. But property HTTPS_PORT (4443) still configures the port that should be used to connect to OpenVidu Server from outside. Bear this in mind when configuring a proxy in front of OpenVidu Server
openvidu-server_1  | [INFO] 2021-07-15 04:12:42,654 [main] io.openvidu.server.pro.OpenViduServerPro - Starting OpenViduServerPro on kali with PID 18 (/opt/openvidu/openvidu-server.jar started by root in /opt/openvidu)
openvidu-server_1  | [INFO] 2021-07-15 04:12:42,656 [main] io.openvidu.server.pro.OpenViduServerPro - No active profile set, falling back to default profiles: default
openvidu-server_1  | [INFO] 2021-07-15 04:12:45,402 [main] io.openvidu.server.config.OpenviduConfig - Configuration properties read from file /opt/openvidu/.env
openvidu-server_1  | [INFO] 2021-07-15 04:12:45,976 [main] org.springframework.boot.web.embedded.tomcat.TomcatWebServer - Tomcat initialized with port(s): 5443 (http)
openvidu-server_1  | [INFO] 2021-07-15 04:12:45,996 [main] org.apache.catalina.core.StandardService - Starting service [Tomcat]
openvidu-server_1  | [INFO] 2021-07-15 04:12:45,997 [main] org.apache.catalina.core.StandardEngine - Starting Servlet engine: [Apache Tomcat/9.0.39]
openvidu-server_1  | [INFO] 2021-07-15 04:12:46,137 [main] org.apache.catalina.core.ContainerBase.[Tomcat].[localhost].[/] - Initializing Spring embedded WebApplicationContext
openvidu-server_1  | [INFO] 2021-07-15 04:12:46,138 [main] org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext - Root WebApplicationContext: initialization completed in 3436 ms
openvidu-server_1  | [INFO] 2021-07-15 04:12:46,219 [main] io.openvidu.server.config.OpenviduConfig - Configuration properties read from file /opt/openvidu/.env
openvidu-server_1  | [INFO] 2021-07-15 04:12:46,232 [main] io.openvidu.server.pro.OpenViduServerPro - Server Micrometer stats enabled. Gathering every 10s
openvidu-server_1  | [INFO] 2021-07-15 04:12:46,306 [main] io.micrometer.core.instrument.push.PushMeterRegistry - publishing metrics for ElasticMeterRegistry every 10s
openvidu-server_1  | [WARN] 2021-07-15 04:12:46,853 [main] io.openvidu.server.rest.ApiRestPathRewriteFilter - Support for deprecated REST API paths enabled. Update your REST API clients to use the new paths
openvidu-server_1  | [WARN] 2021-07-15 04:12:46,853 [main] io.openvidu.server.rest.ApiRestPathRewriteFilter - Deprecated path support will be removed in a future release. You can disable old path support to test compatibility with property SUPPORT_DEPRECATED_API=false
openvidu-server_1  | [INFO] 2021-07-15 04:12:46,925 [main] io.openvidu.server.pro.OpenViduServerPro - OpenVidu Pro is deployed in 'on_premise' environment
openvidu-server_1  | [WARN] 2021-07-15 04:12:46,925 [main] io.openvidu.server.pro.OpenViduServerPro - OpenVidu Pro cluster mode is 'manual'. There will be no automatic instances management
openvidu-server_1  | [INFO] 2021-07-15 04:12:46,934 [main] io.openvidu.server.pro.OpenViduServerPro - OpenVidu Pro cluster mode enabled
openvidu-server_1  | [INFO] 2021-07-15 04:12:46,934 [main] io.openvidu.server.pro.OpenViduServerPro - Cluster identifier not configured in OPENVIDU_PRO_CLUSTER_ID. Using DOMAIN_OR_PUBLIC_IP as cluster identifier: 127.0.0.1
openvidu-server_1  | [INFO] 2021-07-15 04:12:46,971 [main] io.openvidu.server.pro.OpenViduServerPro - OpenVidu Pro Elasticsearch service is enabled
openvidu-server_1  | [ERROR] 2021-07-15 04:12:48,594 [main] io.openvidu.server.pro.cdr.CDRLoggerElasticSearch - Connection to Elasticsearch failed at http://127.0.0.1:9200 (Connection is closed)
openvidu-server_1  | [ERROR] 2021-07-15 04:12:48,595 [main] io.openvidu.server.pro.cdr.CDRLoggerElasticSearch - If property 'OPENVIDU_PRO_ELASTICSEARCH_HOST' is defined, then it is mandatory that OpenVidu Server Pro is able to connect to it
openvidu-server_1  | [ERROR] 2021-07-15 04:12:48,595 [main] io.openvidu.server.pro.cdr.CDRLoggerElasticSearch - Terminating OpenVidu Server Pro
openvidu-server_1  | [WARN] 2021-07-15 04:12:56,316 [elastic-metrics-publisher] io.micrometer.core.instrument.push.PushMeterRegistry - Unexpected exception thrown while publishing metrics for ElasticMeterRegistry
openvidu-server_1  | java.lang.RuntimeException: java.net.SocketException: Connection reset
openvidu-server_1  | 	at io.micrometer.elastic.ElasticMeterRegistry.determineMajorVersionIfNeeded(ElasticMeterRegistry.java:258)
openvidu-server_1  | 	at io.micrometer.elastic.ElasticMeterRegistry.publish(ElasticMeterRegistry.java:200)
openvidu-server_1  | 	at io.micrometer.core.instrument.push.PushMeterRegistry.publishSafely(PushMeterRegistry.java:52)
openvidu-server_1  | 	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
openvidu-server_1  | 	at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
openvidu-server_1  | 	at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
openvidu-server_1  | 	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
openvidu-server_1  | 	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
openvidu-server_1  | 	at java.base/java.lang.Thread.run(Thread.java:829)
openvidu-server_1  | Caused by: java.net.SocketException: Connection reset
openvidu-server_1  | 	at java.base/java.net.SocketInputStream.read(SocketInputStream.java:186)
openvidu-server_1  | 	at java.base/java.net.SocketInputStream.read(SocketInputStream.java:140)
openvidu-server_1  | 	at java.base/java.io.BufferedInputStream.fill(BufferedInputStream.java:252)
openvidu-server_1  | 	at java.base/java.io.BufferedInputStream.read1(BufferedInputStream.java:292)
openvidu-server_1  | 	at java.base/java.io.BufferedInputStream.read(BufferedInputStream.java:351)
openvidu-server_1  | 	at java.base/sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:754)
openvidu-server_1  | 	at java.base/sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:689)
openvidu-server_1  | 	at java.base/sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:713)
openvidu-server_1  | 	at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1615)
openvidu-server_1  | 	at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1520)
openvidu-server_1  | 	at java.base/java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:527)
openvidu-server_1  | 	at io.micrometer.core.ipc.http.HttpUrlConnectionSender.send(HttpUrlConnectionSender.java:102)
openvidu-server_1  | 	at io.micrometer.core.ipc.http.HttpSender$Request$Builder.send(HttpSender.java:284)
openvidu-server_1  | 	at io.micrometer.elastic.ElasticMeterRegistry.determineMajorVersionIfNeeded(ElasticMeterRegistry.java:254)
openvidu-server_1  | 	... 8 common frames omitted

Here, is my .env

DOMAIN_OR_PUBLIC_IP=127.0.0.1
OPENVIDU_PRO_LICENSE=**
OPENVIDU_SECRET=MY_SECRET
CERTIFICATE_TYPE=selfsigned
LETSENCRYPT_EMAIL=user@example.com
HTTPS_PORT=4443
OPENVIDU_PRO_CLUSTER_MODE=manual
OPENVIDU_PRO_CLUSTER_ENVIRONMENT=on_premise
OPENVIDU_PRO_CLUSTER_MEDIA_NODES=1
OPENVIDU_PRO_CLUSTER_AUTOSCALING=true
OPENVIDU_PRO_CLUSTER_LOAD_STRATEGY=streams
OPENVIDU_PRO_RECORDING_STORAGE=s3
OPENVIDU_PRO_AWS_S3_BUCKET=**
OPENVIDU_PRO_AWS_S3_HEADERS=
OPENVIDU_PRO_AWS_ACCESS_KEY=**
OPENVIDU_PRO_AWS_SECRET_KEY=**
OPENVIDU_PRO_AWS_REGION=**
OPENVIDU_RECORDING=true
OPENVIDU_RECORDING_DEBUG=false
OPENVIDU_RECORDING_PATH=/opt/openvidu/recordings
OPENVIDU_RECORDING_CUSTOM_LAYOUT=/opt/openvidu/custom-layout
OPENVIDU_RECORDING_PUBLIC_ACCESS=false
OPENVIDU_RECORDING_NOTIFICATION=publisher_moderator
OPENVIDU_RECORDING_AUTOSTOP_TIMEOUT=120
OPENVIDU_STREAMS_VIDEO_MAX_RECV_BANDWIDTH=1000
OPENVIDU_STREAMS_VIDEO_MIN_RECV_BANDWIDTH=300
PENVIDU_STREAMS_VIDEO_MAX_SEND_BANDWIDTH=1000
OPENVIDU_STREAMS_VIDEO_MIN_SEND_BANDWIDTH=300
OPENVIDU_WEBHOOK=false
OPENVIDU_WEBHOOK_EVENTS=[sessionCreated,sessionDestroyed,participantJoined,participantLeft,webrtcConnectionCreated,webrtcConnectionDestroyed,recordingStatusChanged,filterEventDispatched,signalSent,mediaNodeStatusChanged,autoscaling,nodeCrashed]
OPENVIDU_SESSIONS_GARBAGE_INTERVAL=900
OPENVIDU_SESSIONS_GARBAGE_THRESHOLD=3600
OPENVIDU_CDR=false
OPENVIDU_CDR_PATH=/opt/openvidu/cdr
ELASTICSEARCH_USERNAME=elasticadmin
ELASTICSEARCH_PASSWORD=**
KMS_IMAGE=kurento/kurento-media-server:6.15.0
KMS_URIS=["ws://localhost:8888/kurento"]

Previously I was having the issue of repeating " Waiting for kibana in ‘http://127.0.0.1/kibana’ URL…" but then I changed my DOMAIN_OR_PUBLIC_IP=127.0.0.1 from DOMAIN_OR_PUBLIC_IP=localhost.
This solved the issue but not sure is the correct way.

I am using this tutorial for my testing purpose “openvidu-recording-node”.

I am not sure what are the problems here.

Currently testing this recording and uploading video stream to s3 feature on_premise and if it works would move on deploying it on aws.

Thanks, in advance.

Please Reply… as soon as possible…!

Deven, we reply as soon as we can. Please be patient.

  1. First of all, I think that you’re deploying everything in one machine. OpenVidu Pro needs at least two machines with two public IPs deployed, to deploy the Master node in one machine and the media node in another one. This is because you will be charged additionally if you deploy everything in one machine.

  2. The parameter DOMAIN_OR_PUBLIC_IP, should be the public IP of the OpenVidu, not 127.0.0.1. If the public IP of your master node is 1.2.3.4 it would be:

DOMAIN_OR_PUBLIC_IP=1.2.3.4
  1. On the other hand, KMS_URIS parameter is wrongly configured. If the public IP of your media node is: 1.2.3.5 it would be:
KMS_URIS=["ws://1.2.3.5:8888/kurento"]

You need two machines with two public IPs, also open the ports for both machines explained here: OpenVidu Docs

How to find public IP of my master node and media node?

If you execute this you will know the public IP of any machine:

curl ifconfig.co

Anyways, you should know the public IPs of your instances. Are you using a cloud provider? Is it your own infrastructure?

Regards