| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
| computing:nmbbb [2021/04/03 03:34] – oemb1905 | computing:nmbbb [2022/11/12 05:03] – oemb1905 |
|---|
| ------------------------------------------- | ------------------------------------------- |
| |
| This tutorial is for folks who have a need for a [[https://docs.bigbluebutton.org/|Big Blue Button]] instance. In my case, I am a teacher and I need a reliable digital instructional platform that is also full of features ... and floss. BBB is the only choice for these requirements. Moreover, it also helps with a specific //thinking routine// I developed, called [[https://youtu.be/lOKaVAsyDaY|Inquirer Presenter Scribe]]. The platform and the approach together provide a rich opportunity for mathematical seminar and other forms of pedagogy. This service will, furthermore, be available to all New Mexico educators for free - schedule details will be released when/if the project reaches full maturity, which we hope it will. This will be the official wiki for documentation of configs, setup, etc. The status page and client functionality update site is located here [[https://haacksnetworking.com/2021/03/31/nm-community-big-blue-button-project/|over at my business website]]. Alright, more later folks. | This tutorial is for setting up a BBB instance using their installer script. In my case, this instance will run in a virtualized environment on a physical host with a symmetric gig connection. |
| |
| ------------------------------------------- | ------------------------------------------- |
| Step #1 | Step #1 |
| |
| I have found from trial and error that for some reason it helps to set up a basic apache web server first, disable it, then run their script. If you don't know how to do this, see the [[https://wiki.haacksnetworking.com/doku.php?id=computing:apachesurvival|apachesurvival]] tutorial but do not add php and mysql/mariadb. Just prior to running the bbb-install.sh script they provide, remove the apache2 package. Once the script completes, simply reinstall the certbot packages and then debug from there. There are long reasons for this - but, in short, it is because of how Ubuntu 16 - required for BBB - works with certbot and TLS. From here, once the basic instance is up, we switch to setting up greenlight, which we do as follows. Again, I am using the guide I cited above, so follow along as I use that to set up this particular instance. | Okay, so I installed a clean Ubuntu 18.04.6 on a VM with 8 processors and 16GB RAM. I used the install script found at the [[https://docs.bigbluebutton.org/2.3/install.html#Install_|BBB documentation/install website]]: |
| | |
| | wget -qO- https://ubuntu.bigbluebutton.org/bbb-install-2.5.sh | bash -s -- -v focal-250 -s bbb.example.com -e notice@example.com -a -w |
| | |
| | Since my data center does not support ipv6, I needed to disable this. I am working with Brown Rice to make ipv6 a reality, but all in good time. BBB ipv6 [[https://docs.bigbluebutton.org/support/troubleshooting.html#freeswitch-fails-to-bind-to-port-8021|disable resource]]. |
| | |
| | sudo nano /opt/freeswitch/etc/freeswitch/autoload_configs/event_socket.conf.xml |
| | <param name="listen-ip" value="127.0.0.1"/> |
| | sudo mv /opt/freeswitch/etc/freeswitch/sip_profiles/internal-ipv6.xml /opt/freeswitch/etc/freeswitch/sip_profiles/internal-ipv6.xml_ |
| | sudo mv /opt/freeswitch/etc/freeswitch/sip_profiles/external-ipv6.xml /opt/freeswitch/etc/freeswitch/sip_profiles/external-ipv6.xml_ |
| | |
| | Post-install |
| | |
| | https://docs.bigbluebutton.org/admin/customize.html#secure-your-system--restrict-access-to-specific-ports |
| | |
| | After this completed, I checked for errors and as directed ran ''sudo bbb-conf --check''. It's not time to debug BBB yet, as Greenlight, which manages users and accounts, etc., is not even configured yet. however, it is time to debug failures on the install script, and one pcopart that always fails for me is the Let's Encrypt portion. I just ignore it, however, and then run the following commands manually: |
| | |
| | sudo apt install letsencrypt python-certbot-nginx |
| | sudo certbot --authenticator standalone --installer nginx -d example.com --pre-hook "systemctl stop nginx" --post-hook "systemctl start nginx" |
| | |
| | This lengthy script does what the BBB script does not do properly, and what many other users forget to do, which is properly start and stop the webserver during automatic setup and/or properly start/stop during manual setup. It was posted by someone long ago on the ACME git, and it still works cherry. After fixing this (yep, it worked again), I then finally could run ''sudo bbb-conf --check''. The output revealed that .... --- //[[jonathan@haacksnetworking.com|oemb1905]] 2021/10/29 22:04// |
| |
| mkdir ~/greenlight | mkdir ~/greenlight |
| cd ~/greenlight | cd ~/greenlight |
| | |
| | If you lock yourself out of admin account after a vanilla install. |
| | |
| | docker exec -it greenlight-v2 bash |
| | bundle exec rails c |
| | User.find_by(email: "<email of user to reset>").update_attribute(:password,"<new password>") |
| | |
| | Disabled ipv6 since BR does not support. Open the xml file and change the line to listen to local host only. |
| | |
| | nano /opt/freeswitch/etc/freeswitch/autoload_configs/event_socket.conf.xml |
| | <param name="listen-ip" value="127.0.0.1"/> |
| | |
| | Starting greenlight: |
| | |
| | cd ~/greenlight |
| | docker-compose up -d |
| | |
| | |
| |
| --- //[[jonathan@haacksnetworking.com|oemb1905]] 2021/04/02 21:25// | --- //[[jonathan@haacksnetworking.org|oemb1905]] 2022/07/15 23:22// |
