Kibana is not accessible - Connection refused (Connection refused)

ertan · May 11, 2020, 10:21am

Hi,

I just purchased OpenVidu and wanted to deploy it on my linux server. I downloaded and configured docker file. When i start OpenVidu by ./openvidu start it gives the following log

openvidu-server_1 | [INFO] 2020-05-11 10:12:25,021 [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] 2020-05-11 10:12:25,132 [main] io.openvidu.server.recording.service.RecordingManager - OpenVidu r
ecording service is disabled
openvidu-server_1 | [INFO] 2020-05-11 10:12:25,250 [main] org.springframework.scheduling.concurrent.ThreadPoolTaskScheduler
Initializing ExecutorService ‘jsonrpcTaskScheduler’
openvidu-server_1 | [WARN] 2020-05-11 10:12:25,337 [main] io.openvidu.server.pro.config.KibanaConfig - Kibana is not accessi
ble at http://127.0.0.1:80: Connect to 127.0.0.1:80 [/127.0.0.1] failed: Connection refused (Connection refused)
openvidu-server_1 | [ERROR] 2020-05-11 10:12:25,337 [main] io.openvidu.server.pro.config.KibanaConfig - If property ‘OPENVID
U_PRO_KIBANA_HOST’ is defined, then it is mandatory that OpenVidu Server Pro is able to connect to it
openvidu-server_1 | [ERROR] 2020-05-11 10:12:25,337 [main] io.openvidu.server.pro.config.KibanaConfig - Terminating OpenVidu
Server Pro

I guess, I am missing something here. My server has nginx installation. I tried to start OpenVidu by stopped the nginx server on my linux but still no luck. Can you tell me what am I missing?

Best

micael.gallego · May 11, 2020, 10:58am

OpenVidu installation procedures are designed to be installed in an empty machine because it needs several available ports in the machine:

We recently add some information to our documentation regarding to this:

Free ports inside the server : OpenVidu Server Pro Node services will need the following ports to be available inside the machine: 80, 443, 3478, 5442, 5443, 6379. If some of these ports is used by any process, OpenVidu platform won’t work correctly. It is a typical error to have an NGINX process in the system before installing OpenVidu. Please uninstall it.

If you still need to use your own NGINX in the machine, wait until 2.14 release (to be published tomorrow) to be able to change OpenVidu NGINX ports (80 and 443).

Can you stop other services and try again and share with us all openvidu services logs to see what is wrong?

Regards

ertan · May 11, 2020, 11:19am

@micael.gallego,

thank you for your reply. I uninstalled NGINX and retried but still the same problem.

Here are the logs from OpenVidu

io.openvidu.server.pro.OpenViduServerPro - Started OpenViduServerPro in 3.595 seconds (JVM running for 5.116)

