Openvidu-call docker image not working

rahulnagpal · May 5, 2020, 12:33pm

Ok by when next version will be release?
And how many concurrent users can join meeting on 32GB RAM server in a single room and how many rooms can be created at a time?

micael.gallego · May 7, 2020, 1:31am

We plan to release at the end of this week or beginning of the next one.

The number of concurrent users depend on the number of CPUs, not memory.

rahulnagpal · May 12, 2020, 11:25am

By when the next version will be released?

micael.gallego · May 12, 2020, 11:43am

In a few hours. It is in process right now.

rahulnagpal · May 13, 2020, 4:36am

I have now use 2.14.0 latest version but still its not working on another port:

openvidu-server_1  |
openvidu-server_1  | ----------------------------------------------------
openvidu-server_1  |
openvidu-server_1  |    OpenVidu is ready!
openvidu-server_1  |    ---------------------------
openvidu-server_1  |
openvidu-server_1  |    * OpenVidu Server: https://www.fourmodules.com:4443/
openvidu-server_1  |
openvidu-server_1  |    * OpenVidu Dashboard: https://www.fourmodules.com:4443/dashboard/
openvidu-server_1  |
openvidu-server_1  | ----------------------------------------------------
openvidu-server_1  |
^CERROR: Aborting.
[root@server openvidu]# docker-compose logs nginx
Attaching to openvidu_nginx_1
nginx_1            | 2020/05/13 04:31:39 [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/13 04:31:39 [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/13 04:31:39 [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/13 04:31:39 [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/13 04:31:39 [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/13 04:31:39 [emerg] 13#13: still could not bind()
nginx_1            | nginx: [emerg] still could not bind()
nginx_1            | Domain name: www.fourmodules.com:4443
nginx_1            | Certificated: owncert
nginx_1            | Letsencrypt Email: rahul.nagpal@exoways.com
nginx_1            | Proxy mode: CE
nginx_1            | Demos mode: true
nginx_1            | ===Mode owncert===
nginx_1            | Using owmcert...
nginx_1            | 2020/05/13 04:31:41 [warn] 34#34: "ssl_stapling" ignored, issuer certificate not found for certificate "/etc/letsencrypt/live/www.fourmodules.com:4443/fullchain.pem"
nginx_1            | nginx: [warn] "ssl_stapling" ignored, issuer certificate not found for certificate "/etc/letsencrypt/live/www.fourmodules.com:4443/fullchain.pem"
nginx_1            | 2020/05/13 04:31:41 [warn] 37#37: "ssl_stapling" ignored, issuer certificate not found for certificate "/etc/letsencrypt/live/www.fourmodules.com:4443/fullchain.pem"
nginx_1            | nginx: [warn] "ssl_stapling" ignored, issuer certificate not found for certificate "/etc/letsencrypt/live/www.fourmodules.com:4443/fullchain.pem"
nginx_1            | 2020/05/13 04:31:41 [emerg] 37#37: bind() to 0.0.0.0:443 failed (98: Address already in use)
nginx_1            | nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)
nginx_1            | 2020/05/13 04:31:41 [emerg] 37#37: 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/13 04:31:41 [emerg] 37#37: bind() to 0.0.0.0:443 failed (98: Address already in use)
nginx_1            | nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)
nginx_1            | 2020/05/13 04:31:41 [emerg] 37#37: 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/13 04:31:41 [emerg] 37#37: bind() to 0.0.0.0:443 failed (98: Address already in use)
nginx_1            | nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)
nginx_1            | 2020/05/13 04:31:41 [emerg] 37#37: 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/13 04:31:41 [emerg] 37#37: bind() to 0.0.0.0:443 failed (98: Address already in use)
nginx_1            | nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)
nginx_1            | 2020/05/13 04:31:41 [emerg] 37#37: 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/13 04:31:41 [emerg] 37#37: bind() to 0.0.0.0:443 failed (98: Address already in use)
nginx_1            | nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)
nginx_1            | 2020/05/13 04:31:41 [emerg] 37#37: 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/13 04:31:41 [emerg] 37#37: still could not bind()
nginx_1            | nginx: [emerg] still could not bind()
nginx_1            | Restarting nginx: nginx failed!
[root@server openvidu]#

Oscar.Soto · May 13, 2020, 6:01am

Hi @rahulnagpal,

How did you perform the upgrade process? Because the NGINX is not correctly updated. You can show me the docker-compose.yml file

Regards

