This is an old revision of the document!
- nmbbb
- Jonathan Haack
- Haack's Networking
- netcmnd@jonathanhaack.com
nmbbb
This tutorial is for folks who have a need for a 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 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 at my business website which oversees the project. Alright, more later folks.
Step #1
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 BBB documentation/install website:
wget -qO- https://ubuntu.bigbluebutton.org/bbb-install.sh | bash -s -- -v bionic-230 -s bbb.example.com -e notice@example.com -a -w
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 part 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 …. — oemb1905 2021/10/29 22:04
mkdir ~/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
— oemb1905 2022/07/15 23:22
