

This is because the packaging scripts automatically configure BigBlueButton using the first non-loopback IP address, whereas access to sensitive ports is blocked.Ī variation of this setup occurs when the server has multiple network interfaces, but the external IP is still the first network interface (such as eth0) picked up by the installation scripts. In this simple network configuration, BigBlueButton should work out-of-the-box after installation.

Here is an example of such a setup with the BigBlueButton server having a (fictional) IP address 203.0.113.1 with hostname.

Port-based access firewalling is implemented using UFW. The easiest network configuration for installing BigBlueButton is on a server that has a single external IP address and the server is on the public Internet (and thus directly accessible by your users). If you are a developer setting up BigBlueButton on a local VM for testing, you can skip this section. You should configure your firewall before Installing BigBlueButton otherwise, you may get errors during the installation and will be unable to test BigBlueButton after the installation completes. This document covers firewall configuration for BigBlueButton 2.2.