rahulnagpal · May 13, 2020, 6:13am

I have now perform upgrade process also, it is now showing this error:

[root@server openvidu]# cat docker-compose.yml
# ------------------------------------------------------------------------------
#
#    DO NOT MODIFY THIS FILE !!!
#
#    Configuration properties should be specified in .env file
#
#    Application based on OpenVidu should be specified in
#    docker-compose.override.yml file
#
#    This docker-compose file coordinates all services of OpenVidu CE Platform.
#
#    This file will be overridden when update OpenVidu Platform
#
#    Openvidu Version: 2.14.0
#
# ------------------------------------------------------------------------------

version: '3.1'

services:

    openvidu-server:
        image: openvidu/openvidu-server:2.14.0
        restart: on-failure
        network_mode: host
        entrypoint: ['/bin/bash', '-c', 'export COTURN_IP=`/usr/local/bin/discover_my_public_ip.sh`; /usr/local/bin/entrypoint.sh']
        volumes:
            - /var/run/docker.sock:/var/run/docker.sock
            - ${OPENVIDU_RECORDING_PATH}:${OPENVIDU_RECORDING_PATH}
            - ${OPENVIDU_RECORDING_CUSTOM_LAYOUT}:${OPENVIDU_RECORDING_CUSTOM_LAYOUT}
            - ${OPENVIDU_CDR_PATH}:${OPENVIDU_CDR_PATH}
        env_file:
            - .env
        environment:
            - SERVER_SSL_ENABLED=false
            - SERVER_PORT=5443
            - KMS_URIS=["ws://localhost:8888/kurento"]
            - COTURN_REDIS_IP=127.0.0.1

    kms:
        image: ${KMS_IMAGE:-kurento/kurento-media-server:6.13.2}
        restart: always
        network_mode: host
        ulimits:
          core: -1
        volumes:
            - /opt/openvidu/kms-crashes:/opt/openvidu/kms-crashes
            - ${OPENVIDU_RECORDING_PATH}:${OPENVIDU_RECORDING_PATH}
        environment:
            - KMS_MIN_PORT=40000
            - KMS_MAX_PORT=57000
            - GST_DEBUG=${KMS_DEBUG_LEVEL:-}

    redis:
        image: redis:5.0.7
        restart: always
        network_mode: host

    coturn:
        image: openvidu/openvidu-coturn:1.0.0
        restart: on-failure
        network_mode: host
        environment:
            - REDIS_IP=127.0.0.1
            - TURN_LISTEN_PORT=3478
            - DB_NAME=0
            - DB_PASSWORD=turn
            - MIN_PORT=57001
            - MAX_PORT=65535

    nginx:
        image: openvidu/openvidu-proxy:2.0.0
        restart: on-failure
        network_mode: host
        volumes:
            - ./certificates:/etc/letsencrypt
            - ./owncert:/owncert
            - ${OPENVIDU_RECORDING_CUSTOM_LAYOUT}:/opt/openvidu/custom-layout
        environment:
            - DOMAIN_OR_PUBLIC_IP=${DOMAIN_OR_PUBLIC_IP}
            - CERTIFICATE_TYPE=${CERTIFICATE_TYPE}
            - LETSENCRYPT_EMAIL=${LETSENCRYPT_EMAIL}
            - PROXY_HTTP_PORT=${HTTP_PORT:-}
            - PROXY_HTTPS_PORT=${HTTPS_PORT:-}
            - ALLOWED_ACCESS_TO_DASHBOARD=${ALLOWED_ACCESS_TO_DASHBOARD:-}
            - ALLOWED_ACCESS_TO_RESTAPI=${ALLOWED_ACCESS_TO_RESTAPI:-}
            - PROXY_MODE=CE
            - WITH_APP=true
[root@server openvidu]#

openvidu-server_1  |
openvidu-server_1  |
openvidu-server_1  |    Configuration errors
openvidu-server_1  |    --------------------
openvidu-server_1  |
openvidu-server_1  |    * Property OPENVIDU_DOMAIN_OR_PUBLIC_IP=https://www.fourmodules.com:4443. Is not a valid Internet Address (IP or Domain Name): https://www.fourmodules.com:4443: Name or service not known
openvidu-server_1  |
openvidu-server_1  |
openvidu-server_1  |    Fix config errors
openvidu-server_1  |    ---------------
openvidu-server_1  |
openvidu-server_1  |    1) Return to shell pressing Ctrl+C
openvidu-server_1  |    2) Set correct values in '.env' configuration file
openvidu-server_1  |    3) Restart OpenVidu with:
openvidu-server_1  |
openvidu-server_1  |       $ ./openvidu restart
openvidu-server_1  |
openvidu-server_1  |

