After I type make, how can i attach it to the domain of my server?

[BlakeEram]

vmadmin@cmi:~/m-health$ make
./node_modules/.bin/webpack -p
Hash: fd6378a2ad87ed0113fcd8da8b89472361525b72
Version: webpack 3.9.1
Child
    Hash: fd6378a2ad87ed0113fc
    Time: 189447ms
                                           Asset       Size  Chunks                    Chunk Names
              dial_in_info_bundle.min.js.LICENSE       1 kB          [emitted]         
                               app.bundle.min.js    2.87 MB       0  [emitted]  [big]  app.bundle
                      dial_in_info_bundle.min.js     605 kB       2  [emitted]  [big]  dial_in_info_bundle
                              alwaysontop.min.js     112 kB       3  [emitted]         alwaysontop
                      do_external_connect.min.js    1.99 kB       4  [emitted]         do_external_connect
                       app.bundle.min.js.LICENSE    7.11 kB          [emitted]         
    device_selection_popup_bundle.min.js.LICENSE    6.95 kB          [emitted]         
            device_selection_popup_bundle.min.js     2.4 MB       1  [emitted]  [big]  device_selection_popup_bundle
                      alwaysontop.min.js.LICENSE  529 bytes          [emitted]         
                              app.bundle.min.map    14.1 MB       0  [emitted]         app.bundle
           device_selection_popup_bundle.min.map    11.9 MB       1  [emitted]         device_selection_popup_bundle
                     dial_in_info_bundle.min.map    3.14 MB       2  [emitted]         dial_in_info_bundle
                             alwaysontop.min.map     395 kB       3  [emitted]         alwaysontop
                     do_external_connect.min.map    12.6 kB       4  [emitted]         do_external_connect
      [34] ./node_modules/@atlaskit/theme/dist/esm/index.js + 7 modules 13.2 kB {0} {1} [built]
      [51] (webpack)/buildin/global.js 509 bytes {0} {1} {2} [built]
     [141] ./react/features/base/config/parseURLParams.js 1.51 kB {0} {1} {2} {4} [built]
     [311] ./react/features/base/config/getRoomName.js 761 bytes {0} {1} {2} {4} [built]
     [397] ./react/features/base/react/prop-types-polyfill.js 227 bytes {0} {1} {2} [built]
     [939] multi babel-polyfill whatwg-fetch ./app.js 52 bytes {0} [built]
     [940] ./app.js + 2 modules 4.7 kB {0} [built]
     [962] ./modules/UI/UI.js 35.2 kB {0} [built]
     [977] ./react/index.web.js 1.06 kB {0} [built]
     [978] ./react/features/device-selection/popup.js 476 bytes {1} [built]
     [979] ./react/features/device-selection/DeviceSelectionPopup.js 12.3 kB {1} [built]
     [980] ./react/features/always-on-top/index.js + 3 modules 26.7 kB {3} [built]
     [981] multi babel-polyfill whatwg-fetch ./react/features/base/react/prop-types-polyfill.js ./react/features/invite/components/dial-in-info-page 64 bytes {2} [built]
     [982] ./react/features/invite/components/dial-in-info-page/index.js + 2 modules 4.02 kB {2} [built]
     [983] ./connection_optimization/do_external_connect.js 2.51 kB {4} [built]
        + 969 hidden modules
Child
    Hash: d8da8b89472361525b72
    Time: 21360ms
                   Asset    Size  Chunks             Chunk Names
     external_api.min.js  115 kB       0  [emitted]  external_api
    external_api.min.map  568 kB       0  [emitted]  external_api
      [90] (webpack)/buildin/global.js 509 bytes {0} [built]
     [125] ./react/features/base/util/uri.js 14.1 kB {0} [built]
     [128] multi babel-polyfill ./modules/API/external/index.js 40 bytes {0} [built]
     [331] ./modules/API/external/index.js 171 bytes {0} [built]
     [332] ./modules/API/external/external_api.js 30.9 kB {0} [built]
     [334] ./modules/transport/index.js + 9 modules 24.5 kB {0} [built]
     [335] ./react/features/base/util/httpUtils.js 758 bytes {0} [built]
        + 331 hidden modules
