Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
computing:nmbbb [2021/04/30 21:02] – oemb1905 | computing:nmbbb [2021/10/30 03:33] – oemb1905 |
---|
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.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. |
| |
mkdir ~/greenlight | mkdir ~/greenlight |