Oscar.Soto · May 13, 2020, 7:55am

Hi @rahulnagpal,

First please remove the old .env and rename .env-2.14.0 to .env.

After then edit the variable DOMAIN_OR_PUBLIC_IP using a valid path, as explained in the .env file. In your case it would be like this DOMAIN_OR_PUBLIC_IP=fourmodules.com.

Add a Openvidu Secret in the variable OPENVIDU_SECRET.

To change the ports you must set the following variables:

HTTP_PORT: Uncomment this variable and use a port other than 80, since you’re using it. for example 8080. HTTP_PORT=8080
HTTPS_PORT: Uncomment this variable and use 4443 port. HTTPS_PORT=4443

Regards

rahulnagpal · May 13, 2020, 8:36am

Thanks openvidu server started now.
I just want to know that is it possible to integrate SIP protocol also with this for enabling voice call from mobile phones?

micael.gallego · May 13, 2020, 8:50am

SIP integration is in our roadmap, but it is not yet available.

rahulnagpal · May 13, 2020, 9:06am

When I am accessing on browser: https://www.fourmodules.com:5000
It is showing this error randomly:

'publisher1' has logged in
Getting a token | {sessionName}={Demo}
Existing session Demo
Error: 404
    at /home/fourmodules/public_html/webrtc/openvidu-tutorials/openvidu-js-node/node_modules/openvidu-node-client/lib/Session.js:107:28
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

micael.gallego · May 13, 2020, 9:26am

It seems you are not using OpenVidu-Call. Can you open a new entry for this issue to better management?

Also, please can you share OpenVidu logs with command:

$ cd /opt/openvidu
$ docker-compose logs openvidu-server

rahulnagpal · May 13, 2020, 10:39am

I have created a new thread for that: OpenVidu-Call not working properly

yy_oo · July 9, 2020, 7:52pm

Hi,
I have one interface with multiple ip addresses, can I bind openvidu or nginx with only one ip address? because I use another ip address for a different application. either openvidu or another application uses the same port 80 and 443 but different ip addresses

Regards

micael.gallego · July 10, 2020, 7:49am

This is not supported out of the box.

You will have to tweak proxy container (responsible to use 443 and 80 ports) to bind to only one IP.

Regards

nishmohan · July 16, 2020, 2:06pm

Hello,
https://docs.openvidu.io/en/2.15.0/deployment/deploying-on-premises/
I installed all things on AWS server and working fine but it’s pointing openVidu server.
Now please tell me i can do following things and how:

Customized screens
Live Stream / Meeting
Share Screen
Record
Can i change logo and name?
Please help for this if you not able help then please let me know i’ll search another provider?

Thanks

CSantosM · July 16, 2020, 2:24pm

@nishmohan,

Could you please stop posting the same message everywhere? It’s really annoying for the forum and the community.

micael.gallego · July 16, 2020, 2:25pm

Please @nishmohan, stop repeating the same question in different entries.

We have helped you providing instructions on how to do the things. But you have to do yourself or use our commercial services if you want us to work for you.

nishmohan · July 16, 2020, 3:36pm

@micael.gallego and @CSantosM without reply my questions you are asking for stop posting to forum?
What should i do if i did not get help?
As you provided the Tutorial and demo not sufficient to configure openVidu on AWS.
There is many confusion.

Thanks

micael.gallego · July 16, 2020, 4:00pm

If you have any doubt, you can write your question ONLY ONE TIME. I’ve answered you many times in the forum.

We have tried to help you compiling the Angular application and deploying it in OpenVidu platform. But you are still having problems. As we are a small team and we don’t have infinity resources, we can not help you more…

If you need priority support, you can use our commercial services.

Topic		Replies	Views
OpenVidu-call as a separate deployment - confusion Issues developing apps	5	737	August 11, 2020
Issue with certificate Issues developing apps	9	404	October 20, 2020
Connection Problem--Oops trying to Issues developing apps	7	206	April 19, 2022
Our Web content under Docker does not connect with Openvidu Server Issues with deployment	17	707	August 5, 2020
Deploy recording using docker Issues with deployment	11	525	January 13, 2021

Openvidu-call docker image not working

Related Topics