mkdir -p libs
cp \
    build/app.bundle.min.js \
    build/app.bundle.min.map \
    build/do_external_connect.min.js \
    build/do_external_connect.min.map \
    build/external_api.min.js \
    build/external_api.min.map \
    build/device_selection_popup_bundle.min.js \
    build/device_selection_popup_bundle.min.map \
    build/dial_in_info_bundle.min.js \
    build/dial_in_info_bundle.min.map \
    build/alwaysontop.min.js \
    build/alwaysontop.min.map \
    ./analytics-ga.js \
    libs
cp \
    node_modules/lib-jitsi-meet//lib-jitsi-meet.min.js \
    node_modules/lib-jitsi-meet//lib-jitsi-meet.min.map \
    node_modules/lib-jitsi-meet//connection_optimization/external_connect.js \
    node_modules/lib-jitsi-meet//modules/browser/capabilities.json \
    libs
./node_modules/.bin/node-sass css/main.scss css/all.bundle.css && \
./node_modules/.bin/cleancss css/all.bundle.css > css/all.css ; \
rm css/all.bundle.css
Rendering Complete, saving .css file...
Wrote CSS to /home/vmadmin/m-health/css/all.bundle.css
([ ! -x deploy-local.sh ] || ./deploy-local.sh)
rm -fr build

[damencho]

Did you deploy all the components jicofo, videobridge ... ?

[BlakeEram]

I have now installed all 3 other components, where would I go from here? thanks

[damencho]

It is, just I'm missing context in your question. So you have a regular deployment and you want to deploy a changed jitsi-meet version? If this is the case than you just change the folder from where you serve jitsi-meet. For nginx you need to change root to the folder you have jitsi-meet. If it is jetty you need to edit this property: org.jitsi.videobridge.rest.jetty.ResourceHandler.resourceBase=/usr/share/jitsi-meet

[BlakeEram]

Deploy a changed version of jitsi-meet. Is nginx and jetty another installtion for Jitsi-meet?

[damencho]

Did you already follow this https://github.com/jitsi/jitsi-meet/blob/master/doc/quick-install.md and did the install?

[BlakeEram]

I have followed but maybe this is the issue, when I type this command, apt-get -y install jitsi-meet with only my version of jistsi-meet cloned from github, will it install mine?

Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following additional packages will be installed:
  jitsi-meet-prosody jitsi-meet-web jitsi-meet-web-config lua-event lua-expat
  lua-filesystem lua-sec lua-socket lua5.1 prosody
Suggested packages:
  lua-zlib lua-dbi-postgresql lua-dbi-mysql lua-dbi-sqlite3
The following NEW packages will be installed:
  jitsi-meet jitsi-meet-prosody jitsi-meet-web jitsi-meet-web-config lua-event lua-expat
  lua-filesystem lua-sec lua-socket lua5.1 prosody
