This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
bigbluebutton_setup [2021/08/01 17:01] 157.51.110.15 |
bigbluebutton_setup [2021/09/02 13:48] (current) 157.49.226.162 |
||
|---|---|---|---|
| Line 37: | Line 37: | ||
| **sudo bbb-conf --restart** | **sudo bbb-conf --restart** | ||
| + | |||
| **sudo bbb-conf –check** | **sudo bbb-conf –check** | ||
| Line 83: | Line 84: | ||
| In addition, we’ll generate a set of 4096-bit diffie-hellman parameters to improve security for some types of ciphers. This step can take several minutes to complete, particularly if run on a virtual machine. | In addition, we’ll generate a set of 4096-bit diffie-hellman parameters to improve security for some types of ciphers. This step can take several minutes to complete, particularly if run on a virtual machine. | ||
| - | **sudo mkdir -p /etc/nginx/ssl** | ||
| **sudo openssl dhparam -out /etc/nginx/ssl/dhp-4096.pem 4096** | **sudo openssl dhparam -out /etc/nginx/ssl/dhp-4096.pem 4096** | ||
| Line 104: | Line 104: | ||
| | | ||
| For reference, note that the SSL settings used above are based on those proposed in https://hynek.me/articles/hardening-your-web-servers-ssl-ciphers/ and provide support for all modern browsers (including IE8, but not IE6, on Windows XP). Please note that recommended SSL settings are subject to change as new vulnerabilities are found. | For reference, note that the SSL settings used above are based on those proposed in https://hynek.me/articles/hardening-your-web-servers-ssl-ciphers/ and provide support for all modern browsers (including IE8, but not IE6, on Windows XP). Please note that recommended SSL settings are subject to change as new vulnerabilities are found. | ||
| + | |||
| + | **Configure BigBlueButton to load session via HTTPS** | ||
| + | |||
| + | With nginx now configured to use SSL, the next step is to configure FreeSWITCH to use HTTPS for initiating an audio connection. | ||
| + | |||
| + | Edit **/usr/share/bbb-web/WEB-INF/classes/bigbluebutton.properties** and update the property bigbluebutton.web.serverURL to use HTTPS: | ||
| + | |||
| + | #---------------------------------------------------- | ||
| + | # This URL is where the BBB client is accessible. When a user successfully | ||
| + | # enters a name and password, she is redirected here to load the client. | ||
| + | |||
| + | bigbluebutton.web.serverURL=https://bigbluebutton.example.com | ||
| + | |||
| + | Next, edit the file **/usr/share/red5/webapps/screenshare/WEB-INF/screenshare.properties** and update the property jnlpUrl and jnlpFile to HTTPS: | ||
| + | |||
| + | streamBaseUrl=rtmp://bigbluebutton.example.com/screenshare | ||
| + | jnlpUrl=https://bigbluebutton.example.com/screenshare | ||
| + | jnlpFile=https://bigbluebutton.example.com/screenshare/screenshare.jnlp | ||
| + | |||
| + | You must also update the file /var/www/bigbluebutton/client/conf/config.xml to tell the BigBlueButton | ||
| + | client to load components via HTTPS. | ||
| + | |||
| + | You can do the update with a single command | ||
| + | |||
| + | **$ sudo sed -e 's|http://|https://|g' -i /var/www/bigbluebutton/client/conf/config.xml** | ||
| + | |||
| + | If you would ever need to revert this change, you can run the reverse command: | ||
| + | |||
| + | **$ sudo sed -e 's|https://|http://|g' -i /var/www/bigbluebutton/client/conf/config.xml** | ||
| + | |||
| + | Open **/usr/share/meteor/bundle/programs/server/assets/app/config/settings.yml** editing and change: | ||
| + | |||
| + | kurento: | ||
| + | wsUrl: ws://bbb.example.com/bbb-webrtc-sfu | ||
| + | to | ||
| + | kurento: | ||
| + | wsUrl: wss://bbb.example.com/bbb-webrtc-sfu | ||
| + | |||
| + | Also change: | ||
| + | note: | ||
| + | enabled: true | ||
| + | url: http://bbb.example.com/pad | ||
| + | to | ||
| + | note: | ||
| + | enabled: true | ||
| + | url: https://bbb.example.com/pad | ||
| + | |||
| + | Next, modify the creation of recordings so they are served via HTTPS. | ||
| + | |||
| + | Edit **/usr/local/bigbluebutton/core/scripts/bigbluebutton.yml** and change the value for playback_protocol as | ||
| + | |||
| + | follows: | ||
| + | playback_protocol: https | ||
| + | | ||
| + | /var/lib/tomcat7/webapps/demo/bbb_api_conf.jsp and change the value of BigBlueButtonURL use HTTPS. | ||
| + | | ||
| + | // This is the URL for the BigBlueButton server | ||
| + | String BigBlueButtonURL = "https://bigbluebutton.example.com/bigbluebutton/"; | ||
| + | |||
| + | Finally, to apply all of the configuration changes made, you must restart all components of BigBlueButton: | ||
| + | |||
| + | **sudo bbb-conf –restart** | ||
| + | |||
| + | =====Uninstall Bigbluebutton===== | ||
| + | |||
| + | If anytime you need to uninstall bigbluebutton service from the ubuntu server. You can purge and remove each bbb packages one by one | ||
| + | |||
| + | **dpkg -l | grep bbb** | ||
| + | | ||
| + | apt-get purge bbb-apps | ||
| + | apt-get purge bbb-apps-akka | ||
| + | apt-get purge bbb-apps-screenshare | ||
| + | apt-get purge bbb-apps-sip | ||
| + | apt-get purge bbb-apps-video | ||
| + | apt-get purge bbb-apps-video-broadcast | ||
| + | apt-get purge bbb-client | ||
| + | apt-get purge bbb-config | ||
| + | apt-get purge bbb-demo | ||
| + | apt-get purge bbb-etherpad | ||
| + | apt-get purge bbb-freeswitch-core | ||
| + | apt-get purge bbb-freeswitch-sounds | ||
| + | apt-get purge bbb-fsesl-akka | ||
| + | apt-get purge bbb-html | ||
| + | apt-get purge bbb-mkclean | ||
| + | apt-get purge bbb-playback-presentation | ||
| + | apt-get purge bbb-record-core | ||
| + | apt-get purge bbb-red5 | ||
| + | apt-get purge bbb-transcode-akka | ||
| + | apt-get purge bbb-web | ||
| + | apt-get purge bbb-webrtc-sfu | ||
| + | |||