# Openvidu pro inspector 502 bad gateway

**URL:** <https://openvidu.discourse.group/t/openvidu-pro-inspector-502-bad-gateway/2936>\
**Category:** How to implement?\
**Tags:** v2\
**Created:** [April 14, 2021, 10:22am UTC](https://openvidu.discourse.group/t/openvidu-pro-inspector-502-bad-gateway/2936 "2021-04-14T10:22:00Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![prasanna\_purohit](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/prasanna_purohit/32/46_2.png) [@prasanna\_purohit](https://openvidu.discourse.group/u/prasanna_purohit)\
**Post date:** [April 14, 2021, 10:22am UTC](https://openvidu.discourse.group/t/openvidu-pro-inspector-502-bad-gateway/2936/1 "2021-04-14T10:22:00Z")

</div>

hi openvidu team, I’m using openvidu pro for one of my client, I deployed openvidu pro on Monday, it was working fine on that day, when I reopened the domain today getting an error of 502 bad gateway nginx here is my domain URL [https://node.ratulive.com/inspector](https://node.ratulive.com/inspector)  
and as i made a little search about this issue i found a discourse group [PRO: inspector is not available error 502](https://openvidu.discourse.group/t/pro-inspector-is-not-available-error-502/2229)  
h they mentioned what is the issue and how to resolve it, but here my question is I created an instance in AWS t2-xlarge, but still why this is an issue,?

---

<div class="post-metadata">

**Author:** ![micael.gallego](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/micael.gallego/32/2_2.png) [@micael.gallego](https://openvidu.discourse.group/u/micael.gallego)\
**Post date:** [April 14, 2021, 10:42am UTC](https://openvidu.discourse.group/t/openvidu-pro-inspector-502-bad-gateway/2936/2 "2021-04-14T10:42:55Z")

</div>

Hello @prasanna_purohit,

Can you share openvidu logs to see what is happening?

---

<div class="post-metadata">

**Author:** ![cruizba](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/cruizba/32/18_2.png) [@cruizba](https://openvidu.discourse.group/u/cruizba)\
**Post date:** [April 14, 2021, 3:25pm UTC](https://openvidu.discourse.group/t/openvidu-pro-inspector-502-bad-gateway/2936/3 "2021-04-14T15:25:18Z")

</div>

A 502 Bad Gatweay could mean that OpenVidu Pro stop working. Check what may happened into the instance.

Common issues are instances not having enough disk space when using version 2.15.0 or less. Check the disk space of the instance, clean it and try restarting it.

If the problem is related with high disk space in `/opt/openvidu/elasticsearch`, follow this: [OpenVidu Docs](https://docs.openvidu.io/en/2.17.0/troubleshooting/#option-1-recover-openvidu-pro-deployment-by-deleting-elasticsearch-data)

From version 2.16.0 this problem should be solved.

Regards

---

<div class="post-metadata">

**Author:** ![prasanna\_purohit](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/prasanna_purohit/32/46_2.png) [@prasanna\_purohit](https://openvidu.discourse.group/u/prasanna_purohit)\
**Post date:** [April 16, 2021, 1:00pm UTC](https://openvidu.discourse.group/t/openvidu-pro-inspector-502-bad-gateway/2936/4 "2021-04-16T13:00:21Z")

</div>

hi @cruizba, I had followed the steps as given in this [OpenVidu Docs](https://docs.openvidu.io/en/2.17.0/troubleshooting/#option-1-recover-openvidu-pro-deployment-by-deleting-elasticsearch-data) but still getting the same response of 502 bad gateway.

---

<div class="post-metadata">

**Author:** ![prasanna\_purohit](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/prasanna_purohit/32/46_2.png) [@prasanna\_purohit](https://openvidu.discourse.group/u/prasanna_purohit)\
**Post date:** [April 16, 2021, 1:01pm UTC](https://openvidu.discourse.group/t/openvidu-pro-inspector-502-bad-gateway/2936/5 "2021-04-16T13:01:14Z")

</div>

hi, @micael.gallego from where I will get the openvidu logs? is there any specific path in the instance?

---

<div class="post-metadata">

**Author:** ![cruizba](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/cruizba/32/18_2.png) [@cruizba](https://openvidu.discourse.group/u/cruizba)\
**Post date:** [April 16, 2021, 1:59pm UTC](https://openvidu.discourse.group/t/openvidu-pro-inspector-502-bad-gateway/2936/6 "2021-04-16T13:59:53Z")

</div>

Go to `/opt/openvidu`  
When you run `./openvidu start`, the terminal automatically follows the log of the `openvidu-server` container.

If you exit the ssh session and you want to see the logs again you just need to execute:

```auto
./openvidu logs

```

To follow logs

```auto
./openvidu logs -f

```

Can you share the logs on start?

Regards

---

<div class="post-metadata">

**Author:** ![pabloFuente](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/pablofuente/32/2536_2.png) [@pabloFuente](https://openvidu.discourse.group/u/pabloFuente)\
**Post date:** [April 19, 2021, 9:02am UTC](https://openvidu.discourse.group/t/openvidu-pro-inspector-502-bad-gateway/2936/8 "2021-04-19T09:02:49Z")

</div>

First of all, be carefull when posting logs in public forums, as there couldbe sensitive information. In your case, the log has printed your license key.  
Fortunately, that is the error you are facing. The OpenVidu Pro license key that appears in the log does not exist:

```auto
{"status":404,"message":"License **** does not exist"}

```

---

<div class="post-metadata">

**Author:** ![cruizba](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/cruizba/32/18_2.png) [@cruizba](https://openvidu.discourse.group/u/cruizba)\
**Post date:** [April 19, 2021, 7:53pm UTC](https://openvidu.discourse.group/t/openvidu-pro-inspector-502-bad-gateway/2936/9 "2021-04-19T19:53:52Z")

</div>

I’ve removed the license just in case.

---

<div class="post-metadata">

**Author:** ![prasanna\_purohit](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/prasanna_purohit/32/46_2.png) [@prasanna\_purohit](https://openvidu.discourse.group/u/prasanna_purohit)\
**Post date:** [April 20, 2021, 12:59pm UTC](https://openvidu.discourse.group/t/openvidu-pro-inspector-502-bad-gateway/2936/10 "2021-04-20T12:59:22Z")

</div>

> [@prasanna\_purohit](#):
>
> `./openvidu start`
> 
> `Creating network "openvidu_default" with the default driver Creating openvidu_redis_1 ... done Creating openvidu_metricbeat_1 ... done Creating openvidu_elasticsearch_1 ... done Creating openvidu_kibana_1 ... done Creating openvidu_nginx_1 ... done Creating openvidu_openvidu-server_1 ... done Creating openvidu_app_1 ... done Creating openvidu_filebeat_1 ... done Creating openvidu_coturn_1 ... done Attaching to openvidu_openvidu-server_1 openvidu-server_1 | openvidu-server_1 | openvidu-server_1 | ======================================= openvidu-server_1 | = WAIT KIBANA = openvidu-server_1 | ======================================= openvidu-server_1 | openvidu-server_1 | Waiting for kibana in 'http://127.0.0.1/kibana' URL... openvidu-server_1 | Waiting for kibana in 'http://127.0.0.1/kibana' URL... openvidu-server_1 | Waiting for kibana in 'http://127.0.0.1/kibana' URL... openvidu-server_1 | ==== Kibana is Ready ==== openvidu-server_1 | openvidu-server_1 | ======================================= openvidu-server_1 | = LAUNCH OPENVIDU-SERVER = openvidu-server_1 | ======================================= openvidu-server_1 | [INFO] 2021-04-19 06:55:31,001 [main] io.openvidu.server.pro.OpenViduServerPro - Starting OpenViduServerPro on ip-172-31-2-47 with PID 133 (/opt/openvidu/openvidu-server.jar started by root in /opt/openvidu) openvidu-server_1 | [INFO] 2021-04-19 06:55:31,004 [main] io.openvidu.server.pro.OpenViduServerPro - No active profile set, falling back to default profiles: default openvidu-server_1 | [INFO] 2021-04-19 06:55:31,265 [main] io.openvidu.server.config.OpenviduConfig - Configuration properties read from file /opt/openvidu/.env openvidu-server_1 | [INFO] 2021-04-19 06:55:31,405 [main] io.openvidu.server.pro.OpenViduServerPro - Started OpenViduServerPro in 1.621 seconds (JVM running for 2.316) openvidu-server_1 | [INFO] 2021-04-19 06:55:31,411 [main] io.openvidu.server.config.OpenviduConfig - Configuration properties read from file /opt/openvidu/.env openvidu-server_1 | [INFO] 2021-04-19 06:55:31,414 [main] io.openvidu.server.pro.OpenViduServerPro - Cluster identifier not configured in OPENVIDU_PRO_CLUSTER_ID. Using DOMAIN_OR_PUBLIC_IP as cluster identifier: node.ratulive.com openvidu-server_1 | [INFO] 2021-04-19 06:55:31,547 [main] io.openvidu.server.pro.OpenViduServerPro - Starting OpenViduServerPro on ip-172-31-2-47 with PID 133 (/opt/openvidu/openvidu-server.jar started by root in /opt/openvidu) openvidu-server_1 | [INFO] 2021-04-19 06:55:31,552 [main] io.openvidu.server.pro.OpenViduServerPro - No active profile set, falling back to default profiles: default openvidu-server_1 | [INFO] 2021-04-19 06:55:31,612 [main] io.openvidu.server.config.OpenviduConfig - Configuration properties read from file /opt/openvidu/.env openvidu-server_1 | [INFO] 2021-04-19 06:55:31,625 [main] io.openvidu.server.pro.OpenViduServerPro - Started OpenViduServerPro in 0.204 seconds (JVM running for 2.535) openvidu-server_1 | [INFO] 2021-04-19 06:55:31,654 [main] io.openvidu.server.OpenViduServer - openvidu-server_1 | openvidu-server_1 | openvidu-server_1 | Configuration properties openvidu-server_1 | ------------------------ openvidu-server_1 | openvidu-server_1 | * ADDITIONAL_LOG_AGGREGATOR=none openvidu-server_1 | * ADDITIONAL_MONITORING=none openvidu-server_1 | * CERTIFICATE_TYPE=letsencrypt openvidu-server_1 | * DEV_CONTAINERS_CACHED=4 openvidu-server_1 | * DEV_CONTAINERS_CACHED_PATH=var-lib-docker openvidu-server_1 | * DOMAIN_OR_PUBLIC_IP=node.ratulive.com openvidu-server_1 | * ELASTICSEARCH_PASSWORD=openvidu openvidu-server_1 | * ELASTICSEARCH_USERNAME=elasticadmin openvidu-server_1 | * FILEBEAT_IMAGE= openvidu-server_1 | * HTTPS_PORT=443 openvidu-server_1 | * KMS_IMAGE= openvidu-server_1 | * KMS_URIS=[] openvidu-server_1 | * METRICBEAT_IMAGE= openvidu-server_1 | * OPENVIDU_CDR=false openvidu-server_1 | * OPENVIDU_CDR_PATH=/opt/openvidu/cdr openvidu-server_1 | * OPENVIDU_PRO_AWS_ACCESS_KEY= openvidu-server_1 | * OPENVIDU_PRO_AWS_REGION=us-east-1 openvidu-server_1 | * OPENVIDU_PRO_AWS_S3_BUCKET= openvidu-server_1 | * OPENVIDU_PRO_AWS_S3_HEADERS={} openvidu-server_1 | * OPENVIDU_PRO_AWS_SECRET_KEY= openvidu-server_1 | * OPENVIDU_PRO_CHECK_DIND_UPDATES=true openvidu-server_1 | * OPENVIDU_PRO_CLUSTER=true openvidu-server_1 | * OPENVIDU_PRO_CLUSTER_AUTOSCALING=true openvidu-server_1 | * OPENVIDU_PRO_CLUSTER_AUTOSCALING_INTERVAL=10 openvidu-server_1 | * OPENVIDU_PRO_CLUSTER_AUTOSCALING_MAX_LOAD=30 openvidu-server_1 | * OPENVIDU_PRO_CLUSTER_AUTOSCALING_MAX_NODES=2 openvidu-server_1 | * OPENVIDU_PRO_CLUSTER_AUTOSCALING_MIN_LOAD=30 openvidu-server_1 | * OPENVIDU_PRO_CLUSTER_AUTOSCALING_MIN_NODES=1 openvidu-server_1 | * OPENVIDU_PRO_CLUSTER_ENVIRONMENT=aws openvidu-server_1 | * OPENVIDU_PRO_CLUSTER_ID= openvidu-server_1 | * OPENVIDU_PRO_CLUSTER_LOAD_INTERVAL=3 openvidu-server_1 | * OPENVIDU_PRO_CLUSTER_MEDIA_NODES=1 openvidu-server_1 | * OPENVIDU_PRO_CLUSTER_MODE=auto openvidu-server_1 | * OPENVIDU_PRO_CLUSTER_PATH=/opt/openvidu/cluster openvidu-server_1 | * OPENVIDU_PRO_CLUSTER_TEST=false openvidu-server_1 | * OPENVIDU_PRO_ELASTICSEARCH_MAX_DAYS_DELETE=7 openvidu-server_1 | * OPENVIDU_PRO_LICENSE=****openvidu-server_1 | * OPENVIDU_PRO_NETWORK_QUALITY=false openvidu-server_1 | * OPENVIDU_PRO_NETWORK_QUALITY_INTERVAL=5 openvidu-server_1 | * OPENVIDU_PRO_PRIVATE_IP= openvidu-server_1 | * OPENVIDU_PRO_RECORDING_COMPOSED_EXTERNAL=true openvidu-server_1 | * OPENVIDU_PRO_RECORDING_STORAGE=local openvidu-server_1 | * OPENVIDU_PRO_REPLICATION_MANAGER_WEBHOOK= openvidu-server_1 | * OPENVIDU_PRO_STATS_MONITORING_INTERVAL=10 openvidu-server_1 | * OPENVIDU_PRO_STATS_SERVER_INTERVAL=10 openvidu-server_1 | * OPENVIDU_PRO_STATS_SESSION_INTERVAL=5 openvidu-server_1 | * OPENVIDU_PRO_STATS_WEBRTC_INTERVAL=30 openvidu-server_1 | * OPENVIDU_RECORDING=true openvidu-server_1 | * OPENVIDU_RECORDING_AUTOSTOP_TIMEOUT=120 openvidu-server_1 | * OPENVIDU_RECORDING_COMPOSED_BASICAUTH=true openvidu-server_1 | * OPENVIDU_RECORDING_COMPOSED_URL= openvidu-server_1 | * OPENVIDU_RECORDING_CUSTOM_LAYOUT=/opt/openvidu/custom-layout openvidu-server_1 | * OPENVIDU_RECORDING_DEBUG=false openvidu-server_1 | * OPENVIDU_RECORDING_NOTIFICATION=publisher_moderator openvidu-server_1 | * OPENVIDU_RECORDING_PATH=/opt/openvidu/recordings openvidu-server_1 | * OPENVIDU_RECORDING_PUBLIC_ACCESS=false openvidu-server_1 | * OPENVIDU_RECORDING_VERSION=2.17.0 openvidu-server_1 | * OPENVIDU_SECRET=OPEN_VIDU openvidu-server_1 | * OPENVIDU_SESSIONS_GARBAGE_INTERVAL=900 openvidu-server_1 | * OPENVIDU_SESSIONS_GARBAGE_THRESHOLD=3600 openvidu-server_1 | * OPENVIDU_STREAMS_ALLOW_TRANSCODING=false openvidu-server_1 | * OPENVIDU_STREAMS_FORCED_VIDEO_CODEC=VP8 openvidu-server_1 | * OPENVIDU_STREAMS_VIDEO_MAX_RECV_BANDWIDTH=1000 openvidu-server_1 | * OPENVIDU_STREAMS_VIDEO_MAX_SEND_BANDWIDTH=1000 openvidu-server_1 | * OPENVIDU_STREAMS_VIDEO_MIN_RECV_BANDWIDTH=300 openvidu-server_1 | * OPENVIDU_STREAMS_VIDEO_MIN_SEND_BANDWIDTH=300 openvidu-server_1 | * OPENVIDU_WEBHOOK=false openvidu-server_1 | * OPENVIDU_WEBHOOK_ENDPOINT= openvidu-server_1 | * OPENVIDU_WEBHOOK_EVENTS=[sessionCreated,sessionDestroyed,participantJoined,participantLeft,webrtcConnectionCreated,webrtcConnectionDestroyed,recordingStatusChanged,filterEventDispatched,mediaNodeStatusChanged] openvidu-server_1 | * OPENVIDU_WEBHOOK_HEADERS=[] openvidu-server_1 | openvidu-server_1 | openvidu-server_1 | openvidu-server_1 | [WARN] 2021-04-19 06:55:31,676 [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 (443) 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-04-19 06:55:31,854 [main] io.openvidu.server.pro.OpenViduServerPro - Starting OpenViduServerPro on ip-172-31-2-47 with PID 133 (/opt/openvidu/openvidu-server.jar started by root in /opt/openvidu) openvidu-server_1 | [INFO] 2021-04-19 06:55:31,854 [main] io.openvidu.server.pro.OpenViduServerPro - No active profile set, falling back to default profiles: default openvidu-server_1 | [INFO] 2021-04-19 06:55:33,859 [main] io.openvidu.server.config.OpenviduConfig - Configuration properties read from file /opt/openvidu/.env openvidu-server_1 | [INFO] 2021-04-19 06:55:34,180 [main] org.springframework.boot.web.embedded.tomcat.TomcatWebServer - Tomcat initialized with port(s): 5443 (http) openvidu-server_1 | [INFO] 2021-04-19 06:55:34,193 [main] org.apache.catalina.core.StandardService - Starting service [Tomcat] openvidu-server_1 | [INFO] 2021-04-19 06:55:34,193 [main] org.apache.catalina.core.StandardEngine - Starting Servlet engine: [Apache Tomcat/9.0.39] openvidu-server_1 | [WARN] 2021-04-19 06:55:35,949 [main] com.github.dockerjava.core.DockerClientBuilder - 'dockerHttpClient' should be set.Falling back to Jersey, will be an error in future releases. openvidu-server_1 | [INFO] 2021-04-19 06:55:36,583 [main] io.openvidu.server.utils.DockerManager - Docker is installed and enabled openvidu-server_1 | [INFO] 2021-04-19 06:55:36,586 [main] io.openvidu.server.recording.service.RecordingManager - Initializing recording paths openvidu-server_1 | [INFO] 2021-04-19 06:55:36,587 [main] io.openvidu.server.recording.service.RecordingManager - OpenVidu Server has write permissions on recording path: /opt/openvidu/recordings/ openvidu-server_1 | [WARN] 2021-04-19 06:55:36,591 [main] io.openvidu.server.recording.service.RecordingManager - No KMSs were defined in KMS_URIS array. Recording path check aborted openvidu-server_1 | [INFO] 2021-04-19 06:55:36,592 [main] io.openvidu.server.recording.service.RecordingManager - OpenVidu Server has read permissions on custom layout path: /opt/openvidu/custom-layout/ openvidu-server_1 | [INFO] 2021-04-19 06:55:36,592 [main] io.openvidu.server.recording.service.RecordingManager - Custom layouts path successfully initialized at /opt/openvidu/custom-layout/ openvidu-server_1 | [INFO] 2021-04-19 06:55:36,592 [main] io.openvidu.server.recording.service.RecordingManager - Recording path successfully initialized at /opt/openvidu/recordings/ openvidu-server_1 | [WARN] 2021-04-19 06:55:36,593 [main] com.github.dockerjava.core.DockerClientBuilder - 'dockerHttpClient' should be set.Falling back to Jersey, will be an error in future releases. openvidu-server_1 | [INFO] 2021-04-19 06:55:36,754 [main] io.openvidu.server.pro.infrastructure.InfrastructureManager - Using path "/opt/openvidu/cluster/aws/" as clustering path (set with property "OPENVIDU_PRO_CLUSTER_PATH") openvidu-server_1 | [INFO] 2021-04-19 06:55:36,755 [main] io.openvidu.server.pro.infrastructure.InfrastructureManager - Scripts "openvidu_launch_kms.sh" and "openvidu_drop.sh" found in path "/opt/openvidu/cluster/aws/". OpenVidu Server Pro has execute permissions over them openvidu-server_1 | [INFO] 2021-04-19 06:55:36,755 [main] io.openvidu.server.pro.infrastructure.InfrastructureManager - Script "openvidu_autodiscover.sh" found in path "/opt/openvidu/cluster/aws/". OpenVidu Server Pro has execute permissions over it. Autodiscovery process is possible openvidu-server_1 | [INFO] 2021-04-19 06:55:36,755 [main] io.openvidu.server.pro.infrastructure.InfrastructureManager - Folder "/opt/openvidu/cluster/aws/output" for storing on_premise custom script outputs already existed openvidu-server_1 | [INFO] 2021-04-19 06:55:36,755 [main] io.openvidu.server.pro.infrastructure.InfrastructureManager - Autodiscovering Media Nodes... openvidu-server_1 | [INFO] 2021-04-19 06:55:36,755 [main] io.openvidu.server.pro.infrastructure.onpremise.OnpremiseInfrastructureManager - Autodiscovering 'aws' instances openvidu-server_1 | [INFO] 2021-04-19 06:55:40,193 [main] io.openvidu.server.pro.infrastructure.onpremise.OnpremiseInfrastructureManager - Provisioning media-node 172.31.3.157 if containers are not running openvidu-server_1 | [INFO] 2021-04-19 06:55:40,200 [main] io.openvidu.server.pro.infrastructure.mncontroller.MediaNodeControllerDockerManager - Getting env variable from media-node-controller with ip 172.31.3.157 openvidu-server_1 | [INFO] 2021-04-19 06:55:40,201 [main] io.openvidu.server.pro.infrastructure.mncontroller.MediaNodeControllerDockerManager - Media Node Controller HTTP-GET request: GET http://172.31.3.157:3000/media-node/getEnvVariable/KMS_IMAGE HTTP/1.1 openvidu-server_1 | [INFO] 2021-04-19 06:55:40,218 [main] io.openvidu.server.pro.infrastructure.mncontroller.MediaNodeControllerDockerManager - Checking if Image 'openvidu/openvidu-recording:2.17.0' exists in 172.31.3.157 openvidu-server_1 | [INFO] 2021-04-19 06:55:40,218 [main] io.openvidu.server.pro.infrastructure.mncontroller.MediaNodeControllerDockerManager - Media Node Controller HTTP-POST request: POST http://172.31.3.157:3000/media-node/checkImageExists/ HTTP/1.1 openvidu-server_1 | [INFO] 2021-04-19 06:55:40,226 [main] io.openvidu.server.pro.infrastructure.mncontroller.MediaNodeControllerDockerManager - Checking if Image 'kurento/kurento-media-server:6.16.0' exists in 172.31.3.157 openvidu-server_1 | [INFO] 2021-04-19 06:55:40,226 [main] io.openvidu.server.pro.infrastructure.mncontroller.MediaNodeControllerDockerManager - Media Node Controller HTTP-POST request: POST http://172.31.3.157:3000/media-node/checkImageExists/ HTTP/1.1 openvidu-server_1 | [INFO] 2021-04-19 06:55:40,232 [main] io.openvidu.server.pro.infrastructure.mncontroller.MediaNodeControllerDockerManager - Checking if container 'kms' is running in 172.31.3.157 openvidu-server_1 | [INFO] 2021-04-19 06:55:40,232 [main] io.openvidu.server.pro.infrastructure.mncontroller.MediaNodeControllerDockerManager - Media Node Controller HTTP-GET request: GET http://172.31.3.157:3000/media-node/isContainerRunning/kms HTTP/1.1 openvidu-server_1 | [INFO] 2021-04-19 06:55:40,238 [main] io.openvidu.server.pro.infrastructure.mncontroller.MediaNodeControllerDockerManager - Getting container Id of container with name: kms openvidu-server_1 | [INFO] 2021-04-19 06:55:40,238 [main] io.openvidu.server.pro.infrastructure.mncontroller.MediaNodeControllerDockerManager - Media Node Controller HTTP-GET request: GET http://172.31.3.157:3000/media-node/getContainerIdByName/kms HTTP/1.1 openvidu-server_1 | [INFO] 2021-04-19 06:55:40,242 [main] io.openvidu.server.pro.infrastructure.mncontroller.MediaNodeProvisioner - Container kms is already possibly running at Media Node 172.31.3.157 openvidu-server_1 | [INFO] 2021-04-19 06:55:40,243 [main] io.openvidu.server.pro.infrastructure.mncontroller.MediaNodeControllerDockerManager - Getting container labels of container with name: kms openvidu-server_1 | [INFO] 2021-04-19 06:55:40,244 [main] io.openvidu.server.pro.infrastructure.mncontroller.MediaNodeControllerDockerManager - Media Node Controller HTTP-GET request: GET http://172.31.3.157:3000/media-node/getLabelsFromContainerNameOrId/kms HTTP/1.1 openvidu-server_1 | [INFO] 2021-04-19 06:55:40,254 [main] io.openvidu.server.pro.infrastructure.mncontroller.MediaNodeProvisioner - The configuration properties of service kms have NOT changed at Media Node 172.31.3.157: {'configuration': '{"KURENTO_LOGS_PATH":"/opt/openvidu/kurento-logs","KMS_MIN_PORT":"40000","KURENTO_LOG_FILE_SIZE":"100","KMS_MAX_PORT":"65535"}', 'kmsImage: 'kurento/kurento-media-server:6.16.0', 'mediaNodePrivateIp': '172.31.3.157'} openvidu-server_1 | [INFO] 2021-04-19 06:55:40,254 [main] io.openvidu.server.pro.infrastructure.mncontroller.MediaNodeProvisioner - It is NOT necessary to restart service kms of Media Node 172.31.3.157 openvidu-server_1 | [INFO] 2021-04-19 06:55:40,255 [main] io.openvidu.server.pro.infrastructure.mncontroller.MediaNodeControllerDockerManager - Getting env variable from media-node-controller with ip 172.31.3.157 openvidu-server_1 | [INFO] 2021-04-19 06:55:40,255 [main] io.openvidu.server.pro.infrastructure.mncontroller.MediaNodeControllerDockerManager - Media Node Controller HTTP-GET request: GET http://172.31.3.157:3000/media-node/getEnvVariable/METRICBEAT_IMAGE HTTP/1.1 openvidu-server_1 | [INFO] 2021-04-19 06:55:40,261 [main] io.openvidu.server.pro.infrastructure.mncontroller.MediaNodeControllerDockerManager - Getting OpenVidu IP from Media Node Request 172.31.3.157 openvidu-server_1 | [INFO] 2021-04-19 06:55:40,261 [main] io.openvidu.server.pro.infrastructure.mncontroller.MediaNodeControllerDockerManager - Media Node Controller HTTP-GET request: GET http://172.31.3.157:3000/media-node/getRequestIp/ HTTP/1.1 openvidu-server_1 | [INFO] 2021-04-19 06:55:40,264 [main] io.openvidu.server.pro.infrastructure.mncontroller.MediaNodeControllerDockerManager - Checking if container 'metricbeat-elasticsearch' is running in 172.31.3.157 openvidu-server_1 | [INFO] 2021-04-19 06:55:40,265 [main] io.openvidu.server.pro.infrastructure.mncontroller.MediaNodeControllerDockerManager - Media Node Controller HTTP-GET request: GET http://172.31.3.157:3000/media-node/isContainerRunning/metricbeat-elasticsearch HTTP/1.1 openvidu-server_1 | [INFO] 2021-04-19 06:55:40,269 [main] io.openvidu.server.pro.infrastructure.mncontroller.MediaNodeControllerDockerManager - Getting container Id of container with name: metricbeat-elasticsearch openvidu-server_1 | [INFO] 2021-04-19 06:55:40,269 [main] io.openvidu.server.pro.infrastructure.mncontroller.MediaNodeControllerDockerManager - Media Node Controller HTTP-GET request: GET http://172.31.3.157:3000/media-node/getContainerIdByName/metricbeat-elasticsearch HTTP/1.1 openvidu-server_1 | [INFO] 2021-04-19 06:55:40,273 [main] io.openvidu.server.pro.infrastructure.mncontroller.MediaNodeProvisioner - Container metricbeat-elasticsearch is already possibly running at Media Node 172.31.3.157 openvidu-server_1 | [INFO] 2021-04-19 06:55:40,274 [main] io.openvidu.server.pro.infrastructure.mncontroller.MediaNodeControllerDockerManager - Getting container labels of container with name: metricbeat-elasticsearch openvidu-server_1 | [INFO] 2021-04-19 06:55:40,274 [main] io.openvidu.server.pro.infrastructure.mncontroller.MediaNodeControllerDockerManager - Media Node Controller HTTP-GET request: GET http://172.31.3.157:3000/media-node/getLabelsFromContainerNameOrId/metricbeat-elasticsearch HTTP/1.1 openvidu-server_1 | [INFO] 2021-04-19 06:55:40,300 [main] io.openvidu.server.pro.infrastructure.mncontroller.MediaNodeProvisioner - The configuration properties of service metricbeat-elasticsearch have NOT changed at Media Node 172.31.3.157: {'image': 'docker.elastic.co/beats/metricbeat-oss:7.8.0', 'outputHost: 'http://172.31.2.47:9200', 'esUserName': 'elasticadmin', 'esPassword': 'openvidu', 'clusterId': 'node.ratulive.com', 'nodeId': 'null', 'loadInterval': 10, 'mediaNodePrivateIp': '172.31.3.157', 'volumes': ["/opt/openvidu/beats/metricbeat-elasticsearch.yml:/usr/share/metricbeat/metricbeat.yml:ro","/proc:/hostfs/proc:ro","/sys/fs/cgroup:/hostfs/sys/fs/cgroup:ro","/:/hostfs:ro","/var/run/docker.sock:/var/run/docker.sock:rw"], 'environmentVariables': ["OPENVIDU_PRO_STATS_MONITORING_INTERVAL\u003d10","MEDIA_NODE_IP\u003d172.31.3.157","CLUSTER_ID\u003dnode.ratulive.com","NODE_ID\u003dmedia_i-031da4445f0cb508b"]} openvidu-server_1 | [INFO] 2021-04-19 06:55:40,300 [main] io.openvidu.server.pro.infrastructure.mncontroller.MediaNodeProvisioner - It is NOT necessary to restart service metricbeat-elasticsearch of Media Node 172.31.3.157 openvidu-server_1 | [INFO] 2021-04-19 06:55:40,302 [main] io.openvidu.server.pro.infrastructure.mncontroller.MediaNodeControllerDockerManager - Getting env variable from media-node-controller with ip 172.31.3.157 openvidu-server_1 | [INFO] 2021-04-19 06:55:40,302 [main] io.openvidu.server.pro.infrastructure.mncontroller.MediaNodeControllerDockerManager - Media Node Controller HTTP-GET request: GET http://172.31.3.157:3000/media-node/getEnvVariable/FILEBEAT_IMAGE HTTP/1.1 openvidu-server_1 | [INFO] 2021-04-19 06:55:40,306 [main] io.openvidu.server.pro.infrastructure.mncontroller.MediaNodeControllerDockerManager - Getting OpenVidu IP from Media Node Request 172.31.3.157 openvidu-server_1 | [INFO] 2021-04-19 06:55:40,306 [main] io.openvidu.server.pro.infrastructure.mncontroller.MediaNodeControllerDockerManager - Media Node Controller HTTP-GET request: GET http://172.31.3.157:3000/media-node/getRequestIp/ HTTP/1.1 openvidu-server_1 | [INFO] 2021-04-19 06:55:40,309 [main] io.openvidu.server.pro.infrastructure.mncontroller.MediaNodeControllerDockerManager - Checking if container 'filebeat-elasticsearch' is running in 172.31.3.157 openvidu-server_1 | [INFO] 2021-04-19 06:55:40,310 [main] io.openvidu.server.pro.infrastructure.mncontroller.MediaNodeControllerDockerManager - Media Node Controller HTTP-GET request: GET http://172.31.3.157:3000/media-node/isContainerRunning/filebeat-elasticsearch HTTP/1.1 openvidu-server_1 | [INFO] 2021-04-19 06:55:40,314 [main] io.openvidu.server.pro.infrastructure.mncontroller.MediaNodeControllerDockerManager - Getting container Id of container with name: filebeat-elasticsearch openvidu-server_1 | [INFO] 2021-04-19 06:55:40,314 [main] io.openvidu.server.pro.infrastructure.mncontroller.MediaNodeControllerDockerManager - Media Node Controller HTTP-GET request: GET http://172.31.3.157:3000/media-node/getContainerIdByName/filebeat-elasticsearch HTTP/1.1 openvidu-server_1 | [INFO] 2021-04-19 06:55:40,318 [main] io.openvidu.server.pro.infrastructure.mncontroller.MediaNodeProvisioner - Container filebeat-elasticsearch is already possibly running at Media Node 172.31.3.157 openvidu-server_1 | [INFO] 2021-04-19 06:55:40,319 [main] io.openvidu.server.pro.infrastructure.mncontroller.MediaNodeControllerDockerManager - Getting container labels of container with name: filebeat-elasticsearch openvidu-server_1 | [INFO] 2021-04-19 06:55:40,319 [main] io.openvidu.server.pro.infrastructure.mncontroller.MediaNodeControllerDockerManager - Media Node Controller HTTP-GET request: GET http://172.31.3.157:3000/media-node/getLabelsFromContainerNameOrId/filebeat-elasticsearch HTTP/1.1 openvidu-server_1 | [INFO] 2021-04-19 06:55:40,324 [main] io.openvidu.server.pro.infrastructure.mncontroller.MediaNodeProvisioner - The configuration properties of service filebeat-elasticsearch have NOT changed at Media Node 172.31.3.157: {'image': 'docker.elastic.co/beats/filebeat-oss:7.8.0', 'outputHost: 'http://172.31.2.47:9200', 'esUserName': 'elasticadmin', 'esPassword': 'openvidu', 'clusterId': 'node.ratulive.com', 'nodeId': 'null', 'loadInterval': null, 'mediaNodePrivateIp': '172.31.3.157', 'volumes': ["/opt/openvidu/beats/filebeat.yml:/usr/share/filebeat/filebeat.yml","/var/lib/docker:/var/lib/docker","/var/run/docker.sock:/var/run/docker.sock","/opt/openvidu/kurento-logs:/opt/openvidu/kurento-logs"], 'environmentVariables': ["MEDIA_NODE_IP\u003d172.31.3.157","CLUSTER_ID\u003dnode.ratulive.com","NODE_ID\u003dmedia_i-031da4445f0cb508b"]} openvidu-server_1 | [INFO] 2021-04-19 06:55:40,324 [main] io.openvidu.server.pro.infrastructure.mncontroller.MediaNodeProvisioner - It is NOT necessary to restart service filebeat-elasticsearch of Media Node 172.31.3.157 openvidu-server_1 | [INFO] 2021-04-19 06:55:40,358 [main] io.openvidu.server.pro.infrastructure.onpremise.OnpremiseInfrastructureManager - Autodiscovered 1 instances with ips [172.31.3.157] openvidu-server_1 | [INFO] 2021-04-19 06:55:40,375 [I/O dispatcher 1] io.openvidu.server.pro.cdr.CDRLoggerElasticSearch - New event of type "cdr" sent to Elasticsearch: {"timestamp":1618815340329,"id":"media_i-031da4445f0cb508b","environmentId":"i-031da4445f0cb508b","ip":"172.31.3.157","uri":null,"newStatus":"launching","oldStatus":null,"clusterId":"node.ratulive.com","event":"mediaNodeStatusChanged","elastic_type":"cdr","cluster_id":"node.ratulive.com","master_node_id":"master_i-0def20d06bcc6d2e7"} openvidu-server_1 | [INFO] 2021-04-19 06:55:40,392 [main] org.kurento.jsonrpc.client.JsonRpcClientNettyWebSocket - Connecting native client openvidu-server_1 | [INFO] 2021-04-19 06:55:40,392 [main] org.kurento.jsonrpc.client.JsonRpcClientNettyWebSocket - Creating new NioEventLoopGroup openvidu-server_1 | [INFO] 2021-04-19 06:55:40,507 [nioEventLoopGroup-2-1] org.kurento.jsonrpc.client.JsonRpcClientNettyWebSocket - Initiating new Netty channel. Will create new handler too! openvidu-server_1 | [INFO] 2021-04-19 06:55:40,629 [AbstractJsonRpcClientWebSocket-reqResEventExec-e2-t0] io.openvidu.server.kurento.kms.KmsManager - Kurento Client "connected" event for KMS ws://172.31.3.157:8888/kurento [org.kurento.client.KurentoClient@70582762] openvidu-server_1 | [INFO] 2021-04-19 06:55:40,630 [main] io.openvidu.server.kurento.kms.KmsManager - All KMSs in [ws://172.31.3.157:8888/kurento] are within reach of OpenVidu Server openvidu-server_1 | [INFO] 2021-04-19 06:55:40,681 [main] io.openvidu.server.pro.account.ClusterUsageService - Media Node media_i-031da4445f0cb508b registered into usage service openvidu-server_1 | [INFO] 2021-04-19 06:55:40,688 [main] io.openvidu.server.pro.infrastructure.metrics.MediaNodesCpuLoadCollector - CPU load gathering started for Media Node media_i-031da4445f0cb508b at 172.31.3.157. Performing every 3 seconds openvidu-server_1 | [INFO] 2021-04-19 06:55:40,689 [main] io.openvidu.server.pro.config.MicrometerSessionConfig - Registering Micrometer metrics for Media Node media_i-031da4445f0cb508b openvidu-server_1 | [INFO] 2021-04-19 06:55:40,695 [main] io.openvidu.server.pro.infrastructure.onpremise.OnpremiseInfrastructureManager - Autodiscovery process finished with 1 existing instances openvidu-server_1 | [INFO] 2021-04-19 06:55:40,695 [main] io.openvidu.server.pro.infrastructure.InfrastructureManager - Autoscaling is enabled, so property OPENVIDU_PRO_CLUSTER_MEDIA_NODES will be ignored and the desired initial number of Media Nodes will be OPENVIDU_PRO_CLUSTER_AUTOSCALING_MIN_NODES openvidu-server_1 | [INFO] 2021-04-19 06:55:40,700 [I/O dispatcher 1] io.openvidu.server.pro.cdr.CDRLoggerElasticSearch - New event of type "cdr" sent to Elasticsearch: {"timestamp":1618815340631,"id":"media_i-031da4445f0cb508b","environmentId":"i-031da4445f0cb508b","ip":"172.31.3.157","uri":"ws://172.31.3.157:8888/kurento","newStatus":"running","oldStatus":"launching","clusterId":"node.ratulive.com","event":"mediaNodeStatusChanged","elastic_type":"cdr","cluster_id":"node.ratulive.com","master_node_id":"master_i-0def20d06bcc6d2e7"} openvidu-server_1 | [INFO] 2021-04-19 06:55:40,734 [main] io.openvidu.server.coturn.CoturnCredentialsService - COTURN IP: 50.17.179.224 openvidu-server_1 | [INFO] 2021-04-19 06:55:40,734 [main] io.openvidu.server.coturn.CoturnCredentialsService - COTURN Redis DB accessible with string "ip=127.0.0.1 dbname=0 password=OPEN_VIDU connect_timeout=30" openvidu-server_1 | [INFO] 2021-04-19 06:55:40,734 [main] io.openvidu.server.coturn.CoturnCredentialsService - Cleaning COTURN DB... openvidu-server_1 | [INFO] 2021-04-19 06:55:40,735 [main] io.openvidu.server.coturn.CoturnCredentialsService - Path of COTURN log files: /var/log/ openvidu-server_1 | [INFO] 2021-04-19 06:55:40,744 [main] io.openvidu.server.coturn.CoturnCredentialsService - COTURN DB is now empty openvidu-server_1 | [INFO] 2021-04-19 06:55:40,744 [main] io.openvidu.server.coturn.CoturnCredentialsService - Using COTURN credentials service for BASH environment openvidu-server_1 | [INFO] 2021-04-19 06:55:40,757 [main] io.openvidu.server.pro.utils.GeoLocationByIpPro - Trying to load user location database... openvidu-server_1 | [WARN] 2021-04-19 06:55:41,067 [Thread-5] io.openvidu.server.pro.account.LambdaService - License GET HTTP status: HTTP/1.1 500 Internal Server Error openvidu-server_1 | [ERROR] 2021-04-19 06:55:41,068 [Thread-5] io.openvidu.server.pro.account.LambdaService - License check thread threw a LambdaStatusInvalidException when consuming GET https://accounts.openvidu.io/prod/: {"status":404,"message":"License******************* does not exist"} openvidu-server_1 | [ERROR] 2021-04-19 06:55:41,068 [Thread-5] io.openvidu.server.pro.account.LambdaService - Shutting down OpenVidu Server openvidu-server_1 | [INFO] 2021-04-19 06:55:41,303 [main] io.openvidu.server.pro.utils.GeoLocationByIpPro - Database was loaded successfully openvidu-server_1 | [INFO] 2021-04-19 06:55:41,319 [main] io.openvidu.server.core.SessionManager - Garbage collector for non active sessions initialized. Running every 900 seconds and cleaning up non active Sessions more than 3600 seconds old openvidu-server_1 | [INFO] 2021-04-19 06:55:41,319 [main] io.openvidu.server.pro.kurento.core.KurentoSessionManagerPro - OpenVidu Pro network stat quality service is disabled openvidu-server_1 | [INFO] 2021-04-19 06:55:41,437 [main] org.springframework.scheduling.concurrent.ThreadPoolTaskScheduler - Initializing ExecutorService 'jsonrpcTaskScheduler' openvidu-server_1 | [INFO] 2021-04-19 06:55:41,472 [main] io.openvidu.server.pro.OpenViduServerPro - OpenVidu Pro autoscaling service is enabled openvidu-server_1 | [INFO] 2021-04-19 06:55:41,475 [main] io.openvidu.server.pro.infrastructure.autoscaling.AutoscalingApplier - Autoscaling loop initialized. Current period set to 10 seconds openvidu-server_1 | [WARN] 2021-04-19 06:55:41,490 [main] io.openvidu.server.pro.config.KibanaConfig - Kibana returned an unexpected response to GET: 404 openvidu-server_1 | [INFO] 2021-04-19 06:55:41,490 [main] io.openvidu.server.pro.config.KibanaConfig - ELK is not OpenDistro openvidu-server_1 | [INFO] 2021-04-19 06:55:41,615 [main] io.openvidu.server.pro.config.KibanaConfig - Kibana is accessible at http://127.0.0.1/kibana openvidu-server_1 | [INFO] 2021-04-19 06:55:41,616 [main] io.openvidu.server.pro.config.KibanaConfig - Kibana version is 7.8.0 openvidu-server_1 | [INFO] 2021-04-19 06:55:41,713 [main] io.openvidu.server.pro.config.KibanaConfig - Kibana already has default dashboards imported [OpenVidu Recordings, CPU vs Sessions/Connections/Streams/Recordings, [Metricbeat] Node Monitoring Metrics, OpenVidu Sessions, [Metricbeat] Cluster Monitoring Metrics, Server Monitoring Metrics, Server Application Metrics, [Metricbeat] Nginx Metrics] openvidu-server_1 | [INFO] 2021-04-19 06:55:41,770 [main] io.openvidu.server.pro.config.ElasticSearchConfig - Elasticsearch index "filebeat-nginx-2021.04.19" already exists openvidu-server_1 | OpenVidu is ready! openvidu-server_1 | * OpenVidu Server URL: https://node.ratulive.com/ openvidu-server_1 | * OpenVidu Dashboard: https://node.ratulive.com/inspector openvidu-server_1 | [INFO] 2021-04-19 06:55:44,164 [SpringContextShutdownHook] org.springframework.scheduling.concurrent.ThreadPoolTaskExecutor - Shutting down ExecutorService 'applicationTaskExecutor' openvidu-server_1 | [INFO] 2021-04-19 06:55:44,167 [SpringContextShutdownHook] org.springframework.scheduling.concurrent.ThreadPoolTaskScheduler - Shutting down ExecutorService 'jsonrpcTaskScheduler' openvidu-server_1 | [INFO] 2021-04-19 06:55:44,167 [SpringContextShutdownHook] org.springframework.scheduling.concurrent.ThreadPoolTaskScheduler - Shutting down ExecutorService 'jsonrpcTaskScheduler' openvidu-server_1 | [INFO] 2021-04-19 06:55:44,170 [SpringContextShutdownHook] io.openvidu.server.kurento.core.KurentoParticipantEndpointConfig - Shutting down any remaining MediaEndpoint statistics gathering thread openvidu-server_1 | [INFO] 2021-04-19 06:55:44,171 [SpringContextShutdownHook] io.openvidu.server.kurento.kms.KmsManager - Closing all KurentoClients openvidu-server_1 | [WARN] 2021-04-19 06:55:44,172 [Thread-6] io.openvidu.server.pro.account.LambdaService - Usage post thread interrupted while sleeping`

---

<div class="post-metadata">

**Author:** ![prasanna\_purohit](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/prasanna_purohit/32/46_2.png) [@prasanna\_purohit](https://openvidu.discourse.group/u/prasanna_purohit)\
**Post date:** [April 20, 2021, 1:01pm UTC](https://openvidu.discourse.group/t/openvidu-pro-inspector-502-bad-gateway/2936/11 "2021-04-20T13:01:03Z")

</div>

@pabloFuente okay I got this, now I had removed License from the logs.  
how can I resolve this 404 error? why I’m getting this error?

---

<div class="post-metadata">

**Author:** ![micael.gallego](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/micael.gallego/32/2_2.png) [@micael.gallego](https://openvidu.discourse.group/u/micael.gallego)\
**Post date:** [April 21, 2021, 7:47am UTC](https://openvidu.discourse.group/t/openvidu-pro-inspector-502-bad-gateway/2936/12 "2021-04-21T07:47:25Z")

</div>

Please create a valid license from OpenVidu web site.

Regards