0 upgraded, 11 newly installed, 0 to remove and 88 not upgraded.
Need to get 8,366 kB of archives.
After this operation, 59.9 MB of additional disk space will be used.
Get:1 http://ca.archive.ubuntu.com/ubuntu xenial/universe amd64 lua5.1 amd64 5.1.5-8ubuntu1 [90.8 kB]
Get:2 http://ca.archive.ubuntu.com/ubuntu xenial/universe amd64 lua-expat amd64 1.3.0-3 [11.9 kB]
Get:3 http://ca.archive.ubuntu.com/ubuntu xenial/universe amd64 lua-socket amd64 3.0~rc1+git+321c0c9-1 [63.1 kB]
Get:4 http://ca.archive.ubuntu.com/ubuntu xenial/universe amd64 lua-sec amd64 0.5.1-1 [22.4 kB]
Get:5 http://ca.archive.ubuntu.com/ubuntu xenial/main amd64 lua-filesystem amd64 1.6.3-1 [9,930 B]
Get:6 http://ca.archive.ubuntu.com/ubuntu xenial/universe amd64 prosody amd64 0.9.10-1 [203 kB]
Get:7 https://download.jitsi.org stable/ jitsi-meet-web 1.0.2740-1 [7,932 kB]
Get:8 http://ca.archive.ubuntu.com/ubuntu xenial/universe amd64 lua-event amd64 0.4.3-2 [12.0 kB]
Get:9 https://download.jitsi.org stable/ jitsi-meet-web-config 1.0.2740-1 [11.7 kB]
Get:10 https://download.jitsi.org stable/ jitsi-meet-prosody 1.0.2740-1 [5,560 B]
Get:11 https://download.jitsi.org stable/ jitsi-meet 1.0.2988-1 [2,718 B]
Fetched 8,366 kB in 2s (4,129 kB/s)     
Preconfiguring packages ...
Selecting previously unselected package jitsi-meet-web.
(Reading database ... 168811 files and directories currently installed.)
Preparing to unpack .../jitsi-meet-web_1.0.2740-1_all.deb ...
Unpacking jitsi-meet-web (1.0.2740-1) ...
Selecting previously unselected package jitsi-meet-web-config.
Preparing to unpack .../jitsi-meet-web-config_1.0.2740-1_all.deb ...
Unpacking jitsi-meet-web-config (1.0.2740-1) ...
Selecting previously unselected package lua5.1.
Preparing to unpack .../lua5.1_5.1.5-8ubuntu1_amd64.deb ...
Unpacking lua5.1 (5.1.5-8ubuntu1) ...
Selecting previously unselected package lua-expat:amd64.
Preparing to unpack .../lua-expat_1.3.0-3_amd64.deb ...
Unpacking lua-expat:amd64 (1.3.0-3) ...
Selecting previously unselected package lua-socket:amd64.
Preparing to unpack .../lua-socket_3.0~rc1+git+321c0c9-1_amd64.deb ...
Unpacking lua-socket:amd64 (3.0~rc1+git+321c0c9-1) ...
Selecting previously unselected package lua-sec:amd64.
Preparing to unpack .../lua-sec_0.5.1-1_amd64.deb ...
Unpacking lua-sec:amd64 (0.5.1-1) ...
Selecting previously unselected package lua-filesystem:amd64.
Preparing to unpack .../lua-filesystem_1.6.3-1_amd64.deb ...
Unpacking lua-filesystem:amd64 (1.6.3-1) ...
Selecting previously unselected package prosody.
Preparing to unpack .../prosody_0.9.10-1_amd64.deb ...
Unpacking prosody (0.9.10-1) ...
Selecting previously unselected package jitsi-meet-prosody.
Preparing to unpack .../jitsi-meet-prosody_1.0.2740-1_all.deb ...
Unpacking jitsi-meet-prosody (1.0.2740-1) ...
Selecting previously unselected package jitsi-meet.
Preparing to unpack .../jitsi-meet_1.0.2988-1_all.deb ...
Unpacking jitsi-meet (1.0.2988-1) ...
Selecting previously unselected package lua-event:amd64.
Preparing to unpack .../lua-event_0.4.3-2_amd64.deb ...
Unpacking lua-event:amd64 (0.4.3-2) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for libc-bin (2.23-0ubuntu10) ...
Processing triggers for systemd (229-4ubuntu21.1) ...
Processing triggers for ureadahead (0.100.0-19) ...
Setting up jitsi-meet-web (1.0.2740-1) ...
Setting up jitsi-meet-web-config (1.0.2740-1) ...
----------------

You can now switch to a Let’s Encrypt certificate. To do so, execute:
/usr/share/jitsi-meet/scripts/install-letsencrypt-cert.sh

