Error 1010 - BBB V3 fresh install - physical cloud server

48 views
Skip to first unread message

Mohamed

unread,
May 21, 2025, 11:34:59 AM5/21/25
to BigBlueButton-Setup
Hello dear community, 

i have just installed the lastest version of BBB on our own server.

i have an Error 1010
can somebody help. there are the obvious one like the ip adres who are the same for internal and external.
i don't know if i need to use port 7443 or 5066?

to be sure i didn't do something wrong i only did a fresh install and delete a file.
and that's it. what should i do to make it work from here please.

config: 
BigBlueButton Server 3.0.7 (2540)
                    Kernel version: 6.8.0-59-generic
                      Distribution: Ubuntu 22.04.5 LTS (64-bit)
                            Memory: 16329 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://8d72d73885c3392ece98d323b51b92bb.serveo.net
                defaultGuestPolicy: ALWAYS_ACCEPT
              defaultMeetingLayout: CUSTOM_LAYOUT

/etc/nginx/sites-available/bigbluebutton (nginx)
                       server_name: 192.168.87.129
                              port: 80, [::]:80

/opt/freeswitch/etc/freeswitch/vars.xml (FreeSWITCH)
                       local_ip_v4: 192.168.87.129
                   external_rtp_ip: 192.168.87.129
                   external_sip_ip: 192.168.87.129

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

UDP port ranges

                        FreeSWITCH: 16384-24576
                    bbb-webrtc-sfu: 24577-32768
                    bbb-webrtc-recorder: 24577-32768

/usr/local/bigbluebutton/core/scripts/bigbluebutton.yml (record and playback)
                     playback_host: 192.168.50.50
                 playback_protocol: https
                            ffmpeg: 4.4.2-0ubuntu0.22.04.1

/usr/share/bigbluebutton/nginx/sip.nginx (sip.nginx)
                        proxy_pass: 192.168.87.129
                          protocol: http

/usr/local/bigbluebutton/bbb-webrtc-sfu/config/default.yml (bbb-webrtc-sfu)
/etc/bigbluebutton/bbb-webrtc-sfu/production.yml (bbb-webrtc-sfu - override)
    mediasoup.webrtc.*.announcedIp: 192.168.87.129
  mediasoup.plainRtp.*.announcedIp: 192.168.87.129
                 freeswitch.sip_ip: 192.168.87.129
                  recordingAdapter: bbb-webrtc-recorder
               recordScreenSharing: true
                     recordWebcams: true
                  codec_video_main: VP8
               codec_video_content: VP8

/etc/bbb-webrtc-recorder/bbb-webrtc-recorder.yml (bbb-webrtc-recorder)
/etc/bigbluebutton/bbb-webrtc-recorder.yml (bbb-webrtc-recorder - override)
               debug: null
               recorder.directory: /var/lib/bbb-webrtc-recorder

/usr/share/bigbluebutton/html5-client/private/config/settings.yml (HTML5 client)
/etc/bigbluebutton/bbb-html5.yml (HTML5 client config override)
                             build: 1256
                        kurentoUrl: wss://192.168.50.50/bbb-webrtc-sfu
            defaultFullAudioBridge: fullaudio
           defaultListenOnlyBridge: fullaudio
                    sipjsHackViaWs: false


# Potential problems described below

# Warning: You have this server defined for https, but in
#
#   /usr/share/bigbluebutton/nginx/sip.nginx
#
#  did not find the use of https in definition for proxy_pass
#
#            proxy_pass http://192.168.87.129:5066;
#

# Warning: You have this server defined for https, but in
#
#   /usr/share/bigbluebutton/nginx/sip.nginx
#
#  did not find the use of port 7443 in definition for proxy_pass
#
#            proxy_pass http://192.168.87.129:5066;
#


Jean Pluzo

unread,
Jun 3, 2025, 3:18:33 AM6/3/25
to BigBlueButton-Setup
Hi,

the way I solved this problem (since it came up now and then wehn doing an update) was to edit the sip.nginx file and adding an 's' to http, as well as changing the port to 7443.
It might solve your problem but no guarantee!
If it does solve your problem please update us.

Regards,
J.
Reply all
Reply to author
Forward
0 new messages