# OpenViduPro deployment **URL:** \ **Category:** Issues with deployment\ **Tags:** v2\ **Created:** [January 26, 2021, 2:11pm UTC](https://openvidu.discourse.group/t/openvidupro-deployment/2605 "2021-01-26T14:11:35Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![icap84](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/icap84/32/1284_2.png) [@icap84](https://openvidu.discourse.group/u/icap84)\ **Post date:** [January 26, 2021, 2:11pm UTC](https://openvidu.discourse.group/t/openvidupro-deployment/2605/1 "2021-01-26T14:11:36Z")
Hello , I have problems with the deployment of the application pro in local machine, (we have a CE version which is in production), so I want to do some tests before replacing the CE version with the PRO one NGINX LOGS : nginx\_1 | ======================================= nginx\_1 | = START OPENVIDU PROXY = nginx\_1 | ======================================= nginx\_1 | nginx\_1 | 2021/01/26 12:08:43 [warn] 67#67: “ssl\_stapling” ignored, no OCSP responder URL in the certificate “/etc/letsencrypt/live/127.0.0.1/fullchain.pem” nginx\_1 | nginx: [warn] “ssl\_stapling” ignored, no OCSP responder URL in the certificate “/etc/letsencrypt/live/127.0.0.1/fullchain.pem” nginx\_1 | 2021/01/26 12:08:43 [notice] 67#67: signal process started nginx\_1 | 2021/01/26 12:08:43 [warn] 15#15: “ssl\_stapling” ignored, no OCSP responder URL in the certificate “/etc/letsencrypt/live/127.0.0.1/fullchain.pem” nginx\_1 | 2021/01/26 12:20:20 [error] 68#68: \*74 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: 127.0.0.1, request: “GET /kibana HTTP/1.1”, upstream: “http ://[::1]:5601/”, host: “127.0.0.1” nginx\_1 | 2021/01/26 12:20:20 [warn] 68#68: \*74 upstream server temporarily disabled while connecting to upstream, client: 127.0.0.1, server: 127.0.0.1, request: “GET /kibana HTTP/1.1”, upstream: “http ://[::1]:5601/”, host: “127.0.0.1” nginx\_1 | 2021/01/26 12:20:30 [error] 68#68: \*74 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: 127.0.0.1, request: “GET /inspector HTTP/1.1”, upstream: “http ://[::1]:5443/inspector”, host: “127.0.0.1” nginx\_1 | 2021/01/26 12:20:30 [warn] 68#68: \*74 upstream server temporarily disabled while connecting to upstream, client: 127.0.0.1, server: 127.0.0.1, request: “GET /inspector HTTP/1.1”, upstream: “http ://[::1]:5443/inspector”, host: “127.0.0.1” nginx\_1 | 2021/01/26 12:20:30 [error] 68#68: \*74 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: 127.0.0.1, request: “GET /inspector HTTP/1.1”, upstream: “http ://127.0.0.1:5443/inspector”, host: “127.0.0.1” nginx\_1 | 2021/01/26 12:20:30 [warn] 68#68: \*74 upstream server temporarily disabled while connecting to upstream, client: 127.0.0.1, server: 127.0.0.1, request: “GET /inspector HTTP/1.1”, upstream: “http ://127.0.0.1:5443/inspector”, host: “127.0.0.1” OPENVIDU LOGS : openvidu-server\_1 | [INFO] 2021-01-26 13:57:16,045 [main] io.openvidu.server.config.OpenviduConfig - Configuration properties read from file /opt/openvidu/.env openvidu-server\_1 | [INFO] 2021-01-26 13:57:16,307 [main] io.openvidu.server.pro.OpenViduServerPro - OpenVidu Pro is deployed in ‘on\_premise’ environment openvidu-server\_1 | [WARN] 2021-01-26 13:57:16,309 [main] io.openvidu.server.pro.OpenViduServerPro - OpenVidu Pro cluster mode is ‘manual’. There will be no automatic instances management openvidu-server\_1 | [INFO] 2021-01-26 13:57:16,457 [main] io.openvidu.server.pro.OpenViduServerPro - OpenVidu Pro cluster mode enabled openvidu-server\_1 | [INFO] 2021-01-26 13:57:16,473 [main] io.openvidu.server.pro.OpenViduServerPro - Cluster identifier got from disk: clu\_HHEOUiOa openvidu-server\_1 | [INFO] 2021-01-26 13:57:16,508 [main] io.openvidu.server.pro.OpenViduServerPro - OpenVidu Pro Elasticsearch service is enabled openvidu-server\_1 | [ERROR] 2021-01-26 13:57:19,804 [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-01-26 13:57:19,808 [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-01-26 13:57:19,809 [main] io.openvidu.server.pro.cdr.CDRLoggerElasticSearch - Terminating OpenVidu Server Pro ---
**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:** [January 26, 2021, 3:10pm UTC](https://openvidu.discourse.group/t/openvidupro-deployment/2605/2 "2021-01-26T15:10:42Z")
Hello: The error log is telling you what is missing: ```auto Connection to Elasticsearch failed at http://127.0.0.1:9200 (Connection is closed) If property ‘OPENVIDU_PRO_ELASTICSEARCH_HOST’ is defined, then it is mandatory that OpenVidu Server Pro is able to connect to it Terminating OpenVidu Server Pro ``` There is no Elasticsearch service available at `http://127.0.0.1:9200`. To test in local environment without OpenVidu Pro Elastic stack integration, just disable property **`OPENVIDU_PRO_ELASTICSEARCH_HOST`**. See [OpenVidu Docs](https://docs.openvidu.io/en/2.16.0/reference-docs/openvidu-config/#configuration-parameters-for-openvidu-pro) ![image](https://global.discourse-cdn.com/free1/uploads/openvidu/original/2X/c/c467952c42931e4b3944643f949cec6c048e9f43.png) If you want the Elasticsearch service in your local deployment, then you must have it up and running. The official docker-compose deployment of OpenVidu Pro already includes it: [openvidu/docker-compose.yml at master · OpenVidu/openvidu · GitHub](https://github.com/OpenVidu/openvidu/blob/master/openvidu-server/deployments/pro/docker-compose/openvidu-server-pro/docker-compose.yml#L109-L140). ---
**Author:** ![icap84](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/icap84/32/1284_2.png) [@icap84](https://openvidu.discourse.group/u/icap84)\ **Post date:** [January 26, 2021, 4:03pm UTC](https://openvidu.discourse.group/t/openvidupro-deployment/2605/3 "2021-01-26T16:03:11Z")
thanks for ur response a made both : OPENVIDU\_PRO\_KIBANA\_HOST= OPENVIDU\_PRO\_ELASTICSEARCH\_HOST= and i still have : openvidu-server\_1 | [WARN] 2021-01-26 15:56:34,102 [main] io.openvidu.server.pro.config.KibanaConfig - IOException when reaching Kibana REST API with method GET at path /api/status: null openvidu-server\_1 | [ERROR] 2021-01-26 15:56:34,103 [main] io.openvidu.server.pro.config.KibanaConfig - If property ‘OPENVIDU\_PRO\_KIBANA\_HOST’ is defined, then it is mandatory that OpenVidu Server Pro is able to connect to it openvidu-server\_1 | [ERROR] 2021-01-26 15:56:34,103 [main] io.openvidu.server.pro.config.KibanaConfig - Terminating OpenVidu Server Pro ---
**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:** [January 26, 2021, 4:43pm UTC](https://openvidu.discourse.group/t/openvidupro-deployment/2605/4 "2021-01-26T16:43:47Z")
I don’t think `OPENVIDU_PRO_KIBANA_HOST` is disabled. Please, reivew it again and make sure it is empty. ---
**Author:** ![icap84](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/icap84/32/1284_2.png) [@icap84](https://openvidu.discourse.group/u/icap84)\ **Post date:** [January 26, 2021, 5:10pm UTC](https://openvidu.discourse.group/t/openvidupro-deployment/2605/5 "2021-01-26T17:10:53Z")
this the .env file ![image](https://global.discourse-cdn.com/free1/uploads/openvidu/original/2X/e/e153e95ac9eb14368c9e89ce314b91a5b831015c.png) ---
**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:** [January 26, 2021, 7:39pm UTC](https://openvidu.discourse.group/t/openvidupro-deployment/2605/6 "2021-01-26T19:39:04Z")
How did you deployed? Do you actually have a kibana and elasticsearch running? Please can you show me the output of `docker ps` and: ```auto sudo su cd /opt/openvidu ./openvidu report ``` This will generate a report with all the information of the deployment. I think you did not follow instructions properly or something is missing. Regards, Carlos ---
**Author:** ![icap84](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/icap84/32/1284_2.png) [@icap84](https://openvidu.discourse.group/u/icap84)\ **Post date:** [January 27, 2021, 9:37am UTC](https://openvidu.discourse.group/t/openvidupro-deployment/2605/8 "2021-01-27T09:37:11Z")
I made a new vm and installed openvidu Have I to install kibana and elasticsearch separately ? docker ps ![image](https://global.discourse-cdn.com/free1/uploads/openvidu/original/2X/8/85bd1c0dc9e9cfd3985c0f8b7bbcc6f6fb7a51c2.png) report : [https://sharetxt.xyz/id?55](https://sharetxt.xyz/id?55) ---
**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:** [January 27, 2021, 10:59am UTC](https://openvidu.discourse.group/t/openvidupro-deployment/2605/10 "2021-01-27T10:59:45Z")
Just to confirm, are you trying to deploy OpenVidu Pro in your local machine? I see you’re using `DOMAIN_OR_PUBLIC_IP=127.0.0.1`. We didn’t test such scenario but I don’t think this would work as it is. 1. The main reason is that a Media Node need to be installed externally, and install OpenVidu and Media Nodes in the same machine makes some problems which needs to be solved manually and is not an easy task. 2. As it is installed locally this could cause some problems because of internal ports being used. I can see two possible solutions here: * * * **Option 1** Deploy a dev environment with two instances in your cloud provider or infrastructure, one with OpenVidu and another one with Media Node (to have at least one media node configured). I recommend to make it accesible to the internet with a valid Domain name pointing to it’s public IP. **Option 2** Deploy two VM, install OpenVidu Pro Master Node in one, and a Media Node in the other. I think that if you use the “DOMAIN\_OR\_PUBLIC\_IP” with the private IP of your VM it should work. Also you need to add in OpenVidu Pro the Media Node with its own private Ip as stated here: [OpenVidu Docs](https://docs.openvidu.io/en/2.16.0/openvidu-pro/deployment/on-premises/#change-the-number-of-media-nodes-on-the-fly) ---
**Author:** ![icap84](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/icap84/32/1284_2.png) [@icap84](https://openvidu.discourse.group/u/icap84)\ **Post date:** [January 27, 2021, 11:04am UTC](https://openvidu.discourse.group/t/openvidupro-deployment/2605/11 "2021-01-27T11:04:37Z")
thank you so much for your help ---
**Author:** ![icap84](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/icap84/32/1284_2.png) [@icap84](https://openvidu.discourse.group/u/icap84)\ **Post date:** [January 27, 2021, 11:14am UTC](https://openvidu.discourse.group/t/openvidupro-deployment/2605/12 "2021-01-27T11:14:47Z")
The problem here is that I didn’t install the Media Node, I just tested the Openvidu server and it doesn’t boot and shows the problems mentioned above