openvidu-server_1 | [INFO] 2020-05-11 11:12:06,626 [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=letsencrypt
openvidu-server_1 | * OPENVIDU_CDR=false
openvidu-server_1 | * OPENVIDU_CDR_PATH=/opt/openvidu/cdr
openvidu-server_1 | * OPENVIDU_DOMAIN_OR_PUBLIC_IP={MY_HOST_NAME}
openvidu-server_1 | * OPENVIDU_PRO_CLUSTER=true
openvidu-server_1 | * OPENVIDU_PRO_CLUSTER_AUTODISCOVERY=true
openvidu-server_1 | * OPENVIDU_PRO_CLUSTER_ENVIRONMENT=on_premise
openvidu-server_1 | * OPENVIDU_PRO_CLUSTER_ID=
openvidu-server_1 | * OPENVIDU_PRO_CLUSTER_LOAD_STRATEGY=streams
openvidu-server_1 | * OPENVIDU_PRO_CLUSTER_MEDIA_NODES=1
openvidu-server_1 | * OPENVIDU_PRO_CLUSTER_MODE=manual
openvidu-server_1 | * OPENVIDU_PRO_CLUSTER_PATH=/opt/openvidu/cluster
openvidu-server_1 | * OPENVIDU_PRO_CLUSTER_TEST=false
openvidu-server_1 | * OPENVIDU_PRO_LICENSE=MY_LICENCE
openvidu-server_1 | * OPENVIDU_PRO_STATS_MONITORING_INTERVAL=30
openvidu-server_1 | * OPENVIDU_PRO_STATS_WEBRTC_INTERVAL=30
openvidu-server_1 | * OPENVIDU_RECORDING=false
openvidu-server_1 | * OPENVIDU_RECORDING_AUTOSTOP_TIMEOUT=120
openvidu-server_1 | * OPENVIDU_RECORDING_COMPOSED_URL=
openvidu-server_1 | * OPENVIDU_RECORDING_CUSTOM_LAYOUT=/opt/openvidu/custom-layout
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.9.0
openvidu-server_1 | * OPENVIDU_SECRET=MY_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 |
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.13.0
openvidu-server_1 | ______________________________________________________________
openvidu-server_1 |
openvidu-server_1 | [INFO] 2020-05-11 11:12:06,748 [main] io.openvidu.server.pro.OpenViduServerPro - Starting OpenViduServerPro on MY_DOMAIN with PID 20 (/opt/openvidu/openvidu-server.jar started by root in /opt/openvidu)
openvidu-server_1 | [INFO] 2020-05-11 11:12:06,748 [main] io.openvidu.server.pro.OpenViduServerPro - No active profile set, falling back to default profiles: default
openvidu-server_1 | [INFO] 2020-05-11 11:12:09,703 [main] io.openvidu.server.config.OpenviduConfig - Configuration properties read from file /opt/openvidu/.env
openvidu-server_1 | [INFO] 2020-05-11 11:12:10,767 [main] org.springframework.boot.web.embedded.tomcat.TomcatWebServer - Tomcat initialized with port(s): 5443 (http)
openvidu-server_1 | [INFO] 2020-05-11 11:12:10,794 [main] org.apache.coyote.http11.Http11NioProtocol - Initializing ProtocolHandler [“http-nio-0.0.0.0-5443”]
openvidu-server_1 | [INFO] 2020-05-11 11:12:10,794 [main] org.apache.catalina.core.StandardService - Starting service [Tomcat]
openvidu-server_1 | [INFO] 2020-05-11 11:12:10,795 [main] org.apache.catalina.core.StandardEngine - Starting Servlet engine: [Apache Tomcat/9.0.30]
openvidu-server_1 | [INFO] 2020-05-11 11:12:10,960 [main] org.apache.catalina.core.ContainerBase.[Tomcat].[localhost].[/] - Initializing Spring embedded WebApplicationContext
openvidu-server_1 | [INFO] 2020-05-11 11:12:10,960 [main] org.springframework.web.context.ContextLoader - Root WebApplicationContext: initialization completed in 4180 ms
openvidu-server_1 | [INFO] 2020-05-11 11:12:11,558 [main] io.openvidu.server.config.OpenviduConfig - Configuration properties read from file /opt/openvidu/.env
openvidu-server_1 | [INFO] 2020-05-11 11:12:11,645 [main] io.openvidu.server.pro.OpenViduServerPro - OpenVidu Pro is deployed in ‘on_premise’ environment
openvidu-server_1 | [WARN] 2020-05-11 11:12:11,646 [main] io.openvidu.server.pro.OpenViduServerPro - OpenVidu Pro cluster mode is ‘manual’. There will be no automatic instances management
openvidu-server_1 | [INFO] 2020-05-11 11:12:11,790 [main] io.openvidu.server.coturn.CoturnCredentialsService - COTURN IP: 185.210.95.198
openvidu-server_1 | [INFO] 2020-05-11 11:12:11,790 [main] io.openvidu.server.coturn.CoturnCredentialsService - COTURN Redis DB accessible with string “ip=127.0.0.1 dbname=0 password=turn connect_timeout=30”
openvidu-server_1 | [INFO] 2020-05-11 11:12:11,790 [main] io.openvidu.server.coturn.CoturnCredentialsService - Cleaning COTURN DB…
openvidu-server_1 | [INFO] 2020-05-11 11:12:11,790 [main] io.openvidu.server.coturn.CoturnCredentialsService - Path of COTURN log files: /var/log/
openvidu-server_1 | [ERROR] 2020-05-11 11:12:11,799 [main] io.openvidu.server.coturn.CoturnCredentialsService - COTURN DB is not empty
openvidu-server_1 | [INFO] 2020-05-11 11:12:11,799 [main] io.openvidu.server.coturn.CoturnCredentialsService - Using COTURN credentials service for BASH environment
openvidu-server_1 | [INFO] 2020-05-11 11:12:11,818 [main] io.openvidu.server.pro.utils.GeoLocationByIpPro - Trying to load user location database…
openvidu-server_1 | [INFO] 2020-05-11 11:12:12,387 [main] io.openvidu.server.pro.utils.GeoLocationByIpPro - Database was loaded successfully
openvidu-server_1 | [INFO] 2020-05-11 11:12:12,390 [main] io.openvidu.server.pro.OpenViduServerPro - OpenVidu Pro cluster mode enabled
openvidu-server_1 | [INFO] 2020-05-11 11:12:12,391 [main] io.openvidu.server.pro.OpenViduServerPro - Cluster identifier got from disk: clu_Qz7LAHa0
openvidu-server_1 | [INFO] 2020-05-11 11:12:12,395 [main] io.openvidu.server.pro.OpenViduServerPro - OpenVidu Pro is using ‘streams’ load strategy
openvidu-server_1 | [INFO] 2020-05-11 11:12:12,403 [main] io.openvidu.server.pro.OpenViduServerPro - OpenVidu Pro Elasticsearch service is enabled
openvidu-server_1 | [INFO] 2020-05-11 11:12:13,920 [main] io.openvidu.server.pro.cdr.CDRLoggerElasticSearch - Elasticsearch is accessible at 127.0.0.1:9200
openvidu-server_1 | [INFO] 2020-05-11 11:12:13,997 [main] io.openvidu.server.pro.cdr.CDRLoggerElasticSearch - Elasticsearch version is 7.6.2
openvidu-server_1 | [INFO] 2020-05-11 11:12:14,031 [main] io.openvidu.server.pro.cdr.CDRLoggerElasticSearch - Elasticsearch index “openvidu” already exists
openvidu-server_1 | [INFO] 2020-05-11 11:12:14,031 [main] io.openvidu.server.pro.OpenViduServerPro - OpenVidu Pro CDR service is disabled (may be enable with ‘OPENVIDU_CDR=true’)
openvidu-server_1 | [INFO] 2020-05-11 11:12:14,031 [main] io.openvidu.server.pro.OpenViduServerPro - OpenVidu Pro Webhook service is disabled (may be enabled with ‘OPENVIDU_WEBHOOK=true’)
openvidu-server_1 | [INFO] 2020-05-11 11:12:14,041 [main] io.openvidu.server.kurento.kms.KmsManager - OpenVidu Server Pro is deployed with ‘OPENVIDU_PRO_CLUSTER_MODE’ set to ‘manual’. Initializing Media Nodes defined in parameter ‘KMS_URIS’:
openvidu-server_1 | [INFO] 2020-05-11 11:12:14,047 [main] io.openvidu.server.kurento.kms.KmsManager - No KMS uris were defined
openvidu-server_1 | [INFO] 2020-05-11 11:12:14,071 [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] 2020-05-11 11:12:14,152 [main] io.openvidu.server.recording.service.RecordingManager - OpenVidu recording service is disabled
openvidu-server_1 | [INFO] 2020-05-11 11:12:14,245 [main] org.springframework.scheduling.concurrent.ThreadPoolTaskScheduler - Initializing ExecutorService ‘jsonrpcTaskScheduler’
openvidu-server_1 | [WARN] 2020-05-11 11:12:14,311 [main] io.openvidu.server.pro.config.KibanaConfig - Kibana is not accessible at Connect to 127.0.0.1:80 [/127.0.0.1] failed: Connection refused (Connection refused)
openvidu-server_1 | [ERROR] 2020-05-11 11:12:14,311 [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] 2020-05-11 11:12:14,311 [main] io.openvidu.server.pro.config.KibanaConfig - Terminating OpenVidu Server Pro
[root@vds openvidu]#

PS: I can not send all the log file here because discourse wont let me.

micael.gallego · May 11, 2020, 11:31am

Can you share the NGINX log please? If discourse don’t you allow it, please upload it to another place and provide us the link.

ertan · May 11, 2020, 11:34am

can you tell me the location of OPENVIDU NGINX log and Server Log file?

micael.gallego · May 11, 2020, 11:52am

You have to execute the following commands in /opt/openvidu folder:

$ docker-compose logs nginx
$ docker-compose logs openvidu-server

ertan · May 11, 2020, 12:10pm

@micael.gallego,

Thank you. Here are the logs:

NGINX Logs

gist.github.com

https://gist.github.com/ertanyildiz/ae7651ff8502b711646de23231f457c1

nginx.log

> Attaching to openvidu_nginx_1
> nginx_1            | Adding password for user kibanaadmin
> nginx_1            | 2020/05/11 10:09:10 [emerg] 13#13: bind() to 0.0.0.0:80 failed (98: Address already in use)
> nginx_1            | nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
> nginx_1            | 2020/05/11 10:09:10 [emerg] 13#13: bind() to 0.0.0.0:80 failed (98: Address already in use)
> nginx_1            | nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
> nginx_1            | 2020/05/11 10:09:10 [emerg] 13#13: bind() to 0.0.0.0:80 failed (98: Address already in use)
> nginx_1            | nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
> nginx_1            | 2020/05/11 10:09:10 [emerg] 13#13: bind() to 0.0.0.0:80 failed (98: Address already in use)
> nginx_1            | nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)

