Enhance your
Live Video Chat

You need a web server with a) installed Node.js with at least 10th version; or b) Root access and SSL certificates. After that follow the install instructions from here.

You can set it in any Linux or Windows server, though you need:
– SSL enabled;
– Web server (Apache or Nginx);
– Root access;
– Access to the certificates and keys;
– Eventually Node.js with at least 12th version;
– PHP and MySQL are not mandatory, but if you want to manage your agents/users/rooms and chat history, they are a must;
– Please note that most probably shared hosting will not fit your need. Use VPS or dedicated hosting.

LiveSmart is based on WebRTC technology with Mesh topology. This means that the connections and bandwidth traffic are mainly handled by client side. The traffic on the server is not high, as the connections are peer-to-peer.

– For 1:1 video sessions, theoretically the number of concurrent sessions can be unlimited. I have tested with 50 1:1 video sessions on the demo server. It is scalable, so it can maintain much more.

– For multi user video session, the number of participants in each session is limited by client-side bandwidth, device, and CPU limitations for processing vast amounts of video and audio streams. Five participants, rarely on good connections and low resolution camera to eight in a single video conference is a reasonable number. (#1 for rooms at once is valid here)

– For the broadcasting session where there is one or two broadcaster and many viewers that are subscribing to their video and audio stream. I have clients that are using the broadcasting feature for online lessons for 60+ viewers, but this number is also scalable and for sure it can maintain more attendees.

1. Check config/config.json is a valid JSON file here https://jsonlint.com/

2. Make sure you have installed and setup correctly signaling server:
 – ws/server – did you do here npm install
 – ws/server/config.json – did you set correct certificate and key path?
   “sslKey”: “../ssl/key.pem”,
   “sslCert”: “../ssl/cert.pem”,
 – make sure port 9001 is opened in your firewall
 – in config/config.json
   “appWss”: “https://YOUR_DOMAIN:9001/”, should be your domain name;
 – make sure you use HTTPS everywhere;
 – make sure you are running the signaling server with pm2:
 (you can install it with npm install pm2 -g)
 in ws/server do pm2 start server.js

3. In sample agent.html page
<script src="YOUR_DOMAIN/js/loader.v2.js" data-source_path="YOUR_DOMAIN/" ></script>
must be of the type
<script src="https://domain.com/js/loader.v2.js" data-source_path="https://domain.com/" ></script>

net::ERR_SSL_VERSION_OR_CIPHER_MISMATCH, net::ERR_CERT_AUTHORITY_INVALID or net::ERR_SSL_PROTOCOL_ERROR

These errors are because the certificate and key paths that you set in ws/server/config.json file are not correct, not matching, or self-singed. Please double check to use the correct certificate. Usual location for them are:

/etc/ssl/private/ and /etc/ssl/certs/;
/home/YOURACCOUT/ssl/certs and /home/YOURACCOUT/ssl/keys for WHM/Cpanel users;
/etc/letsencrypt/live/YOURDOMAIN/fullchain.pem and key: /etc/letsencrypt/live/YOURDOMAIN/privkey.pem for Letsencrypt;
/usr/local/psa/var/modules/letsencrypt/etc/live/YOURDOMAIN/chain.pem and /usr/local/psa/var/modules/letsencrypt/etc/live/YOURDOMAIN/privkey.pem for Plesk users.

net::ERR_CONNECTION_TIMED_OUT or net::ERR_CONNECTION_REFUSED

Most probably you have installed everything correctly, but a firewall is blocking your port. So please check your firewall/iptables, so you can open them for 9001.

PermissionDeniedError

The errors are most common if your browser has no access to web camera or microphone
– Make sure you are using SSL;
– Make sure you have granted permissions to microphone and camera;
– If you are using Firefox or Safari, make sure there is no other app that is accessing your camera or microphone;

I got stuck on Waiting screen, or my camera feed is black

Most probably your camera is stuck by another video streaming software, antivirus program, not accepting permissions or something else. To make sure your camera is working, please open this google test page and click on Start button. If your video feed is not shown, check your camera. More for Chrome browser about camera not working can be found here.
If you see your local feed, please contact me to resolve this issue.

1. If you are on Apache webserver, make sure the demo.htaccess file is .htaccess. If you already have .htaccess from your current site, you need to merge the content of demo.htaccess in the existing .htaccess.

Make sure the mod rewrite module of the apache is enabled and check the the Apache configuration file where is <Directory "/var/www/YOURDOMAIN"> to have AllowOverride All
to be something like:

            <Directory "/var/www/...">
                Options FollowSymLinks
                AllowOverride All

                Order allow,deny
                Allow from all
            </Directory>

Check this article for more information.

2. If you are on Nginx web server, open Nginx config file and make sure to merge this into it (if LiveSmart is in your /live folder.)

        location /live/ {
            rewrite ^/live/(\w+)$ /live/routes.php?short=$1 last;
        }

Make sure the backend is properly installed and that the port for signaling server is the same as in the /config/config.json file. Check the code snippet that you added to the site has data-source_path correctly added and that <div id="nd-widget-container" class="nd-widget-container"></div> is present in your HTML.

You can email me with demand for unminified version of the JavaScript folder. But have in mind that if you change the code, this may affect your future release. Another option to do modifications and customizations is to add your own JavaScipt functions in the blank JavaScript file additional.js in /js folder. You can overwrite existing functions, write your own event handlers, or manage the UI elements. If you plan to change the HTML part, you can change pages/w.html. Style modifications of video popup are in css/roomconference.css file.

Please check the contact options from here and send description of the issue, together with a detailed info about the system you are using: backend, browser, OS.