----------------
Setting up lua5.1 (5.1.5-8ubuntu1) ...
update-alternatives: using /usr/bin/lua5.1 to provide /usr/bin/lua (lua-interpreter) in auto mode
update-alternatives: using /usr/bin/luac5.1 to provide /usr/bin/luac (lua-compiler) in auto mode
Setting up lua-expat:amd64 (1.3.0-3) ...
Setting up lua-socket:amd64 (3.0~rc1+git+321c0c9-1) ...
Setting up lua-sec:amd64 (0.5.1-1) ...
Setting up lua-filesystem:amd64 (1.6.3-1) ...
Setting up prosody (0.9.10-1) ...
Setting up jitsi-meet-prosody (1.0.2740-1) ...
Setting up jitsi-meet (1.0.2988-1) ...
Setting up lua-event:amd64 (0.4.3-2) ...
Processing triggers for libc-bin (2.23-0ubuntu10) ...

[BlakeEram]

I am also using apache2 for my server

[BlakeEram]

it installed on my ip but if you go to http://142.55.32.25/ nothing shows,

`sudo /usr/share/jitsi-meet/scripts/install-letsencrypt-cert.sh
-------------------------------------------------------------------------
This script will:
- Need a working DNS record pointing to this machine(for domain cmi.fast.sheridanc.on.ca)
- Download certbot-auto from https://dl.eff.org to /usr/local/sbin
- Install additional dependencies in order to request Let’s Encrypt certificate
- If running with jetty serving web content, will stop Jitsi Videobridge
- Configure and reload nginx or apache2, whichever is used

You need to agree to the ACME server's Subscriber Agreement (https://letsencrypt.org/documents/LE-SA-v1.1.1-August-1-2016.pdf) 
by providing an email address for important account notifications
Enter your email and press [ENTER]: blakeeram@gmail.com
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator standalone, Installer None
Cert is due for renewal, auto-renewing...
Renewing an existing certificate
Performing the following challenges:
tls-sni-01 challenge for cmi.fast.sheridanc.on.ca
Waiting for verification...
Cleaning up challenges

IMPORTANT NOTES:
 - Congratulations! Your certificate and chain have been saved at:
   /etc/letsencrypt/live/cmi.fast.sheridanc.on.ca/fullchain.pem
   Your key file has been saved at:
   /etc/letsencrypt/live/cmi.fast.sheridanc.on.ca/privkey.pem
   Your cert will expire on 2018-09-02. To obtain a new or tweaked
   version of this certificate in the future, simply run certbot-auto
   again. To non-interactively renew *all* of your certificates, run
   "certbot-auto renew"
 - If you like Certbot, please consider supporting our work by:

   Donating to ISRG / Let's Encrypt:   https://letsencrypt.org/donate
   Donating to EFF:                    https://eff.org/donate-le

Configuring jetty
Importing keystore /etc/jitsi/videobridge/cmi.fast.sheridanc.on.ca.p12 to /etc/jitsi/videobridge/cmi.fast.sheridanc.on.ca.jks...
Entry for alias 1 successfully imported.
Import command completed:  1 entries successfully imported, 0 entries failed or cancelled

Warning:
The JKS keystore uses a proprietary format. It is recommended to migrate to PKCS12 which is an industry standard format using "keytool -importkeystore -srckeystore /etc/jitsi/videobridge/cmi.fast.sheridanc.on.ca.jks -destkeystore /etc/jitsi/videobridge/cmi.fast.sheridanc.on.ca.jks -deststoretype pkcs12".
vmadmin@cmi:~$ nano /etc/jitsi/videobridge/sip-communicator.properties
vmadmin@cmi:~$ cat /etc/jitsi/videobridge/sip-communicator.properties
cat: /etc/jitsi/videobridge/sip-communicator.properties: Permission denied
vmadmin@cmi:~$ sudo cat /etc/jitsi/videobridge/sip-communicator.properties
org.jitsi.videobridge.AUTHORIZED_SOURCE_REGEXP=focus@auth.cmi.fast.sheridanc.on.ca/.*
org.ice4j.ice.harvest.NAT_HARVESTER_LOCAL_ADDRESS=142.55.32.25
org.ice4j.ice.harvest.NAT_HARVESTER_PUBLIC_ADDRESS=142.55.32.25`

