# Unable to deploy on AWS with v2.16 **URL:** \ **Category:** Issues with deployment\ **Tags:** v2\ **Created:** [November 29, 2020, 10:32pm UTC](https://openvidu.discourse.group/t/unable-to-deploy-on-aws-with-v2-16/2349 "2020-11-29T22:32:13Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![Adam](https://avatars.discourse-cdn.com/v4/letter/a/4af34b/32.png) [@Adam](https://openvidu.discourse.group/u/Adam)\ **Post date:** [November 29, 2020, 10:32pm UTC](https://openvidu.discourse.group/t/unable-to-deploy-on-aws-with-v2-16/2349/1 "2020-11-29T22:32:13Z")
The CloudFormation template for v2.16 is not working for me. v2.15 still works fine with the same parameters. The logs for v2.16… ``` root@ip-172-31-29-245:/opt/openvidu# ./openvidu logs Attaching to openvidu_openvidu-server_1 openvidu-server_1 | openvidu-server_1 | openvidu-server_1 | ======================================= openvidu-server_1 | = LAUNCH OPENVIDU-SERVER = openvidu-server_1 | ======================================= openvidu-server_1 | openvidu-server_1 | ______________________________________________ openvidu-server_1 | ______ ___ _ openvidu-server_1 | / __ \ \ \ / (_) | | openvidu-server_1 | | | | |_ _____ _ _\ \ / / _ __| |_ _ openvidu-server_1 | | | | | '_ \ / _ \ '_ \ \/ / | |/ _` | | | | openvidu-server_1 | | |__| | |_) |__/ | | \ / | | (_| | |_| | openvidu-server_1 | \ ____/| .__ / \ ___|_| |_|\/ |_|\__ ,_|\__,_| openvidu-server_1 | | | openvidu-server_1 | |_| version 2.16.0 openvidu-server_1 | ______________________________________________ openvidu-server_1 | openvidu-server_1 | [INFO] 2020-11-29 20:06:45,005 [main] io.openvidu.server.OpenViduServer - Starting OpenViduServer on ip-172-31-29-245 with PID 14 (/openvidu-server.jar started by root in /) openvidu-server_1 | [INFO] 2020-11-29 20:06:45,036 [main] io.openvidu.server.OpenViduServer - No active profile set, falling back to default profiles: default openvidu-server_1 | [ERROR] 2020-11-29 20:06:45,844 [main] io.openvidu.server.config.OpenviduConfig - .env file not found at /.env openvidu-server_1 | [INFO] 2020-11-29 20:06:46,232 [main] io.openvidu.server.OpenViduServer - Started OpenViduServer in 5.151 seconds (JVM running for 12.161) openvidu-server_1 | [INFO] 2020-11-29 20:06:46,235 [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 | * CERTIFICATE_TYPE=selfsigned openvidu-server_1 | * DOMAIN_OR_PUBLIC_IP= ***** openvidu-server_1 | * HTTPS_PORT=443 openvidu-server_1 | * KMS_URIS=["ws://localhost:8888/kurento"] openvidu-server_1 | * OPENVIDU_CDR=false openvidu-server_1 | * OPENVIDU_CDR_PATH=/opt/openvidu/cdr openvidu-server_1 | * OPENVIDU_RECORDING=false 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.16.0 openvidu-server_1 | * OPENVIDU_SECRET= ***** openvidu-server_1 | * OPENVIDU_SESSIONS_GARBAGE_INTERVAL=900 openvidu-server_1 | * OPENVIDU_SESSIONS_GARBAGE_THRESHOLD=3600 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] 2020-11-29 20:06:46,237 [main] io.openvidu.server.OpenViduServer - You have set property server.port (or SERVER_PORT). This will serve OpenVidu Server 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] 2020-11-29 20:06:46,237 [main] io.openvidu.server.OpenViduServer - Using /dev/urandom for secure random generation openvidu-server_1 | [INFO] 2020-11-29 20:06:46,430 [main] io.openvidu.server.OpenViduServer - Starting OpenViduServer on ip-172-31-29-245 with PID 14 (/openvidu-server.jar started by root in /) openvidu-server_1 | [INFO] 2020-11-29 20:06:46,431 [main] io.openvidu.server.OpenViduServer - No active profile set, falling back to default profiles: default openvidu-server_1 | [ERROR] 2020-11-29 20:06:48,803 [main] io.openvidu.server.config.OpenviduConfig - .env file not found at /.env openvidu-server_1 | [INFO] 2020-11-29 20:06:50,677 [main] org.springframework.boot.web.embedded.tomcat.TomcatWebServer - Tomcat initialized with port(s): 5443 (http) openvidu-server_1 | [INFO] 2020-11-29 20:06:50,689 [main] org.apache.coyote.http11.Http11NioProtocol - Initializing ProtocolHandler ["http-nio-0.0.0.0-5443"] openvidu-server_1 | [INFO] 2020-11-29 20:06:50,689 [main] org.apache.catalina.core.StandardService - Starting service [Tomcat] openvidu-server_1 | [INFO] 2020-11-29 20:06:50,689 [main] org.apache.catalina.core.StandardEngine - Starting Servlet engine: [Apache Tomcat/9.0.39] openvidu-server_1 | [INFO] 2020-11-29 20:06:50,763 [main] org.apache.catalina.core.ContainerBase.[Tomcat].[localhost].[/] - Initializing Spring embedded WebApplicationContext openvidu-server_1 | [INFO] 2020-11-29 20:06:50,763 [main] org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext - Root WebApplicationContext: initialization completed in 4256 ms openvidu-server_1 | [WARN] 2020-11-29 20:06:50,974 [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] 2020-11-29 20:06:50,975 [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] 2020-11-29 20:06:51,045 [main] io.openvidu.server.OpenViduServer - OpenVidu CDR service is disabled (may be enable with 'OPENVIDU_CDR=true') openvidu-server_1 | [INFO] 2020-11-29 20:06:51,045 [main] io.openvidu.server.OpenViduServer - OpenVidu Webhook service is disabled (may be enabled with 'OPENVIDU_WEBHOOK=true') openvidu-server_1 | [INFO] 2020-11-29 20:06:51,069 [main] io.openvidu.server.OpenViduServer - OpenVidu Server using one KMS: ws://localhost:8888/kurento openvidu-server_1 | [INFO] 2020-11-29 20:06:51,228 [JsonRpcClient-hearbeatExec-e1-t0] org.kurento.jsonrpc.client.JsonRpcClientNettyWebSocket - [KurentoClient] Connecting native client openvidu-server_1 | [INFO] 2020-11-29 20:06:51,229 [JsonRpcClient-hearbeatExec-e1-t0] org.kurento.jsonrpc.client.JsonRpcClientNettyWebSocket - [KurentoClient] Creating new NioEventLoopGroup openvidu-server_1 | [INFO] 2020-11-29 20:06:52,405 [nioEventLoopGroup-2-1] org.kurento.jsonrpc.client.JsonRpcClientNettyWebSocket - [KurentoClient] Initiating new Netty channel. Will create new handler too! openvidu-server_1 | [WARN] 2020-11-29 20:06:52,721 [JsonRpcClient-hearbeatExec-e1-t0] org.kurento.jsonrpc.client.JsonRpcClientNettyWebSocket - [KurentoClient] Trying to close a JsonRpcClientNettyWebSocket with channel == null openvidu-server_1 | [WARN] 2020-11-29 20:06:52,722 [JsonRpcClient-hearbeatExec-e1-t0] org.kurento.jsonrpc.client.JsonRpcClient - [KurentoClient] Error sending heartbeat to server. Exception: [KurentoClient] Exception connecting to WebSocket server ws://localhost:8888/kurento openvidu-server_1 | [INFO] 2020-11-29 20:06:52,722 [main] org.kurento.jsonrpc.client.JsonRpcClientNettyWebSocket - [KurentoClient] Connecting native client openvidu-server_1 | [WARN] 2020-11-29 20:06:52,722 [JsonRpcClient-hearbeatExec-e1-t0] org.kurento.jsonrpc.client.JsonRpcClient - [KurentoClient] Stopping heartbeat and closing client: failure during heartbeat mechanism openvidu-server_1 | [INFO] 2020-11-29 20:06:52,722 [main] org.kurento.jsonrpc.client.JsonRpcClientNettyWebSocket - [KurentoClient] Creating new NioEventLoopGroup openvidu-server_1 | [INFO] 2020-11-29 20:06:52,723 [nioEventLoopGroup-3-1] org.kurento.jsonrpc.client.JsonRpcClientNettyWebSocket - [KurentoClient] Initiating new Netty channel. Will create new handler too! openvidu-server_1 | [WARN] 2020-11-29 20:06:52,725 [main] org.kurento.jsonrpc.client.JsonRpcClientNettyWebSocket - [KurentoClient] Trying to close a JsonRpcClientNettyWebSocket with channel == null openvidu-server_1 | [ERROR] 2020-11-29 20:06:52,726 [main] io.openvidu.server.kurento.kms.KmsManager - KMS in ws://localhost:8888/kurento is not reachable by OpenVidu Server openvidu-server_1 | [ERROR] 2020-11-29 20:06:52,726 [main] io.openvidu.server.kurento.kms.KmsManager - Shutting down OpenVidu Server root@ip-172-31-29-245:/opt/openvidu# ``` There are a few errors and warnings that don’t happen when using v2.15… starting with `[WARN] 2020-11-29 20:06:52,721 [JsonRpcClient-hearbeatExec-e1-t0] org.kurento.jsonrpc.client.JsonRpcClientNettyWebSocket - [KurentoClient] Trying to close a JsonRpcClientNettyWebSocket with channel == null` I’m not seeing any errors in cloud-init.log ot cloud-init-output.log, but let me know if you need those as well. Thanks. ---
**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:** [November 30, 2020, 10:13am UTC](https://openvidu.discourse.group/t/unable-to-deploy-on-aws-with-v2-16/2349/2 "2020-11-30T10:13:52Z")
Hi, I’ve tried this and you’re right. But it happens sometimes, I will try to fix it. What you can do after the deployment fails is to execute in `/opt/openvidu` the command: ```auto sudo su ./openvidu restart ``` Regards, Carlos ---
**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:** [November 30, 2020, 11:11am UTC](https://openvidu.discourse.group/t/unable-to-deploy-on-aws-with-v2-16/2349/3 "2020-11-30T11:11:58Z")
Fixed @Adam Please, try again. Regards, Carlos ---
**Author:** ![Adam](https://avatars.discourse-cdn.com/v4/letter/a/4af34b/32.png) [@Adam](https://openvidu.discourse.group/u/Adam)\ **Post date:** [December 10, 2020, 3:53am UTC](https://openvidu.discourse.group/t/unable-to-deploy-on-aws-with-v2-16/2349/4 "2020-12-10T03:53:51Z")
Looks good now. Thanks! ---
**Author:** ![Vitalije\_Milosevic](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/vitalije_milosevic/32/1206_2.png) [@Vitalije\_Milosevic](https://openvidu.discourse.group/u/Vitalije_Milosevic)\ **Post date:** [December 12, 2020, 3:24pm UTC](https://openvidu.discourse.group/t/unable-to-deploy-on-aws-with-v2-16/2349/5 "2020-12-12T15:24:22Z")
Hello, I tried today to follow tutorial on OpenviduPro AWS deployment and it failed several times. I’ve tried to disable rollback option in order to later access server and collect logs, but I can’t access server using ssh and my key. You have suggested to execute some shell commands but what to do if I can’t access my server? ---
**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:** [December 12, 2020, 3:38pm UTC](https://openvidu.discourse.group/t/unable-to-deploy-on-aws-with-v2-16/2349/6 "2020-12-12T15:38:12Z")
Can you show me what parameters are you using in your CF? ---
**Author:** ![Sachin](https://avatars.discourse-cdn.com/v4/letter/s/c77e96/32.png) [@Sachin](https://openvidu.discourse.group/u/Sachin)\ **Post date:** [February 8, 2021, 12:37pm UTC](https://openvidu.discourse.group/t/unable-to-deploy-on-aws-with-v2-16/2349/7 "2021-02-08T12:37:23Z")
@cruizba I’m having trouble with Cloud formation too, the parameter that were working for 2.15 are failing for 2.16, i’m using c5.xlarge and letsencrypt The AWS::CloudFormation::WaitCondition is failing - Failed to receive 1 resource signal(s) within the specified duration, The CF params are: AwsInstanceTypeKMS c5.xlarge - AwsInstanceTypeOV c5.xlarge - ElasticsearchPassword \*\*\*\* - ElasticsearchUser \*\*\*\* - KeyName \*\*\*\*\*\* - LetsEncryptEmail \*\*\*\*\* - MediaNodesStartNumber 1 - MyDomainName \*\*\*\* - OpenViduLicense \*\*\*\* - OpenViduSecret \*\*\*\* - OpenViduSubnet \*\*\*\*\* - OpenViduVPC \*\*\*\*\* - OwnCertCRT - - OwnCertKEY - - PublicElasticIP \*\*\*\* - Recording local - S3RecordingsBucketName - - WantToDeployDemos false - WhichCert letsencrypt - The server keeps waiting for kibana, and then ultimately fails ---
**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:** [February 8, 2021, 1:03pm UTC](https://openvidu.discourse.group/t/unable-to-deploy-on-aws-with-v2-16/2349/8 "2021-02-08T13:03:08Z")
Can you disable rollback in AWS and show me the logs of nginx and kibana? ```auto sudo su cd /opt/openvidu docker-compose logs nginx ``` ```auto sudo su cd /opt/openvidu docker-compose logs kibana ``` Regards ---
**Author:** ![Sachin](https://avatars.discourse-cdn.com/v4/letter/s/c77e96/32.png) [@Sachin](https://openvidu.discourse.group/u/Sachin)\ **Post date:** [February 8, 2021, 1:50pm UTC](https://openvidu.discourse.group/t/unable-to-deploy-on-aws-with-v2-16/2349/9 "2021-02-08T13:50:47Z")
Hi @cruizba It started working now, we were having trouble with c5.large, then after multiple failed attempts, we switched to c5.xlarge, but due to multiple restarts, letsencrypt rate limit was hit, after switching to new sub domain, it started working. Thanks anyway ---
**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:** [February 8, 2021, 2:09pm UTC](https://openvidu.discourse.group/t/unable-to-deploy-on-aws-with-v2-16/2349/10 "2021-02-08T14:09:04Z")
Yes, we may need to remove this instance type from the CloudFormation. 4GB of RAM is not enough for Elasticsearch and Kibana to run properly. ---
**Author:** ![Sachin](https://avatars.discourse-cdn.com/v4/letter/s/c77e96/32.png) [@Sachin](https://openvidu.discourse.group/u/Sachin)\ **Post date:** [February 8, 2021, 2:27pm UTC](https://openvidu.discourse.group/t/unable-to-deploy-on-aws-with-v2-16/2349/11 "2021-02-08T14:27:43Z")
is there a way to disable kibana and elasticsearch? if not, can we point them to an external service that responds with status 200 always, will that work to keep running pro instance on c5.large? ---
**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:** [February 8, 2021, 2:34pm UTC](https://openvidu.discourse.group/t/unable-to-deploy-on-aws-with-v2-16/2349/12 "2021-02-08T14:34:52Z")
It’s not possible right now to disable Elasticsearch and Kibana. I did not test such scenario with a “dummy service” it may work but I can’t confirm. ---
**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:** [February 8, 2021, 2:40pm UTC](https://openvidu.discourse.group/t/unable-to-deploy-on-aws-with-v2-16/2349/13 "2021-02-08T14:40:15Z")
Anyways, OpenVidu Pro will not work properly without Elasticsearch and Kibana because a lot of functionality depends on it. For example, session history and a lot of statistics. ---
**Author:** ![Sachin](https://avatars.discourse-cdn.com/v4/letter/s/c77e96/32.png) [@Sachin](https://openvidu.discourse.group/u/Sachin)\ **Post date:** [February 8, 2021, 2:41pm UTC](https://openvidu.discourse.group/t/unable-to-deploy-on-aws-with-v2-16/2349/14 "2021-02-08T14:41:24Z")
Ok, thanks, i’ll give it a shot maybe and see what happens