User Tools

Site Tools


computing:nmbbb

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
computing:nmbbb [2022/11/12 05:03] oemb1905computing:nmbbb [2022/11/12 05:23] (current) oemb1905
Line 28: Line 28:
   sudo mv /opt/freeswitch/etc/freeswitch/sip_profiles/external-ipv6.xml /opt/freeswitch/etc/freeswitch/sip_profiles/external-ipv6.xml_   sudo mv /opt/freeswitch/etc/freeswitch/sip_profiles/external-ipv6.xml /opt/freeswitch/etc/freeswitch/sip_profiles/external-ipv6.xml_
      
-Post-install +It is now time to set up Greenlight.
- +
-https://docs.bigbluebutton.org/admin/customize.html#secure-your-system--restrict-access-to-specific-ports  +
-  +
-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 pcopart 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 ....  --- //[[jonathan@haacksnetworking.com|oemb1905]] 2021/10/29 22:04//+
  
   mkdir ~/greenlight   mkdir ~/greenlight
Line 44: Line 35:
 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 supportOpen the xml file and change the line to listen to local host only.+  docker run --rm bigbluebutton/greenlight:v2 cat ./greenlight.nginx | sudo tee /etc/bigbluebutton/nginx/greenlight.nginx 
 +  sudo systemctl restart nginx
  
-  nano /opt/freeswitch/etc/freeswitch/autoload_configs/event_socket.conf.xml +Now, let's start greenlight:  
-  <param name="listen-ip" value="127.0.0.1"/> +
-   +
-Starting greenlight:+
  
   cd ~/greenlight   cd ~/greenlight
 +  docker-compose -v
 +  mkdir /etc/bigbluebutton/nginx/
 +  touch /etc/bigbluebutton/nginx/greenlight.nginx
 +  docker run --rm bigbluebutton/greenlight:v2 cat ./docker-compose.yml > docker-compose.yml
 +  export pass=$(openssl rand -hex 24); sed -i 's/POSTGRES_PASSWORD=password/POSTGRES_PASSWORD='$pass'/g' docker-compose.yml;sed -i 's/DB_PASSWORD=password/DB_PASSWORD='$pass'/g' .env
   docker-compose up -d   docker-compose up -d
      
  
- + --- //[[jonathan@haacksnetworking.org|oemb1905]] 2022/11/11 22:12//
- --- //[[jonathan@haacksnetworking.org|oemb1905]] 2022/07/15 23:22//+
computing/nmbbb.1668229390.txt.gz · Last modified: 2022/11/12 05:03 by oemb1905