Thanks very much for you help

[damencho]

This will install latest jitsi-meet from the repo. Than got ot your jitsi-meet apache config and change these lines: https://github.com/jitsi/jitsi-meet/blob/master/doc/debian/jitsi-meet/jitsi-meet.example-apache#L23

DocumentRoot "/opt/jitsi-meet"
<Directory "/opt/jitsi-meet">

Make sure you put your jitsi-meet clone in a folder where apache user can read it. The restart apache and it should take your changed version.

[damencho]

It needs to be https. And check your apache config and logs is jitsi-meet config taken into account.

[damencho]

vmadmin@cmi:~$ sudo cat /etc/jitsi/videobridge/sip-communicator.properties
org.jitsi.videobridge.AUTHORIZED_SOURCE_REGEXP=focus@auth.cmi.fast.sheridanc.on.ca/.*
org.ice4j.ice.harvest.NAT_HARVESTER_LOCAL_ADDRESS=142.55.32.25
org.ice4j.ice.harvest.NAT_HARVESTER_PUBLIC_ADDRESS=142.55.32.25`

This is incorrect if your machine has interface with address 142.55.32.25, then remove those two lines. This is needed only if the VM is behind nat and ports will be forwarded.

[BlakeEram]

is this file https://github.com/jitsi/jitsi-meet/blob/master/doc/debian/jitsi-meet/jitsi-meet.example-apache#L23 installed with jitsi-meet? or do you know where it would be installed

I am very new to this, I appreciate your help so much

[damencho]

It should be in /etc/apache2/sites-available/YOUR_HOSTNAME.conf

[BlakeEram]

I have 000-default.conf and default-ssl.conf, I assume its default-ssl.conf that I need to edit?

[BlakeEram]

I configured default-ssl.conf with the correct directory. DocumentRoot "~/m-health"

      <Directory "~/m-health">
                  Options Indexes MultiViews Includes FollowSymLinks
                  AddOutputFilter Includes html
                  AllowOverride All
                  Order allow,deny
                  Allow from all
                </Directory>

when i go to my address https://cmi.fast.sheridanc.on.ca/, it says the site cannot be reached.

[damencho]

No this is apache default files, you should no edit them, apparently you do not have the jitsi-meet apache config installed. Did you have apache installed before doing the first jitsi-meet install? Can you check do you have folder /etc/nginx ?

[BlakeEram]

vmadmin@cmi:/home$ cd /etc/nginx 
vmadmin@cmi:/etc/nginx$ ls
conf.d        fastcgi_params  koi-win     nginx.conf    scgi_params      sites-enabled  uwsgi_params
fastcgi.conf  koi-utf         mime.types  proxy_params  sites-available  snippets       win-utf
vmadmin@cmi:/etc/nginx$ ls sites-available/
default

[damencho]

Hum, that is strange and in your jvb sip-communicator.properties you do not have any "org.jitsi.videobridge.rest.jetty...." configs?

Something terribly got wrong there, not sure how this is possible at all.

So, if you are not using nginx, my proposal is to purge jitsi-meet and nginx, this will Delete any custom config for them and then install again. If you already have apache2 installed it should configure it and use it. apt-get purge jitsi-meet jitsi-meet-web-config jitsi-meet-prosody jitsi-meet-web jicofo jitsi-videobridge nginx

[BlakeEram]

sudo apt-get purge jitsi-meet-web-config
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  authbind lua-event lua-expat lua-filesystem lua-sec lua-socket lua5.1 prosody
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  jitsi-meet-web-config
0 upgraded, 0 newly installed, 1 to remove and 88 not upgraded.
1 not fully installed or removed.
After this operation, 49.2 kB disk space will be freed.
Do you want to continue? [Y/n] Y
(Reading database ... 168894 files and directories currently installed.)
Removing jitsi-meet-web-config (1.0.2740-1) ...
apache2.service is not active, cannot reload.
invoke-rc.d: initscript apache2, action "reload" failed.
dpkg: error processing package jitsi-meet-web-config (--remove):
 subprocess installed post-removal script returned error exit status 1
Errors were encountered while processing:
 jitsi-meet-web-config
E: Sub-process /usr/bin/dpkg returned an error code (1)

I get this error, would it be easier to wipe my server, considering there is currently nothing on it?

[damencho]

But why you purge only this?

[damencho]

Hum it complains about not able to restart apache ... someone was complaining about similar thing ...

[BlakeEram]

I purged all of them but jitsi-meet-web-config wont delete

[BlakeEram]

sudo apt-get purge jitsi-meet jitsi-meet-web-config jitsi-meet-prosody jitsi-meet-web jicofo jitsi-videobridge nginx
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  authbind lua-event lua-expat lua-filesystem lua-sec lua-socket lua5.1 prosody
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  jicofo* jitsi-meet* jitsi-meet-prosody* jitsi-meet-web* jitsi-meet-web-config* jitsi-videobridge* nginx*
0 upgraded, 0 newly installed, 7 to remove and 88 not upgraded.
After this operation, 122 MB disk space will be freed.
Do you want to continue? [Y/n] Y
(Reading database ... 169323 files and directories currently installed.)
Removing jitsi-meet (1.0.2988-1) ...
Purging configuration files for jitsi-meet (1.0.2988-1) ...
Removing jitsi-meet-prosody (1.0.2740-1) ...
Purging configuration files for jitsi-meet-prosody (1.0.2740-1) ...
Removing jicofo (1.0-405-1) ...
Purging configuration files for jicofo (1.0-405-1) ...
Removing user `jicofo' ...
Warning: group `jitsi' has no more members.
Done.
Removing jitsi-meet-web (1.0.2740-1) ...
Removing jitsi-meet-web-config (1.0.2740-1) ...
apache2.service is not active, cannot reload.
invoke-rc.d: initscript apache2, action "reload" failed.
dpkg: error processing package jitsi-meet-web-config (--purge):
 subprocess installed post-removal script returned error exit status 1
Removing jitsi-videobridge (1055-1) ...
Purging configuration files for jitsi-videobridge (1055-1) ...
Removing user `jvb' ...
Warning: group `jitsi' has no more members.
Done.
dpkg: warning: while removing jitsi-videobridge, directory '/etc/jitsi/videobridge' not empty so not removed
Removing nginx (1.10.3-0ubuntu0.16.04.2) ...
Errors were encountered while processing:
 jitsi-meet-web-config
E: Sub-process /usr/bin/dpkg returned an error code (1)

[BlakeEram]

I can wipe the server and start from the beginning, this way I am not just trying things hoping for the best. Again I cannot thank you enough for your help

[damencho]

Do apt-get install apache2 first and then apt-get install jitsi-meet.

[BlakeEram]

if im installing my custom version of Jitsi-Meet, apt-get install jitsi-meet the right command to install?

[damencho]

This will install latest jitsi-meet(no midifications). Then you need to edit the path in your web server that points to your custom jitsi-meet instead of /usr/share/jitsi-meet.

[BlakeEram]

I will be pulling my jitsi-meet of my github, do I need to install that one as well or no?

[damencho]

So there are two options to create debian packages and host your own debian repo ith different versioning for jitsi-meet or run it from source, with my statement above my advice (as it is quicker) is to run it from source.

[BlakeEram]

Sorry for my lack knowledge, what do you mean run it from source? Not get it from github?

[damencho]

Running your modified version from source means, you clone from github directly from github.com/jitsi or from your fork, modify the source code and let the web server serve that custom jitsi-meet version.

[BlakeEram]

Thanks for clarifying, and when I pull my version from github, i would install my version?

[damencho]

You just need npm install && make and edit your webserver config to point to your modified version. First, make sure everything works with just apt-get install ...

[BlakeEram]

Okay perfect, I will hopefully respond with good news soon. Again thanks for everything

[BlakeEram]

Do I need to install jicofo, videobridge ..., with my app as well?

[damencho]

Yep, this is what apt-get install jitsi-meet will do, it will install and configure all that is needed.

[BlakeEram]

Just so I have the commands in order:

apt-get install apache2 
apt-get install jitsi-meet
git clone myapp
cd myapp
npm install --g get-dependencies
npm install myapp
make

then configure apache2 to myapp

[damencho]

npm install --g get-dependencies
npm install myapp

I'm not sure what these do. But to make jitsi-meet you just need npm install. As stated in the readme https://github.com/jitsi/jitsi-meet/blob/master/README.md#building-the-sources

[BlakeEram]

npm install --g get-dependencies - will get the dependencies that my app has that jitsi-meet may not
npm install myapp - is suppose to be npm install

[BlakeEram]

After peforming

apt-get install apache2 
apt-get install jitsi-meet
git clone myapp
cd myapp
npm install 
make

and go to /etc/apache2/sites-available/ there is nothing new is there something I am missing?

[damencho]

You mean there is no jitsi-meet config in that folder?

[BlakeEram]

no there was nothing there, we did a full wipe on the server, apt-get install jitsi-meet gives me

vmadmin@cmi:~$ sudo apt-get install jitsi-meet
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package jitsi-meet

do you recommend using this command first?

echo 'deb https://download.jitsi.org stable/' >> /etc/apt/sources.list.d/jitsi-stable.list
wget -qO -  https://download.jitsi.org/jitsi-key.gpg.key | apt-key add -

[damencho]

Yes of course these are the steps if you are reading the quick install guide https://github.com/jitsi/jitsi-meet/blob/master/doc/quick-install.md

[BlakeEram]

I configured sudo nano cmi.fast.sheridanc.on.ca.conf to

` DocumentRoot "~/m-health"
  <Directory "~/m-health">
    Options Indexes MultiViews Includes FollowSymLinks
    AddOutputFilter Includes html
    AllowOverride All
    Order allow,deny
    Allow from all
  </Directory>`

when i go to https://cmi.fast.sheridanc.on.ca/

i get

any ideas?

[damencho]

Don't you have a specific jitsi-meet apache2 config under /etc/apache2/sites-available/ ?

[BlakeEram]

vmadmin@cmi:/etc/apache2/sites-available$ ls
000-default.conf  cmi.fast.sheridanc.on.ca.conf  default-ssl.conf

and inside was, and the orignal jitsi-meet worked

DocumentRoot "/usr/share/jitsi-meet"
  <Directory "/usr/share/jitsi-meet">
    Options Indexes MultiViews Includes FollowSymLinks
    AddOutputFilter Includes html
    AllowOverride All
    Order allow,deny
    Allow from all
  </Directory>

but after I changed it to, where my custom version of jitsi-meet is

 DocumentRoot "/m-health/"
  <Directory "/m-health/">
    Options Indexes MultiViews Includes FollowSymLinks
    AddOutputFilter Includes html
    AllowOverride All
    Order allow,deny
    Allow from all
  </Directory>

and it gives me

any ideas?

[damencho]

Does the user as which runs apache2(www-data) has at least read rights to that folder? Most probably apache cannot read from that folder.

[BlakeEram]

do you have the command that would change the read rights I have tried and did not change the problem sudo chmod -R ugo+r ~/m-health/

[damencho]

Wait in your apache config you have /m-health/, which means the folder is under /, while in this command you are using ~/m-health/ which should be something like /home/user/m-health. You are using wrong directories in the apache config. Move the m-health out of your home for example in /opt and then make sure the www-data has read access to it and modify apache config to be /opt/m-health

[BlakeEram]

I got it to run on my domain, again thanks for your help but no video is showing up. I have checked my webcam and it works on other things. I get this error [react/features/base/connection/actions.web.js] <r/</<>: Error: Missing strophe-plugins (disco plugin is required)!