If you start openvidu while there is no internet, it fails to start and an error appears.
In the system configuration, a PC is connected to the router through an internal network.
The error is:
dig: couldn’t get address for ‘resolver1.opendns.com’: failure
dig: couldn’t get address for ‘ns1.google.com’: failure
dig: couldn’t get address for ‘ns1-1.akamaitech.net’: failure
[/usr/local/bin/discover_my_public_ip.sh] Discovery failed
What’s the problem?
The same error occurs even if I try to set the DOMAIN_OR_PUBLIC_IP item value in the .env file to 188.8.131.52 and to set the internal IP to 192.168.2.10.
One doubt, as of now after deploying openvidu as on-premise solution when i start the service it tries to access - COTURN IP: 184.108.40.206 which i think is public ip.
If we dont have internet access then what ip we need to set for COTURN.
Also do we need to install COTURN SERVER on our local machine.
Yes, we have subnet network only.
IP of openvidu server is - 192.168.148.186
I have made following changes in .env file:
But in logs it is coming as “io.openvidu.server.coturn.CoturnCredentialsService - COTURN IP: 220.127.116.11”
How to configure COTURN_IP and in which file changes need to be made?
Could you please help in this?
If you just want to use it inside your private network, a COTURN server should not be necessary. You would need if users behind different NATs or firewalls want to connect to each other. If I turn off our COTURN server and then start a session in our private network - all participants can hear and see each other.
Because of this I asked you what do you mean with “not working”. Are you only missing audio and video or does the complete connection fail?
We are setting up the environment in our private network but video conference can be done with client who is not in our network. After setting COTURN_IP=192.168.148.186, openvidu is trying to access COTURN on IP - 18.104.22.168
[INFO] 2022-08-22 11:26:44,915 [main] io.openvidu.server.coturn.CoturnCredentialsService - COTURN IP: 22.214.171.124.
Please help to resolve it.
OK - your OpenVidu server is part of your private network - but the server has no public IP? It only has access to the internet over a proxy or gateway?
In this case it is normal, that external clients can not participate. An external client can’t do anything with your private it. It needs an public IP where to coturn is located or were the coturn ports (mostly 3478 TCP/UDP) are redirected to your local IP.
Hello, I have the same problem
When I want to reset ./openvidu reset and I don’t have internet, this error appears
i add `COTURN_IP no error but when i go to https://192.168.1.106/dashboard
i got this from browser
Unable to connect
An error occurred during a connection to 192.168.1.106.
The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer’s network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.
# OpenVidu configuration
# Documentation: https://docs.openvidu.io/en/stable/reference-docs/openvidu-config/
# NOTE: This file doesn't need to quote assignment values, like most shells do.
# All values are stored as-is, even if they contain spaces, so don't quote them.
# Domain name. If you do not have one, the public IP of the machine.
# For example: 198.51.100.1, or openvidu.example.com
# OpenVidu SECRET used for apps to connect to OpenVidu server and users to access to OpenVidu Dashboard
# Certificate type:
# - selfsigned: Self signed certificate. Not recommended for production use.
# Users will see an ERROR when connected to web page.
# - owncert: Valid certificate purchased in a Internet services company.
# Please put the certificates files inside folder ./owncert
# with names certificate.key and certificate.cert
# - letsencrypt: Generate a new certificate using letsencrypt. Please set the
# required contact email for Let's Encrypt in LETSENCRYPT_EMAIL
# If CERTIFICATE_TYPE=letsencrypt, you need to configure a valid email for notifications
# Proxy configuration
# If you want to change the ports on which openvidu listens, uncomment the following lines
# Allows any request to http://DOMAIN_OR_PUBLIC_IP:HTTP_PORT/ to be automatically
# redirected to https://DOMAIN_OR_PUBLIC_IP:HTTPS_PORT/.
# WARNING: the default port 80 cannot be changed during the first boot
# if you have chosen to deploy with the option CERTIFICATE_TYPE=letsencrypt
# Changes the port of all services exposed by OpenVidu.
# SDKs, REST clients and browsers will have to connect to this port
You should at least be connected in the same LAN as OpenVidu . No internet connection does not mean that you are not connected to at least, a router or a switch which let both machines to be in the same network.