Issues on 2.3

[paolo podestà]

Hi, I manage a BBB installation since 0-9-

I switched to the bbb-install.sh this year for the 2.3 and run in  several problems.

Now it seems I managed to solve most of the problems and got it to work but I have something strange in turn settings:

BigBlueButton Server 2.3.12 (2427)

                    Kernel version: 4.15.0-154-generic

                      Distribution: Ubuntu 18.04.5 LTS (64-bit)

                            Memory: 65934 MB

                         CPU cores: 12

/etc/bigbluebutton/bbb-web.properties (override for bbb-web)

/usr/share/bbb-web/WEB-INF/classes/bigbluebutton.properties (bbb-web)

       bigbluebutton.web.serverURL: https://webinar.trinitycollege.it

                defaultGuestPolicy: ALWAYS_ACCEPT

                 svgImagesRequired: true

/etc/nginx/sites-available/bigbluebutton (nginx)

                       server_name: webinar.trinitycollege.it

                              port: 80, [::]:80

                              port: 443 ssl

/opt/freeswitch/etc/freeswitch/vars.xml (FreeSWITCH)

                       local_ip_v4: 176.31.228.9

                   external_rtp_ip: 176.31.228.9

                   external_sip_ip: 176.31.228.9

/opt/freeswitch/etc/freeswitch/sip_profiles/external.xml (FreeSWITCH)

                        ext-rtp-ip: $${local_ip_v4}

                        ext-sip-ip: $${local_ip_v4}

                        ws-binding: 176.31.228.9:5066

                       wss-binding: 176.31.228.9:7443

/usr/local/bigbluebutton/core/scripts/bigbluebutton.yml (record and playback)

                     playback_host: webinar.trinitycollege.it

                 playback_protocol: https

                            ffmpeg: 4.2.4-1ubuntu0.1bbb2~18.04

/etc/bigbluebutton/nginx/sip.nginx (sip.nginx)

                        proxy_pass: 176.31.228.9

                          protocol: http

/usr/local/bigbluebutton/bbb-webrtc-sfu/config/default.yml (Kurento SFU)

                        kurento.ip: 176.31.228.9

                       kurento.url: ws://127.0.0.1:8888/kurento

                    kurento.sip_ip: 176.31.228.9

                    localIpAddress: 176.31.228.9

               recordScreenSharing: true

                     recordWebcams: true

                  codec_video_main: VP8

               codec_video_content: VP8

/usr/share/meteor/bundle/programs/server/assets/app/config/settings.yml (HTML5 client)

                             build: 1833

                        kurentoUrl: wss://webinar.trinitycollege.it/bbb-webrtc-sfu

                  enableListenOnly: true

                    sipjsHackViaWs: true

/usr/share/bbb-web/WEB-INF/classes/spring/turn-stun-servers.xml (STUN Server)

                              stun: turn.trinitycollege.it

# Potential problems described below

after I tried the override file i just have in the check output only the stun conf and nothing about turn. nothing change if I rename the override file .

Is it normal?

Paolo

[Julien Gribonvald]

Hi,

On my side I'm switching from 2.2 to 2.3 and, like described from the doc, I think the best is to provide a custom overriding file like described here: https://docs.bigbluebutton.org/admin/configuration-files.html#local-overrides-for-configuration-settings

So in /etc/bigbluebutton/ provide directly your custom configuration turn-stun-servers.xml file.

Thanks

Julien Gribonvald

--
You received this message because you are subscribed to the Google Groups "BigBlueButton-Setup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-s...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bigbluebutton-setup/970715e5-f782-4720-8499-2b57405b714dn%40googlegroups.com.

[paolo podestà]

Thanks Julien, unfortunately the "issue" started as soon as I provided the override file. If your switching to 2.3 on a clean ubuntu 18 there's some undocumented option to take care of:

 

-d "Skip SSL certificates request (use provided certificates from mounted volume)" 

  to make it works you need to put your certificate in /local/certs named fullchain.pem and privkey.pem
  if [ -z "$PROVIDED_CERTIFICATE" ]; then
     ...... setup certbot
  else
    mkdir -p /etc/letsencrypt/live/$HOST/
    ln -s /local/certs/fullchain.pem /etc/letsencrypt/live/$HOST/fullchain.pem
    ln -s /local/certs/privkey.pem /etc/letsencrypt/live/$HOST/privkey.pem
  fi

- m <link_path> Create a Symbolic link from /var/bigbluebutton to <link_path>

after a few try (and ubuntu reinstall) I just removed the option and set up the symlink manually  after the install 

if [ ! -z "$LINK_PATH" ]; then
  ln -s "$LINK_PATH" "/var/bigbluebutton"
fi

after a clean install $LINK_PATH does not exist.