This file has been truncated. show original

Server Logs

gist.github.com

https://gist.github.com/ertanyildiz/b205fea0590ef657038c0c9f9e37ba8a

logs.txt

Attaching to openvidu_openvidu-server_1
[36mopenvidu-server_1  |[0m 
[36mopenvidu-server_1  |[0m ______________________________________________________________
[36mopenvidu-server_1  |[0m    ____               __      ___     _       
[36mopenvidu-server_1  |[0m   / __ \              \ \    / (_)   | |      
[36mopenvidu-server_1  |[0m  | |  | |_ __   ___ _ _\ \  / / _  __| |_   _     ___         
[36mopenvidu-server_1  |[0m  | |  | | '_ \ / _ \ '_ \ \/ / | |/ _` | | | |   | _ \_ _ ___ 
[36mopenvidu-server_1  |[0m  | |__| | |_) |  __/ | | \  /  | | (_| | |_| |   |  _/ '_/ _ \
[36mopenvidu-server_1  |[0m   \____/| .__/ \___|_| |_|\/   |_|\__,_|\__,_|   |_| |_| \___/
[36mopenvidu-server_1  |[0m         | |

This file has been truncated. show original

Oscar.Soto · May 11, 2020, 12:17pm

Hi @ertan,

The NGINX is not capable of using port 80, and it does not get a certificate using letsencrypt.

Please try the following:

1.- Turn off your local nginx with the command sudo systemctl stop nginx
2.- Delete the contents of the “certificates” folder with the command rm -rf /opt/openvidu/certificates/*
3.- Restart Openvidu, first go to the cd /opt/openvidu folder and then run ./openvidu restart

Greetings

ertan · May 11, 2020, 12:36pm

@Oscar.Soto,

Thank you for reply. I removed certificates folder. It now gives 404 error. Here are the updated logs:

NGINX Log

gist.github.com

https://gist.github.com/ertanyildiz/ae7651ff8502b711646de23231f457c1

nginx.log

> Attaching to openvidu_nginx_1
> nginx_1            | Adding password for user kibanaadmin
> nginx_1            | 2020/05/11 10:09:10 [emerg] 13#13: bind() to 0.0.0.0:80 failed (98: Address already in use)
> nginx_1            | nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
> nginx_1            | 2020/05/11 10:09:10 [emerg] 13#13: bind() to 0.0.0.0:80 failed (98: Address already in use)
> nginx_1            | nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
> nginx_1            | 2020/05/11 10:09:10 [emerg] 13#13: bind() to 0.0.0.0:80 failed (98: Address already in use)
> nginx_1            | nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
> nginx_1            | 2020/05/11 10:09:10 [emerg] 13#13: bind() to 0.0.0.0:80 failed (98: Address already in use)
> nginx_1            | nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)

This file has been truncated. show original

Server Log

gist.github.com

https://gist.github.com/ertanyildiz/b205fea0590ef657038c0c9f9e37ba8a

logs.txt

Attaching to openvidu_openvidu-server_1
[36mopenvidu-server_1  |[0m 
[36mopenvidu-server_1  |[0m ______________________________________________________________
[36mopenvidu-server_1  |[0m    ____               __      ___     _       
[36mopenvidu-server_1  |[0m   / __ \              \ \    / (_)   | |      
[36mopenvidu-server_1  |[0m  | |  | |_ __   ___ _ _\ \  / / _  __| |_   _     ___         
[36mopenvidu-server_1  |[0m  | |  | | '_ \ / _ \ '_ \ \/ / | |/ _` | | | |   | _ \_ _ ___ 
[36mopenvidu-server_1  |[0m  | |__| | |_) |  __/ | | \  /  | | (_| | |_| |   |  _/ '_/ _ \
[36mopenvidu-server_1  |[0m   \____/| .__/ \___|_| |_|\/   |_|\__,_|\__,_|   |_| |_| \___/
[36mopenvidu-server_1  |[0m         | |

This file has been truncated. show original

Oscar.Soto · May 11, 2020, 12:47pm

Hi @ertan,

The NGINX not working correctly because fails getting letsencrypt certificated. You need configure properly a email in the ‘LETSENCRYPT_EMAIL’ variable.

Nonetheless try deploy with “CERTIFICATE_TYPE=selfsigned” mode.

Regards

ertan · May 12, 2020, 7:57am

I’ve used my own certificate and problem solved.

S_la_Shuu · December 18, 2020, 10:44am

How can you fix it using your own certificate?

S_la_Shuu · January 4, 2021, 3:22am

hi @ertan
How can you fix it with your own certificate? Can you show me how to fix it.

Topic		Replies	Views
Kibana returned an unexpected response to GET http://127.0.0.1/kibana/api/status: 404 Issues with deployment v2	2	519	June 3, 2020
On Premises Pro Deployment Kibana Issues (openvidu-server_1 \| Waiting for kibana in 'http://127.0.0.1/kibana' 'URL'.) Issues with deployment v2	11	744	June 15, 2022
Connect() failed (111: Connection refused) while connecting to upstream Issues with deployment v2	2	3599	February 24, 2020
Inspector & Kibana not working Issues with deployment v2	12	1325	June 7, 2021
OpenViduPro : Waiting for kibana Issues with deployment v2	18	1509	April 13, 2021

Kibana is not accessible - Connection refused (Connection refused)

Related topics