Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
computing:nmbbb [2022/11/12 03:47] – oemb1905 | computing:nmbbb [2022/11/12 05:09] – oemb1905 |
---|
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 | 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 |
| |
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: | 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 apt install letsencrypt python-certbot-nginx | sudo nano /opt/freeswitch/etc/freeswitch/autoload_configs/event_socket.conf.xml |
sudo certbot --authenticator standalone --installer nginx -d example.com --pre-hook "systemctl stop nginx" --post-hook "systemctl start nginx" | <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_ |
| |
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// | It is now time to set up Greenlight. |
| |
mkdir ~/greenlight | mkdir ~/greenlight |
If you lock yourself out of admin account after a vanilla install. | If you lock yourself out of admin account after a vanilla install. |
| |
docker exec -it greenlight-v2 bash | docker run --rm bigbluebutton/greenlight:v2 cat ./sample.env > .env |
bundle exec rails c | docker run --rm bigbluebutton/greenlight:v2 bundle exec rake secret |
User.find_by(email: "<email of user to reset>").update_attribute(:password,"<new password>") | sudo bbb-conf --secret |
| docker run --rm --env-file .env bigbluebutton/greenlight:v2 bundle exec rake conf:check |
| |
Disabled ipv6 since BR does not support. Open the xml file and change the line to listen to local host only. | Disabled ipv6 since BR does not support. Open the xml file and change the line to listen to local host only. |