BBB 2.3 couldn't make it work on a public address

76 views
Skip to first unread message

Idriss Hassani

unread,
Sep 8, 2021, 8:00:18 AM9/8/21
to BigBlueButton-Setup
Hello everyone, I hope you are doing fine,

I know my problem is common but I really tried many leads from different websites but I couldn't solve it...

I'm working for a company and they put me on a project where I have to add BBB to Mattermost. 

Here is what I get with bbb-conf --check

BigBlueButton Server 2.3.6 (2378)
                    Kernel version: 4.15.0-147-generic
                      Distribution: Ubuntu 18.04.5 LTS (64-bit)
                            Memory: 4038 MB
                         CPU cores: 8

/etc/bigbluebutton/bbb-web.properties (override for bbb-web)
/usr/share/bbb-web/WEB-INF/classes/bigbluebutton.properties (bbb-web)
       bigbluebutton.web.serverURL: https://<DOMAIN_NAME>
                defaultGuestPolicy: ALWAYS_ACCEPT
                 svgImagesRequired: true

/etc/nginx/sites-available/bigbluebutton (nginx)
                       server_name: <DOMAIN_NAME>
                              port: 80, [::]:80
                              port: 443 ssl

/opt/freeswitch/etc/freeswitch/vars.xml (FreeSWITCH)
                       local_ip_v4: <PRIVATE_IP>
                   external_rtp_ip: <PUBLIC_IP>
                   external_sip_ip: <PUBLIC_IP>

/opt/freeswitch/etc/freeswitch/sip_profiles/external.xml (FreeSWITCH)
                        ext-rtp-ip: $${external_rtp_ip}
                        ext-sip-ip: $${external_sip_ip}
                        ws-binding: <PUBLIC_IP>:5066
                       wss-binding: :7443

/usr/local/bigbluebutton/core/scripts/bigbluebutton.yml (record and playback)
                     playback_host: <DOMAIN_NAME>
                 playback_protocol: http
                            ffmpeg: 4.2.4-1ubuntu0.1bbb2~18.04

/etc/bigbluebutton/nginx/sip.nginx (sip.nginx)
                        proxy_pass: <PUBLIC_IP>
                          protocol: http

/usr/local/bigbluebutton/bbb-webrtc-sfu/config/default.yml (Kurento SFU)
                        kurento.ip: <PUBLIC_IP>
                       kurento.url: ws://127.0.0.1:8888/kurento
                    kurento.sip_ip: <PUBLIC_IP>
                    localIpAddress: <PRIVATE_IP>
               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: 1801
                        kurentoUrl: wss://<DOMAIN_NAME>/bbb-webrtc-sfu
                  enableListenOnly: true
                    sipjsHackViaWs: true

/usr/share/bbb-web/WEB-INF/classes/spring/turn-stun-servers.xml (STUN Server)
                              stun: stun.l.google.com:19302

/etc/kurento/modules/kurento/WebRtcEndpoint.conf.ini (STUN Server)
                              stun: 172.217.212.127:19302


# Potential problems described below
curl: (7) Failed to connect to <DOMAIN_NAME> port 443: Connection refused
curl: (7) Failed to connect to <DOMAIN_NAME> port 443: Connection refused
# Error: Could not connect to the configured hostname/IP address
#
#    https://<DOMAIN_NAME>
#
# If your BigBlueButton server is behind a firewall, see FAQ.

# Warning: The API demos are installed and accessible from:
#
#    https://<DOMAIN_NAME>
#
# and
#
#    https:// <DOMAIN_NAME>/demo/demo1.jsp
#
# These API demos allow anyone to access your server without authentication
# to create/manage meetings and recordings. They are for testing purposes only.
# If you are running a production system, remove them by running:
#
#    apt-get purge bbb-demo

curl: (7) Failed to connect to  <DOMAIN_NAME>   port 443: Connection refused
# Error: Unable to reach default URL for presentation:
#
#    https:// <DOMAIN_NAME>/default.pdf
#
# Check value for beans.presentationService.defaultUploadedPresentation in
#   /usr/share/bbb-web/WEB-INF/classes/bigbluebutton.properties and /etc/bigbluebutton/bbb-web.properties

#
# Warning: Failed to verify STUN server at stun.l.google.com 19302 with command
#
#    stunclient --mode full --localport 30000 stun.l.google.com 19302
#

#
# Warning: Failed to verify STUN server at 172.217.212.127:19302 with command
#
#    stunclient --mode full --localport 30000 172.217.212.127 19302


for the SSL Certificates I have configured it correctly because when I tried it in our private network it worked perfectly.

I hope you can help me, I'd really appreciate it.

Kind regards
Reply all
Reply to author
Forward
0 new messages