New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
Sign in
to your account
Closed
manggiardi opened this issue
May 15, 2019
· 9 comments
Comments
I installed BBB behind NAT using the manual method because when I installed using the script, there was an error «bbb-install error: DNS lookup for resolved to but didn’t match local», then after I followed the steps to finish , webcam can’t share, error: Error on webcam sharing, and 1107 ICE negotiation failed in Firefox.
second problem, audio echo sometimes works, sometimes not (for chrome browsers), but for firefox it can’t be at all.
I already open all firewall ports
any suggestions for this case?
I’m using HTML5 Client
BigBlueButton Server 2.0.0 (1698)
Kernel version: 4.4.0-146-generic
Distribution: Ubuntu 16.04.6 LTS (64-bit)
Memory: 16169 MB
/var/www/bigbluebutton/client/conf/config.xml (bbb-client)
Port test (tunnel): rtmp://bbb.hostname.com
red5: bbb.hostname.com
useWebrtcIfAvailable: true
/opt/freeswitch/etc/freeswitch/sip_profiles/external.xml (FreeSWITCH)
websocket: 103.78.26.76:7443
WebRTC enabled: true
/etc/nginx/sites-available/bigbluebutton (nginx)
server name: bbb.hostname.com
port: 80, [::]:80
port: 443 ssl
bbb-client dir: /var/www/bigbluebutton
/var/lib/tomcat7/webapps/bigbluebutton/WEB-INF/classes/bigbluebutton.properties (bbb-web)
bbb-web host: bbb.hostname.com
/var/lib/tomcat7/webapps/demo/bbb_api_conf.jsp (API demos)
url: bbb.hostname.com
/var/www/bigbluebutton/check/conf/config.xml (client check)
client check: bbb.hostname.com
/usr/share/red5/webapps/bigbluebutton/WEB-INF/red5-web.xml (red5)
voice conference: FreeSWITCH
/usr/local/bigbluebutton/core/scripts/bigbluebutton.yml (record and playback)
playback host: bbb.hostname.com
ffmpeg: 4.1.3-0york1~16.04
/usr/local/bigbluebutton/bbb-webrtc-sfu/config/default.yml (Kurento)
kurentoUrl: ws://bbb.hostname.com:8888/kurento
kurentoIp: (external IP)
localIpAddress: 10.10.12.10
recordScreenSharing: true
recordWebcams: true
Node: v8.16.0
mongoDB: v3.4.20
'
The —check output is missing the bottom part. I would also recommend installing BBB 2.2-beta instead of 2.0 if your primary focus is the HTML5 client (http://docs.bigbluebutton.org/2.2/install.html). Another potential issue is the SSL certificate if you’re using a self-signed certificate instead one from a trusted CA. A self-signed certificate will cause issues with some of the components.
Thanks capilkey for your reply
I generate SSL cert using Let’s encrypt.
audio echo resolved using https://groups.google.com/forum/#!msg/bigbluebutton-setup/cw4v1DK-xzY/NI2xnR1nGwAJ
but webcam still problem
** Potential problems described below **
# IP does not match:
# IP from ifconfig: 10.10.12.10
# /etc/nginx/sites-available/bigbluebutton: vc.xxx.id
# Warning: API URL IPs do not match host:
#
# IP from ifconfig: 10.10.12.10
# /var/lib/tomcat7/webapps/demo/bbb_api_conf.jsp: vc.xxx.id
# Warning: The setting of x.x.x.x for proxy_pass in
#
# /etc/bigbluebutton/nginx/sip.nginx
#
# does not match the local IP address (10.10.12.10).
# (This is OK if you've manually changed the values)
# Warning: The API demos are installed and accessible from:
#
# https://vc.xxx.id/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
# Warning: The client self check is installed and accessible from:
#
# https://vc.xxx.id/check
#
The likely cause is that the candidates being sent for the webcam connection can’t be reached. The interesting thing is that Kurento is usually more permissive than the FreeSWITCH is. Try to share your webcam in Firefox and after it fails check the browser console for errors, You can also open a tab to «about:webrtc» and check the candidates that are tried.
@manggiardi Your server is behind NAT so Kurento needs a STUN server to gather valid candidates. Did you setup a STUN server for Kurento to use in /etc/kurento/modules/kurento/WebRtcEndpoint.conf.ini
? If not, try it. If it still doesn’t work, please attach a dump of about:webrtc and/or (preferably) chrome://webrtc-internals.
Before I configure NAT on my ubuntu with iptables -t nat -A POSTROUTING -p udp —match multiport —sports 16384:32768 -s 10.10.12.10 -j SNAT —to-source 103.78.26.76.
Webcam (Failed) :
SDP
Local SDP (Offer)
v=0
o=mozilla...THIS_IS_SDPARTA-66.0.4 2470052438303504604 0 IN IP4 0.0.0.0
s=-
t=0 0
a=sendrecv
a=fingerprint:sha-256 D9:BC:31:C9:BE:B8:E9:6A:78:26:BF:17:EB:C1:A5:95:52:48:EE:19:D2:ED:C7:1C:90:E8:1F:16:07:DE:43:CF
a=group:BUNDLE 0
a=ice-options:trickle
a=msid-semantic:WMS *
m=video 49178 UDP/TLS/RTP/SAVPF 120 121 126 97
c=IN IP4 202.158.69.122
a=candidate:0 1 UDP 2122252543 192.168.0.119 49178 typ host
a=candidate:2 1 TCP 2105524479 192.168.0.119 9 typ host tcptype active
a=candidate:0 2 UDP 2122252542 192.168.0.119 52027 typ host
a=candidate:2 2 TCP 2105524478 192.168.0.119 9 typ host tcptype active
a=candidate:1 1 UDP 1686052863 202.158.69.122 49178 typ srflx raddr 192.168.0.119 rport 49178
a=candidate:1 2 UDP 1686052862 202.158.69.122 52027 typ srflx raddr 192.168.0.119 rport 52027
a=sendonly
a=end-of-candidates
a=extmap:3 urn:ietf:params:rtp-hdrext:sdes:mid
a=extmap:4 http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time
a=extmap:5 urn:ietf:params:rtp-hdrext:toffset
a=fmtp:126 profile-level-id=42e01f;level-asymmetry-allowed=1;packetization-mode=1
a=fmtp:97 profile-level-id=42e01f;level-asymmetry-allowed=1
a=fmtp:120 max-fs=12288;max-fr=60
a=fmtp:121 max-fs=12288;max-fr=60
a=ice-pwd:8962d343c316171f3ce42857883b59bb
a=ice-ufrag:cf66069c
a=mid:0
a=msid:{bb8d5b4f-12ad-fb4d-9b0d-ae1aa26ab6d5} {a4b7dab9-a436-804a-9935-8d44fe0591ea}
a=rtcp:52027 IN IP4 192.168.0.119
a=rtcp-fb:120 nack
a=rtcp-fb:120 nack pli
a=rtcp-fb:120 ccm fir
a=rtcp-fb:120 goog-remb
a=rtcp-fb:121 nack
a=rtcp-fb:121 nack pli
a=rtcp-fb:121 ccm fir
a=rtcp-fb:121 goog-remb
a=rtcp-fb:126 nack
a=rtcp-fb:126 nack pli
a=rtcp-fb:126 ccm fir
a=rtcp-fb:126 goog-remb
a=rtcp-fb:97 nack
a=rtcp-fb:97 nack pli
a=rtcp-fb:97 ccm fir
a=rtcp-fb:97 goog-remb
a=rtcp-mux
a=rtpmap:120 VP8/90000
a=rtpmap:121 VP9/90000
a=rtpmap:126 H264/90000
a=rtpmap:97 H264/90000
a=setup:actpass
a=ssrc:3450890513 cname:{3228c32a-b011-304b-95e2-4afc7f8b056b}
Remote SDP (Answer)
v=0
o=- 3767052248 3767052248 IN IP4 0.0.0.0
s=-
t=0 0
a=sendrecv
a=fingerprint:sha-256 D9:BC:31:C9:BE:B8:E9:6A:78:26:BF:17:EB:C1:A5:95:52:48:EE:19:D2:ED:C7:1C:90:E8:1F:16:07:DE:43:CF
a=group:BUNDLE 0
a=ice-options:trickle
a=msid-semantic:WMS *
m=video 1 UDP/TLS/RTP/SAVPF 120
c=IN IP4 0.0.0.0
b=AS:300
b=TIAS:300000
a=candidate:1 1 UDP 2013266431 fe80::9657:a5ff:fe58:8128 27528 typ host
a=candidate:2 1 TCP 1015023103 fe80::9657:a5ff:fe58:8128 9 typ host tcptype active
a=candidate:3 1 TCP 1010828799 fe80::9657:a5ff:fe58:8128 27765 typ host tcptype passive
a=candidate:4 1 UDP 2013266430 10.10.12.10 28255 typ host
a=candidate:5 1 TCP 1015022079 10.10.12.10 9 typ host tcptype active
a=candidate:6 1 TCP 1010827775 10.10.12.10 31934 typ host tcptype passive
a=candidate:1 2 UDP 2013266430 fe80::9657:a5ff:fe58:8128 32197 typ host
a=candidate:2 2 TCP 1015023102 fe80::9657:a5ff:fe58:8128 9 typ host tcptype active
a=candidate:3 2 TCP 1010828798 fe80::9657:a5ff:fe58:8128 25473 typ host tcptype passive
a=candidate:4 2 UDP 2013266429 10.10.12.10 25730 typ host
a=candidate:5 2 TCP 1015022078 10.10.12.10 9 typ host tcptype active
a=candidate:6 2 TCP 1010827774 10.10.12.10 28921 typ host tcptype passive
a=candidate:7 1 UDP 1677722111 103.78.26.75 28255 typ srflx raddr 10.10.12.10 rport 28255
a=candidate:8 1 TCP 847249919 103.78.26.75 9 typ srflx raddr 10.10.12.10 rport 9 tcptype active
a=candidate:9 1 TCP 843055615 103.78.26.75 31934 typ srflx raddr 10.10.12.10 rport 31934 tcptype passive
a=recvonly
a=extmap:4 http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time
a=fingerprint:sha-256 9C:F7:62:B9:2D:7D:77:22:5B:78:A4:B1:46:BD:17:4D:FA:74:5D:71:AD:D3:2D:4C:BB:7F:3B:F4:16:9D:FE:6C
a=fmtp:120 max-fs=12288;max-fr=60
a=ice-pwd:DEvMckjzYLLoASzHL65GW5
a=ice-ufrag:eM++
a=mid:0
a=rtcp:9 IN IP4 0.0.0.0
a=rtcp-fb:120 nack
a=rtcp-fb:120 nack pli
a=rtcp-fb:120 ccm fir
a=rtcp-fb:120 goog-remb
a=rtcp-mux
a=rtpmap:120 VP8/90000
a=setup:active
a=ssrc:4242259379 cname:user3374002973@host-851adecc
RTP Stats
outbound_rtcp_video_0
Local: 10:24:21 GMT+0700 (Western Indonesia Time) remote-inbound-rtp SSRC: 3450890513
outbound_rtp_video_0
Local: 10:24:21 GMT+0700 (Western Indonesia Time) outbound-rtp SSRC: 3450890513
Audio (Failed):
SDP
Local SDP (Offer)
v=0
o=mozilla...THIS_IS_SDPARTA-66.0.4 6883034204585101738 0 IN IP4 0.0.0.0
s=-
t=0 0
a=sendrecv
a=fingerprint:sha-256 88:76:28:BD:77:BF:37:54:E9:ED:2E:DF:CD:CE:40:49:3A:17:3F:13:74:72:BC:EC:C1:B3:89:5F:5D:B3:AC:37
a=group:BUNDLE 0 1
a=ice-options:trickle
a=msid-semantic:WMS *
m=audio 61859 UDP/TLS/RTP/SAVPF 109 9 0 8 101
c=IN IP4 202.158.69.122
a=candidate:0 1 UDP 2122252543 192.168.0.119 61859 typ host
a=candidate:2 1 TCP 2105524479 192.168.0.119 9 typ host tcptype active
a=candidate:0 2 UDP 2122252542 192.168.0.119 52441 typ host
a=candidate:2 2 TCP 2105524478 192.168.0.119 9 typ host tcptype active
a=candidate:1 1 UDP 1686052863 202.158.69.122 61859 typ srflx raddr 192.168.0.119 rport 61859
a=candidate:1 2 UDP 1686052862 202.158.69.122 52441 typ srflx raddr 192.168.0.119 rport 52441
a=sendrecv
a=end-of-candidates
a=extmap:1 urn:ietf:params:rtp-hdrext:ssrc-audio-level
a=extmap:2/recvonly urn:ietf:params:rtp-hdrext:csrc-audio-level
a=extmap:3 urn:ietf:params:rtp-hdrext:sdes:mid
a=fmtp:109 maxplaybackrate=48000;stereo=1;useinbandfec=1
a=fmtp:101 0-15
a=ice-pwd:8f5f0fcc40e8c9fe81cd601f4135d4be
a=ice-ufrag:af4eb623
a=mid:0
a=msid:{f942e6fa-06c3-df42-a746-df5023d6c920} {77f7e203-ec1e-2448-ab4c-9bddab5e3337}
a=rtcp:52441 IN IP4 202.158.69.122
a=rtcp-mux
a=rtpmap:109 opus/48000/2
a=rtpmap:9 G722/8000/1
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=setup:actpass
a=ssrc:1531806075 cname:{5d281b52-fe88-b74e-9119-7fdb395af162}
m=audio 0 UDP/TLS/RTP/SAVPF 109 9 0 8 101
c=IN IP4 0.0.0.0
a=bundle-only
a=sendrecv
a=extmap:1 urn:ietf:params:rtp-hdrext:ssrc-audio-level
a=extmap:2/recvonly urn:ietf:params:rtp-hdrext:csrc-audio-level
a=extmap:3 urn:ietf:params:rtp-hdrext:sdes:mid
a=fmtp:109 maxplaybackrate=48000;stereo=1;useinbandfec=1
a=fmtp:101 0-15
a=ice-pwd:8f5f0fcc40e8c9fe81cd601f4135d4be
a=ice-ufrag:af4eb623
a=mid:1
a=msid:- {44b5d3b1-0c0a-dd40-9038-9d3380ad2823}
a=rtcp-mux
a=rtpmap:109 opus/48000/2
a=rtpmap:9 G722/8000/1
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=setup:actpass
a=ssrc:2278076372 cname:{5d281b52-fe88-b74e-9119-7fdb395af162}
Remote SDP (Answer)
v=0
o=FreeSWITCH 1558041558 1558041559 IN IP4 103.78.26.76
s=-
t=0 0
a=sendrecv
a=msid-semantic:WMS wAQfPSn3LsPnyZfk0uZ2PXDIq3zG2cHp
m=audio 21808 RTP/SAVPF 109 101
c=IN IP4 103.78.26.76
a=candidate:1711230016 1 udp 659136 103.78.26.76 21808 typ host generation 0
a=sendrecv
a=end-of-candidates
a=fingerprint:sha-256 94:E9:A4:DC:E6:C5:F7:26:3F:74:B7:05:50:0D:28:92:43:CE:DD:5E:86:48:E6:D3:B2:E9:9C:00:C1:57:D2:BD
a=fmtp:109 maxplaybackrate=0;stereo=1;useinbandfec=0
a=ice-pwd:KgDGOFeGnZWUQmi1ByRDhhWT
a=ice-ufrag:kpp0cSzsMZZF2xUv
a=ptime:20
a=rtcp:21808 IN IP4 103.78.26.76
a=rtcp-mux
a=rtpmap:109 opus/48000/2
a=rtpmap:101 telephone-event/8000
a=setup:active
a=ssrc:3034761166 cname:Dnvi5IcH1RVpH0zx
a=ssrc:3034761166 msid:wAQfPSn3LsPnyZfk0uZ2PXDIq3zG2cHp a0
a=ssrc:3034761166 mslabel:wAQfPSn3LsPnyZfk0uZ2PXDIq3zG2cHp
a=ssrc:3034761166 label:wAQfPSn3LsPnyZfk0uZ2PXDIq3zG2cHpa0
m=audio 0 RTP/SAVPF 19
c=IN IP4 103.78.26.76
a=sendrecv
RTP Stats
inbound_rtp_audio_1
Local: 10:23:13 GMT+0700 (Western Indonesia Time) inbound-rtp SSRC: 3034761166
outbound_rtp_audio_0
Local: 10:23:13 GMT+0700 (Western Indonesia Time) outbound-rtp SSRC: 1531806075
After I configure NAT :
Webcam (Failed ):
SDP
Local SDP (Offer)
v=0
o=mozilla...THIS_IS_SDPARTA-66.0.4 398510380721091314 0 IN IP4 0.0.0.0
s=-
t=0 0
a=sendrecv
a=fingerprint:sha-256 9F:C2:1B:8B:9B:06:AD:E6:AC:F5:40:3E:C5:D5:38:E2:DE:98:EC:B4:D5:63:F9:D3:47:BF:53:7C:7F:23:4F:99
a=group:BUNDLE 0
a=ice-options:trickle
a=msid-semantic:WMS *
m=video 54459 UDP/TLS/RTP/SAVPF 120 121 126 97
c=IN IP4 202.158.69.122
a=candidate:0 1 UDP 2122252543 192.168.0.119 54459 typ host
a=candidate:2 1 TCP 2105524479 192.168.0.119 9 typ host tcptype active
a=candidate:0 2 UDP 2122252542 192.168.0.119 64399 typ host
a=candidate:2 2 TCP 2105524478 192.168.0.119 9 typ host tcptype active
a=candidate:1 1 UDP 1686052863 202.158.69.122 54459 typ srflx raddr 192.168.0.119 rport 54459
a=candidate:1 2 UDP 1686052862 202.158.69.122 64399 typ srflx raddr 192.168.0.119 rport 64399
a=sendonly
a=end-of-candidates
a=extmap:3 urn:ietf:params:rtp-hdrext:sdes:mid
a=extmap:4 http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time
a=extmap:5 urn:ietf:params:rtp-hdrext:toffset
a=fmtp:126 profile-level-id=42e01f;level-asymmetry-allowed=1;packetization-mode=1
a=fmtp:97 profile-level-id=42e01f;level-asymmetry-allowed=1
a=fmtp:120 max-fs=12288;max-fr=60
a=fmtp:121 max-fs=12288;max-fr=60
a=ice-pwd:398f38775a5957af8e6cd00745ca131e
a=ice-ufrag:c1cd067c
a=mid:0
a=msid:{a6e3a69c-7ee5-6e45-bfa8-053ecbf78802} {87f1d0a9-0752-ce47-a466-00ddd6d63157}
a=rtcp:64399 IN IP4 192.168.0.119
a=rtcp-fb:120 nack
a=rtcp-fb:120 nack pli
a=rtcp-fb:120 ccm fir
a=rtcp-fb:120 goog-remb
a=rtcp-fb:121 nack
a=rtcp-fb:121 nack pli
a=rtcp-fb:121 ccm fir
a=rtcp-fb:121 goog-remb
a=rtcp-fb:126 nack
a=rtcp-fb:126 nack pli
a=rtcp-fb:126 ccm fir
a=rtcp-fb:126 goog-remb
a=rtcp-fb:97 nack
a=rtcp-fb:97 nack pli
a=rtcp-fb:97 ccm fir
a=rtcp-fb:97 goog-remb
a=rtcp-mux
a=rtpmap:120 VP8/90000
a=rtpmap:121 VP9/90000
a=rtpmap:126 H264/90000
a=rtpmap:97 H264/90000
a=setup:actpass
a=ssrc:439366203 cname:{e09d5e80-e9d9-df47-8430-67b969950fe8}
Remote SDP (Answer)
v=0
o=- 3767051665 3767051665 IN IP4 0.0.0.0
s=-
t=0 0
a=sendrecv
a=fingerprint:sha-256 9F:C2:1B:8B:9B:06:AD:E6:AC:F5:40:3E:C5:D5:38:E2:DE:98:EC:B4:D5:63:F9:D3:47:BF:53:7C:7F:23:4F:99
a=group:BUNDLE 0
a=ice-options:trickle
a=msid-semantic:WMS *
m=video 1 UDP/TLS/RTP/SAVPF 120
c=IN IP4 0.0.0.0
b=AS:300
b=TIAS:300000
a=candidate:1 1 UDP 2013266431 fe80::9657:a5ff:fe58:8128 25934 typ host
a=candidate:2 1 TCP 1015023103 fe80::9657:a5ff:fe58:8128 9 typ host tcptype active
a=candidate:3 1 TCP 1010828799 fe80::9657:a5ff:fe58:8128 31726 typ host tcptype passive
a=candidate:4 1 UDP 2013266430 10.10.12.10 27180 typ host
a=candidate:5 1 TCP 1015022079 10.10.12.10 9 typ host tcptype active
a=candidate:6 1 TCP 1010827775 10.10.12.10 27144 typ host tcptype passive
a=candidate:1 2 UDP 2013266430 fe80::9657:a5ff:fe58:8128 27446 typ host
a=candidate:2 2 TCP 1015023102 fe80::9657:a5ff:fe58:8128 9 typ host tcptype active
a=candidate:3 2 TCP 1010828798 fe80::9657:a5ff:fe58:8128 31742 typ host tcptype passive
a=candidate:4 2 UDP 2013266429 10.10.12.10 31118 typ host
a=candidate:5 2 TCP 1015022078 10.10.12.10 9 typ host tcptype active
a=candidate:6 2 TCP 1010827774 10.10.12.10 28305 typ host tcptype passive
a=recvonly
a=extmap:4 http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time
a=fingerprint:sha-256 9C:F7:62:B9:2D:7D:77:22:5B:78:A4:B1:46:BD:17:4D:FA:74:5D:71:AD:D3:2D:4C:BB:7F:3B:F4:16:9D:FE:6C
a=fmtp:120 max-fs=12288;max-fr=60
a=ice-pwd:U67wFP6VCTOVvUkprGB22c
a=ice-ufrag:c07A
a=mid:0
a=rtcp:9 IN IP4 0.0.0.0
a=rtcp-fb:120 nack
a=rtcp-fb:120 nack pli
a=rtcp-fb:120 ccm fir
a=rtcp-fb:120 goog-remb
a=rtcp-mux
a=rtpmap:120 VP8/90000
a=setup:active
a=ssrc:2502884274 cname:user3031769634@host-7c574a45
RTP Stats
outbound_rtcp_video_0
Local: 10:14:38 GMT+0700 (Western Indonesia Time) remote-inbound-rtp SSRC: 439366203
outbound_rtp_video_0
Local: 10:14:38 GMT+0700 (Western Indonesia Time) outbound-rtp SSRC: 439366203
Audio Echo (Success):
SDP
Local SDP (Offer)
v=0
o=mozilla...THIS_IS_SDPARTA-66.0.4 6797297505337959408 0 IN IP4 0.0.0.0
s=-
t=0 0
a=sendrecv
a=fingerprint:sha-256 3C:47:75:C9:CB:78:D7:6C:82:B1:3C:6D:8F:66:68:7E:1A:50:D6:50:3F:57:85:FF:35:0B:1D:55:61:E8:84:42
a=group:BUNDLE 0 1
a=ice-options:trickle
a=msid-semantic:WMS *
m=audio 64849 UDP/TLS/RTP/SAVPF 109 9 0 8 101
c=IN IP4 202.158.69.122
a=candidate:0 1 UDP 2122252543 192.168.0.119 64849 typ host
a=candidate:2 1 TCP 2105524479 192.168.0.119 9 typ host tcptype active
a=candidate:0 2 UDP 2122252542 192.168.0.119 49608 typ host
a=candidate:2 2 TCP 2105524478 192.168.0.119 9 typ host tcptype active
a=candidate:1 1 UDP 1686052863 202.158.69.122 64849 typ srflx raddr 192.168.0.119 rport 64849
a=candidate:1 2 UDP 1686052862 202.158.69.122 49608 typ srflx raddr 192.168.0.119 rport 49608
a=sendrecv
a=end-of-candidates
a=extmap:1 urn:ietf:params:rtp-hdrext:ssrc-audio-level
a=extmap:2/recvonly urn:ietf:params:rtp-hdrext:csrc-audio-level
a=extmap:3 urn:ietf:params:rtp-hdrext:sdes:mid
a=fmtp:109 maxplaybackrate=48000;stereo=1;useinbandfec=1
a=fmtp:101 0-15
a=ice-pwd:1659c17134d3088ae5976bfdd7a3a077
a=ice-ufrag:74cbb03f
a=mid:0
a=msid:{03321227-e716-2440-bf71-669854c356b4} {bb76f614-75f0-e94d-8e2c-6f5dee64dfb7}
a=rtcp:49608 IN IP4 202.158.69.122
a=rtcp-mux
a=rtpmap:109 opus/48000/2
a=rtpmap:9 G722/8000/1
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=setup:actpass
a=ssrc:4294094465 cname:{e843dee7-ba06-4d4c-b70d-7b85a169cb35}
m=audio 0 UDP/TLS/RTP/SAVPF 109 9 0 8 101
c=IN IP4 0.0.0.0
a=bundle-only
a=sendrecv
a=extmap:1 urn:ietf:params:rtp-hdrext:ssrc-audio-level
a=extmap:2/recvonly urn:ietf:params:rtp-hdrext:csrc-audio-level
a=extmap:3 urn:ietf:params:rtp-hdrext:sdes:mid
a=fmtp:109 maxplaybackrate=48000;stereo=1;useinbandfec=1
a=fmtp:101 0-15
a=ice-pwd:1659c17134d3088ae5976bfdd7a3a077
a=ice-ufrag:74cbb03f
a=mid:1
a=msid:- {8ea2783d-412a-004d-bcd1-863f3c76a4fc}
a=rtcp-mux
a=rtpmap:109 opus/48000/2
a=rtpmap:9 G722/8000/1
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=setup:actpass
a=ssrc:97475070 cname:{e843dee7-ba06-4d4c-b70d-7b85a169cb35}
Remote SDP (Answer)
v=0
o=FreeSWITCH 1558042280 1558042281 IN IP4 103.78.26.76
s=-
t=0 0
a=sendrecv
a=msid-semantic:WMS lbK0CeECblVmlYakoYprP0DKBK9dB7sN
m=audio 20552 RTP/SAVPF 109 101
c=IN IP4 103.78.26.76
a=candidate:0622446502 1 udp 659136 103.78.26.76 20552 typ host generation 0
a=sendrecv
a=end-of-candidates
a=fingerprint:sha-256 94:E9:A4:DC:E6:C5:F7:26:3F:74:B7:05:50:0D:28:92:43:CE:DD:5E:86:48:E6:D3:B2:E9:9C:00:C1:57:D2:BD
a=fmtp:109 maxplaybackrate=0;stereo=1;useinbandfec=0
a=ice-pwd:rLMoKFnUkyfNJKvKwvp7YFb1
a=ice-ufrag:aV9PLDpddphEmzhl
a=ptime:20
a=rtcp:20552 IN IP4 103.78.26.76
a=rtcp-mux
a=rtpmap:109 opus/48000/2
a=rtpmap:101 telephone-event/8000
a=setup:active
a=ssrc:3034936904 cname:82DA6838jOlvDlFS
a=ssrc:3034936904 msid:lbK0CeECblVmlYakoYprP0DKBK9dB7sN a0
a=ssrc:3034936904 mslabel:lbK0CeECblVmlYakoYprP0DKBK9dB7sN
a=ssrc:3034936904 label:lbK0CeECblVmlYakoYprP0DKBK9dB7sNa0
m=audio 0 RTP/SAVPF 19
c=IN IP4 103.78.26.76
a=sendrecv
RTP Stats
outbound_rtcp_audio_0
Local: 10:16:34 GMT+0700 (Western Indonesia Time) remote-inbound-rtp SSRC: 4294094465 Received: 7244 packets (1139.08 Kb) Lost: 4 Jitter: 0 RTT: 30 ms
inbound_rtp_audio_1
Local: 10:16:34 GMT+0700 (Western Indonesia Time) inbound-rtp SSRC: 3034936904 Received: 7314 packets (192.88 Kb) Lost: 12 Jitter: 0.003
outbound_rtp_audio_0
Local: 10:16:34 GMT+0700 (Western Indonesia Time) outbound-rtp SSRC: 4294094465 Sent: 7322 packets (1237.15 Kb)
inbound_rtcp_audio_1
Local: 10:16:34 GMT+0700 (Western Indonesia Time) remote-outbound-rtp SSRC: 3034936904 Sent: 7279 packets (176.95 Kb)
seems stun not working ?
Did you setup the STUN server in the server-side file I mentioned or not? The remote SDP for video does not have a valid public IP address for your server, so either you did not set the STUN up there or it’s not correctly set. See https://docs.bigbluebutton.org/html/html5-install.html section Extra steps when server is behind NAT
. Make sure the STUN server is on the network border. Also make sure you use its IP address in the config file, not the domain name. If you did configure it, please paste the file contents here.
You can test if the STUN server you’re using is working properly by using the stun-client
utilitary (found on apt
) on your server against the desired STUN server credentials.
I already setting up extra step with NAT.
;; STUN server
;; The ICE process uses STUN servers to punch holes through NAT firewalls.
;;
;; <IpAddress> MUST be an IP Address; domain names are NOT supported.
;;
;; You need to use a well-working STUN server. Use this to check if it works:
;; https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/
;; You should get at least one Server-Reflexive Candidate (type "srflx").
;;
stunServerAddress=203.183.172.196
stunServerPort=3478
;; TURN server
;; When STUN is not enough to open connections through some NAT firewalls,
;; using TURN is the remaining alternative.
;;
;; Note that TURN is a superset of STUN, so you don't strictly need to
;; configure STUN if you are going to use TURN.
;;
FInally I found the problem.
I have 4 Public IP on my router,
x.x.x.2
x.x.x.3
x.x.x.4
x.x.x.5
and default nat configuration on my router is on x.x.x.2, but I use x.x.x.3 for my BBB server. I already configure DST NAT for x.x.x.3 to my BBB local address, Until here, maybe BBB can be accessed, but I just realized that the inbound and outbound connections are different. this makes video sockets unable to run.
most NAT configurations on routers are only configuring Destination NAT without directing its Source NAT to Public IP, this doesn’t matter if the router has 1 public ip, but if the router has many Public IPs and each server has its own IP slot (like this case, ) , the Source NAT configuration must be added to the router they have (Not only DST NAT), while the routers in our client have no Source NAT configuration, so inbound and outbound connections are separated not through the same public ip, and BBB does not support this condition. then I add rules on the router so that the inbound and outbound connections through the same ip.
Hi
I had this error and I could resolve it. I write it’s solution here to help other people
It is related to Turn Server.
You can check bbb-conf --check
output. at the latest line, you can see this file in the Turn Server:
/etc/kurento/modules/kurento/WebRtcEndpoint.conf.ini
edit this file and check these values:
;networkInterfaces=eth0
;stunServerAddress=198.51.100.1
;stunServerPort=3478
;externalIPv4=198.51.100.1
;externalAddress=198.51.100.1
In addition, I recommend setup a dedicated Turn Server for yourself by this instruction. Don’t be afraid, It’s easy to set up!
Have a good time
Connection failure (ICE error 1107)
3-4 weeks ago, we could no longer share webcams using the BBB.
Tests have been conducted with students and teachers from office computers (wired Ethernet) and laptops connected with WiFi (eduroam). Tests have been conducted using mobile hotspot connections.
All tests resulted in the Connection failure (ICE error 1107) when trying to share webcams.
NOTE: BBB works OK at my home using a 5G router and a public IPv6 address.
https://groups.google.com/g/bigbluebutton-users/c/CCAa4G10cUA)
https://groups.google.com/g/bigbluebutton-users/c/HWP1-MSSIFs
I have sent a last round of emails to our service providers.
Possibilities:
a. A middle-box or server (BBB?) somewhere is not configured correctly for dual stack IPv4/IPv6.
b. Company X have misconfigured our firewall. (I doubt this is the case.)
c. Company Y have misconfigured the BBB server. (I doubt this is the case.)
d. A good old-fashioned bug in the version of BBB being used.
Andrew Brooks
Содержание
- Connection failure (ICE error 1107) 3-4 weeks ago, we could no longer share webcams using the BBB #14698
- Comments
- Footer
- ICE 1107 error with webcam on clean Ubuntu 20.04 due to libcurl3 / kurento / gstream error about bbb-install HOT 7 OPEN
- Comments (7)
- Related Issues (20)
- Recommend Projects
- React
- Vue.js
- Typescript
- TensorFlow
- Django
- Laravel
- Recommend Topics
- javascript
- server
- Machine learning
- Visualization
- Recommend Org
- Microsoft
- Big Blue Button
- Contents
- Configuring TURN
- Configuration
- Disable Echo Test
- Testing configuration
- Nextcloud integration
- Troubleshooting
- ICE error 1107, video not working
- Query String API
- Security
- Error 1107. not able to reconnect about bigbluebutton HOT 4 OPEN
- Comments (4)
- Related Issues (20)
- Recommend Projects
- React
- Vue.js
- Typescript
- TensorFlow
- Django
- Laravel
- Recommend Topics
- javascript
- server
- Machine learning
- Visualization
- Recommend Org
- Microsoft
Connection failure (ICE error 1107) 3-4 weeks ago, we could no longer share webcams using the BBB #14698
Connection failure (ICE error 1107)
3-4 weeks ago, we could no longer share webcams using the BBB.
Tests have been conducted with students and teachers from office computers (wired Ethernet) and laptops connected with WiFi (eduroam). Tests have been conducted using mobile hotspot connections.
All tests resulted in the Connection failure (ICE error 1107) when trying to share webcams.
NOTE: BBB works OK at my home using a 5G router and a public IPv6 address.
I have sent a last round of emails to our service providers.
Possibilities:
a. A middle-box or server (BBB?) somewhere is not configured correctly for dual stack IPv4/IPv6.
b. Company X have misconfigured our firewall. (I doubt this is the case.)
c. Company Y have misconfigured the BBB server. (I doubt this is the case.)
d. A good old-fashioned bug in the version of BBB being used.
The text was updated successfully, but these errors were encountered:
@AndrewBrooks56 have you set up your own coturn instance with TURN+STUN?
Review your server firewall policies, make sure your TURN instance is working.
I also suggest reviewing this checklist if you’re using Kurento as your media server:
- Add the networkInterfaces config option to your install scripts. It’s configured in /etc/kurento/modules/kurento/WebRtcEndpoint.conf.ini. You should set it to whichever is the default, public network interface in your server (in this case, ens2).
- If the NIF has unwanted IPs (ie private intranet IPs for VPS comms which are not used for media exchange), you can add them to ipIgnoreList
- Please set niceAgentIceTcp (/etc/kurento/modules/kurento/WebRtcEndpoint.conf.ini) to 0 if you’re not using TCP for media comm (that’s BBB’s default, so it can be set to 0)
- /etc/kurento/modules/kurento/WebRtcEndpoint.conf.ini -> Set externalIPv4 if your server is behind NAT
- /etc/kurento/modules/kurento/WebRtcEndpoint.conf.ini -> stunServerAddress/stunServerPort: this config is superseded by externalIPv4 the absolute majority of scenarios, so you don’t need to set it. Cases where you do need to set it is on premises deployments where you need media to work both over the intranet and the internet at the same time.
@henriquebol the described behavior is certainly not similar to the OP’s, so please try not to add noise to unrelated issues. I suggest going to the mailing lists first and preferably send relevant logs. For starters, look at #14198.
@AndrewBrooks56 now I see that you’re dealing with a BBB instance provided to you by a 3rd party, so most of things I sent might be a bit difficult to do if you’re not the administrator of the system.
Given the scenario, I’m closing the issue. Can we move the discussion back to the the mailing list topic Connection failure (ICE error 1107) in bbb-users? We can continue to engage there.
© 2023 GitHub, Inc.
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Источник
ICE 1107 error with webcam on clean Ubuntu 20.04 due to libcurl3 / kurento / gstream error about bbb-install HOT 7 OPEN
jona-es commented on January 15, 2023
I’m not sure if this is a general issue. @ffdixon is already involved.
I’ve tried to install it a few times, but I always face the same issue.
bpetit commented on January 15, 2023
It seems I have the exact same error, on
ffdixon commented on January 15, 2023
We just did a new install on Ubuntu 20.04 using Digital Ocean and it worked.
blank ubuntu 20.04 LTS system which runs as a virtual machine on ESXi
We’re thinking the issue is running it under ESXi. @bpetit Are you installing in this environment?
bpetit commented on January 15, 2023
I am. But it is a KVM host, not an ESXi one.
As a first guess, I’d say it would be interesting to look at the base VM images, rather than the VMM or hypervisor.
In my case this is an ubuntu 20.04 «minimal». Maybe «complete» ubuntu images already include what’s needed for bbb-install, which explains you get a clean installation ?
ffdixon commented on January 15, 2023
I would try the complete ubuntu images. We’re seeing no problem installing on Digital Ocean.
bpetit commented on January 15, 2023
I tried with the complete image, no good.
To better understand, what’s the exact version of ubuntu you had on DO ?
In the mean time I tried to identify the root cause. It seems that kurento media server, needs libcurl3 to start properly (at least in the version installed by bbb-install 2.5), while BBB needs libcurl4 (at least bbb-conf —check says so). The two are incompatible (from apt point of view) and libcurl3 is not available as a package in 20.04.5.
I managed to successfully start kurento media server, after having hackishly installed libcurl3 (and broke bbb as libcurl4 had to be removed). So it’s not satisfying at all, but it seems to indicate that libcurl3 vs libcurl4 is root problem.
Did you have libcurl3 still on your ubuntu VM ? I wonder what was the difference.
- Error running wget -qO- command https://ubuntu.bigbluebutton.org/bbb-install.sh | bash -s — -v bionic-240 -s bbb.example.com -e [email protected] -a -w HOT 5
- Test installation HOT 3
- Check for Apache’s installation should be a warning HOT 1
- Enable HSTS on https installations
- Enable X-Content-Type-Options
- ./bbb-install-2.5.sh: line 209: [: missing `]’ HOT 1
- bbb-install for 2.5 messes up greenlight HOT 2
- Websocket Error with bigbluebutton code#1002 HOT 2
- certbot not renewing on 2.6 install due to nginx directory change HOT 1
- problem with installation: Depends: bbb-config but it is not going to be installed
- Add an option to install webhooks HOT 2
- don’t set PROXY PORT HOT 1
- Improve NAT configuration HOT 1
- issue with installing turn server HOT 1
- Sanity check for `-d` (/local/certs/)
- BigBlueButton errors 1107
- [2.6-beta3] Installation script does not respect -p option HOT 2
- bbb-install.sh stuck during update HOT 4
- Ruby 2.5 fails rubygems-update on ubuntu 18.04.6 LTS HOT 3
Recommend Projects
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
TensorFlow
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
Recommend Topics
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
server
A server is a program made to process requests and deliver data to clients.
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Visualization
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Recommend Org
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Источник
Big Blue Button
This article or section is a stub. Stubs are articles that have not yet received substantial attention from the authors. They are short or insufficient pieces of information and require additions to further increase the article’s usefulness. The project values stubs as useful first steps toward complete articles.
|
Contents
Configuring TURN
Configuration
The configuration files can be found on the BBB Configuration page.
Disable Echo Test
Edit /etc/bigbluebutton/bbb-html5.yml — if this file does not exist then run:
Then edit the properties you want.
Testing configuration
Run the configuration test script to see some potential issues and solutions.
Nextcloud integration
BBB has a Nextcloud integration that makes organising calls much easier if you already use a Nextcloud instance. It adds a new icon on the taskbar (shown at the top of the image below) that takes you to a page where you can manage rooms. Each room can be configured with a lot of useful options such as automatic private rooms for your Nextcloud users. The room is entered by simply clicking the play button for the appropriate room. You can copy a link for inviting other users too.
Note that by default a room you create will not show up in the list for any of the other users in your Nextcloud. You need to add them as moderators and then click the share icon to the right of each moderator to make them all admins for the room.
Troubleshooting
ICE error 1107, video not working
After initial installation, room members couldn’t activate video, all getting Connection failed: ICE error 1107, which is a known issue in Github. This is most likely that UDP is not getting through to the server. You can test UDP as follows:
On the target machine being tested:
And on the machine sending the tests:
Then type text and hit enter, it should be echoed on the server.
If it’s not, check the firewall status and disable:
If you still are having issues, setup a TURN server which should significantly improve reliability.
Query String API
Security
You will need access to the shared secret in BBB’s configuration:
Источник
Error 1107. not able to reconnect about bigbluebutton HOT 4 OPEN
Could you upgrade to 2.4.5 (the latest release at the time of this writing) and let us know if you still encounter the same issues.
Braehler commented on January 15, 2023
@ffdixon
We jsut set up a new server based on the recomendation of the AX51 server on Hetzter and installed the latest 2.4.5 Version of BBB.
I´m now waiting for feedback of our teachers regarding the issue
ffdixon commented on January 15, 2023
Sounds good — let us know the results. Also, can you have users who are encountering the error test against https://test.bigbluebutton.org/.
ffdixon commented on January 15, 2023
In the future, please post to https://groups.google.com/g/bigbluebutton-setup and the community will help you there. If in helping we encounter a bug in BigBlueButton, we’ll open an issue here to track it.
- Adding Embed (Iframe) option HOT 1
- Adding Embed (iframe) option HOT 2
- Uncaught (in Promise) HOT 3
- Problem with Big Blue & cPanel on ubuntu 20.04 HOT 5
- Whiteboard cursor jumps up and down
- tldraw whiteboard does not display current tool
- Export breakout shared notes only if there is content inside
- Export breakout whiteboard only if it was used
- Make video pagination limits configurable by user HOT 1
- Can Spoken «You are Now Muted» / «You are Now Unmuted» Notifications be Per-User-Configurable, instead of Per-Server?
- Newly switched presentation shown differently to presenter
- Add settings.yml config for breakout auto export notes or whiteboard
- Sticky notes are giant on portrait view slides HOT 1
- [2.6] Custom background image not restored after returning from breakout room
- Missing tooltips from certain tldraw tools
- [2.6] Only moderators can change layout (regression from 2.5)
- [2.5/2.6] Mute users/unmute meeting UI has confusing behaviour HOT 1
- [2.6] poll results missing in exported presentation HOT 2
- [2.6] Whiteboard component crash HOT 1
- Chyron, Live Caption on web cams for context/background of speakers and attendees
Recommend Projects
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
TensorFlow
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
Recommend Topics
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
server
A server is a program made to process requests and deliver data to clients.
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Visualization
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Recommend Org
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Источник
Cheekian Tan
unread,
Jan 30, 2019, 11:50:46 AM1/30/19
to BigBlueButton-Setup
Hi, all. I just upgraded my BigBlueButton server from RC8 to RC10. My server has HTML5 installed and set to run by default. Before the upgrade, everything was fine, the audio, screenshare and video. After upgrade, I have Error 1107 ice negotiation failed when I tried to connect the microphone. Audio and screensharing are giving error without any error code. I tried accessing https://test.bigbluebutton.org with same network and computer, everything works fine. Any idea? Thanks.
Fred Dixon
unread,
Jan 30, 2019, 4:07:56 PM1/30/19
to BigBlueButton-.
> After upgrade, I have Error 1107 ice negotiation failed when I tried to connect the microphone. Audio and screensharing are giving error without any error code.
There is an upgrade to freeswitch in this release — did you previously make any changes to the FreeSWITCH configuration files (prior to upgrade)? Does
sudo bbb-conf —check
show any errors?
Regards,… Fred
Hi, all. I just upgraded my BigBlueButton server from RC8 to RC10. My server has HTML5 installed and set to run by default. Before the upgrade, everything was fine, the audio, screenshare and video. After upgrade, I have Error 1107 ice negotiation failed when I tried to connect the microphone. Audio and screensharing are giving error without any error code. I tried accessing https://test.bigbluebutton.org with same network and computer, everything works fine. Any idea? Thanks.
—
BigBlueButton Developer
@bigbluebutton
stepa…@gmail.com
unread,
Jan 30, 2019, 4:17:02 PM1/30/19
to BigBlueButton-Setup
Hello,
I have the same issues after upgrading to RC10 from previous version.
Here is the bbb check output.
BigBlueButton Server 2.0.0-RC10 (1662)
Kernel version: 4.4.0-141-generic
Distribution: Ubuntu 16.04.5 LTS (64-bit)
Memory: 82475 MB
/var/www/bigbluebutton/client/conf/config.xml (bbb-client)
useWebrtcIfAvailable: true
/opt/freeswitch/etc/freeswitch/sip_profiles/external.xml (FreeSWITCH)
WebRTC enabled: true
/etc/nginx/sites-available/bigbluebutton (nginx)
port: 80, [::]:80
port: 443 ssl
bbb-client dir: /var/www/bigbluebutton
/var/lib/tomcat7/webapps/bigbluebutton/WEB-INF/classes/bigbluebutton.properties (bbb-web)
/usr/share/red5/webapps/bigbluebutton/WEB-INF/red5-web.xml (red5)
voice conference: FreeSWITCH
/usr/local/bigbluebutton/core/scripts/bigbluebutton.yml (record and playback)
ffmpeg: 4.1-1~16.04.york0
/usr/bin/bbb-conf: line 1686: yq: command not found
/usr/bin/bbb-conf: line 1687: yq: command not found
/usr/bin/bbb-conf: line 1688: yq: command not found
/usr/bin/bbb-conf: line 1689: yq: command not found
/usr/bin/bbb-conf: line 1690: yq: command not found
/usr/local/bigbluebutton/bbb-webrtc-sfu/config/default.yml (Kurento)
kurentoUrl:
kurentoIp:
localIpAddress:
recordScreenSharing:
recordWebcams:
Node: v8.15.0
mongoDB: v3.4.19
** Potential problems described below **
# Warning: The setting of 77.158.7.70 for proxy_pass in
#
# /etc/bigbluebutton/nginx/sip.nginx
#
# does not match the local IP address
I haven’t made any changes since you helped me to make freeswitch to work.:
Thanks,
Fred Dixon
unread,
Jan 30, 2019, 4:44:44 PM1/30/19
to BigBlueButton-.
Hi Stephan,
You missed a step in the upgrade :-). Some packages now use yq to make it easier (and more deterministic) to update YAML files. You need to install a personal package archive (PPA) and do the apt-get update/apt-get dist-upgrade again. See
One of the packages that needs the command is bbb-webrtc-sfu. Without yq installed, apt-get won’t update the package and this is probably what’s causing the problem.
Try the above and let us know if the WebRTC audio and video now work again after the upgrade.
Regards,… Fred
stepa…@gmail.com
unread,
Jan 30, 2019, 6:28:26 PM1/30/19
to BigBlueButton-Setup
Same issue.
I checked also IP settings in the different conf file, and everything looks ok…
webmaster@EU-BBB:~$ sudo bbb-conf —check
BigBlueButton Server 2.0.0-RC10 (1666)
Kernel version: 4.4.0-141-generic
Distribution: Ubuntu 16.04.5 LTS (64-bit)
Memory: 82475 MB
/var/www/bigbluebutton/client/conf/config.xml (bbb-client)
useWebrtcIfAvailable: true
/opt/freeswitch/etc/freeswitch/sip_profiles/external.xml (FreeSWITCH)
WebRTC enabled: true
/etc/nginx/sites-available/bigbluebutton (nginx)
port: 80, [::]:80
port: 443 ssl
bbb-client dir: /var/www/bigbluebutton
/var/lib/tomcat7/webapps/bigbluebutton/WEB-INF/classes/bigbluebutton.properties (bbb-web)
/usr/share/red5/webapps/bigbluebutton/WEB-INF/red5-web.xml (red5)
voice conference: FreeSWITCH
/usr/local/bigbluebutton/core/scripts/bigbluebutton.yml (record and playback)
ffmpeg: 4.1-1~16.04.york0
/usr/local/bigbluebutton/bbb-webrtc-sfu/config/default.yml (Kurento)
kurentoIp: 192.168.13.25
localIpAddress: 192.168.13.25
recordScreenSharing: true
recordWebcams: true
Node: v8.15.0
mongoDB: v3.4.19
** Potential problems described below **
# Warning: The setting of 77.158.7.70 for proxy_pass in
#
# /etc/bigbluebutton/nginx/sip.nginx
#
# does not match the local IP address (192.168.13.25).
# (This is OK if you’ve manually changed the values)
Chad Pilkey
unread,
Jan 30, 2019, 8:29:09 PM1/30/19
to BigBlueButton-Setup
Are you trying to share audio or video? Also is there an error visible in the client?
stepa…@gmail.com
unread,
Jan 30, 2019, 8:58:27 PM1/30/19
to BigBlueButton-Setup
not on the client.
I have attached the console log but not seing something strange there…
webmeeting.stepaneurope.com-1548870937490.log
stepa…@gmail.com
unread,
Jan 30, 2019, 10:04:41 PM1/30/19
to BigBlueButton-Setup
I trying sharing audio. but video won’t work too..
Chad Pilkey
unread,
Jan 30, 2019, 11:40:28 PM1/30/19
to BigBlueButton-Setup
Let’s get audio working first and then deal with the video. I can see from the log that your server is sending a private IP for its candidate.
a=ice-pwd:Hlj5IVqWcysDtoglQTkLQ9Ev a=candidate:0123927270 1 udp 659136 192.168.13.25 19410 typ host generation 0 a=end-of-candidates
I think the problem is going to be related to the websocket binding in FreeSWITCH. We updated FreeSWITCH in the latest release candidate and it might have overwritten a customization in one of the configuration files. I would look for the wss-binding in /opt/freeswitch/conf/sip_profiles/external.xml. I’m going to guess that it might have a value of «:7443» and the problem will be resolved with it being changed to «<your_public_IP>:7443». You can also re-run the bbb-install script if you used that to install previously and give it the options used previously.
stepa…@gmail.com
unread,
Jan 31, 2019, 2:04:14 AM1/31/19
to BigBlueButton-Setup
Hi Chad,
Thanks for your suggestion, but the conf file already contained 77.158.7.70:7443
I gave a full restart to the server just in case, but the issue remain.
After reboot greenlight has stopped, is this a normal behavior?
stepa…@gmail.com
unread,
Jan 31, 2019, 2:33:04 AM1/31/19
to BigBlueButton-Setup
Fyi, The issue for audio is happening from internal and external networks
For greenlight.
webmaster@EU-BBB:~$ sudo docker run —rm —env-file env bigbluebutton/greenlight:v2 bundle exec rake conf:check
Checking environment: Passed
Checking Connection: Passed
Checking Secret: Passed
webmaster@EU-BBB:~$ systemctl restart nginx
webmaster@EU-BBB:~$ sudo docker run —restart unless-stopped -d -p 5000:80 -v $(pwd)/db/production:/usr/src/app/db/production —env-file env —name greenlight-v2 bigbluebutton/greenlight:v2
docker: Error response from daemon: Conflict. The container name «/greenlight-v2» is already in use by container «caa5c72d38e1c72ede90dd8f5f870659d245b0465a3b921a8166b884210fe9d8». You have to remove (or rename) that container to be able to reuse that name.
Still getting a 404 error when calling greenlight
bbb is running fine, I can create a meeting with API.
Fred Dixon
unread,
Jan 31, 2019, 6:21:47 AM1/31/19
to BigBlueButton-.
Hi Stephan,
Did you need to setup a dummy NIC before to get BigBlueButton audio working? See
If so, did you set the dummy NIC to be re-applied on restart? It might be that FreeSWITCH does not have the dummy NIC to bind to anymore. See the above section and go through the steps to confirm that FreeSWITCH is configured to work with NAT.
> docker: Error response from daemon: Conflict. The container name «/greenlight-v2» is already in use by container «caa5c72d38e1c72ede90dd8f5f870659d245b0465a3b921a8166b884210fe9d8». You have to remove (or rename) that container to be able to reuse that name.
This is the reason why you can’t run GreenLight. See
for steps to remove the old GreenLight and start with a new one.
Regards,… Fred
stepa…@gmail.com
unread,
Jan 31, 2019, 11:59:58 AM1/31/19
to BigBlueButton-Setup
Hi Fred,
The dummy NIC shoud have started automatically.
Here is the test.
curl —trace-ascii — -k https://77.158.7.70:443/bigbluebutton/api
== Info: Trying 77.158.7.70…
== Info: Connected to 77.158.7.70 (77.158.7.70) port 443 (#0)
== Info: found 148 certificates in /etc/ssl/certs/ca-certificates.crt
== Info: found 592 certificates in /etc/ssl/certs
== Info: ALPN, offering http/1.1
== Info: SSL connection using TLS1.2 / ECDHE_RSA_AES_128_GCM_SHA256
== Info: server certificate verification SKIPPED
== Info: server certificate status verification SKIPPED
== Info: common name: webmeeting.stepaneurope.com (does not match ‘77.158.7.70’)
== Info: server certificate expiration date OK
== Info: server certificate activation date OK
== Info: certificate public key: RSA
== Info: certificate version: #3
== Info: subject: CN=webmeeting.stepaneurope.com
== Info: start date: Thu, 29 Nov 2018 14:20:51 GMT
== Info: expire date: Wed, 27 Feb 2019 14:20:51 GMT
== Info: issuer: C=US,O=Let’s Encrypt,CN=Let’s Encrypt Authority X3
== Info: compression: NULL
== Info: ALPN, server accepted to use http/1.1
=> Send header, 92 bytes (0x5c)
0000: GET /bigbluebutton/api HTTP/1.1
0021: Host: 77.158.7.70
0034: User-Agent: curl/7.47.0
004d: Accept: */*
005a:
<= Recv header, 17 bytes (0x11)
0000: HTTP/1.1 200 OK
<= Recv header, 31 bytes (0x1f)
0000: Server: nginx/1.10.3 (Ubuntu)
<= Recv header, 37 bytes (0x25)
0000: Date: Thu, 31 Jan 2019 08:33:18 GMT
<= Recv header, 38 bytes (0x26)
0000: Content-Type: text/xml;charset=utf-8
<= Recv header, 28 bytes (0x1c)
0000: Transfer-Encoding: chunked
<= Recv header, 24 bytes (0x18)
0000: Connection: keep-alive
<= Recv header, 25 bytes (0x19)
0000: Cache-Control: no-cache
<= Recv header, 35 bytes (0x23)
0000: P3P: CP=»No P3P policy available»
<= Recv header, 2 bytes (0x2)
0000:
<= Recv data, 86 bytes (0x56)
0000: 4b
0004: <response><returncode>SUCCESS</returncode><version>2.0</version>
0044: </response>
0051: 0
0054:
<response><returncode>SUCCESS</returncode><version>2.0</version></response>== Info: Connection #0 to host 77.158.7.70 left intact
Greenlight it’s working now Thanks!
Do I have to do this everytime I reboot my server?
This article or section is a stub. Stubs are articles that have not yet received substantial attention from the authors. They are short or insufficient pieces of information and require additions to further increase the article’s usefulness. The project values stubs as useful first steps toward complete articles.
|
Contents
- 1 Configuring TURN
- 2 Configuration
- 2.1 Disable Echo Test
- 2.2 Testing configuration
- 3 Nextcloud integration
- 4 Troubleshooting
- 4.1 ICE error 1107, video not working
- 5 Query String API
- 5.1 Security
- 6 Resources
- 7 See also
Configuring TURN
- Setting up a TURN server
- https://docs.bigbluebutton.org/2.2/setup-turn-server.html#configure-bigbluebutton-to-use-your-turn-server
Configuration
The configuration files can be found on the BBB Configuration page.
Disable Echo Test
Edit /etc/bigbluebutton/bbb-html5.yml — if this file does not exist then run:
cp /usr/share/meteor/bundle/programs/server/assets/app/config/settings.yml /etc/bigbluebutton/bbb-html5.yml
Then edit the properties you want.
Testing configuration
Run the configuration test script to see some potential issues and solutions.
sudo bbb-conf --check
Nextcloud integration
BBB has a Nextcloud integration that makes organising calls much easier if you already use a Nextcloud instance. It adds a new icon on the taskbar (shown at the top of the image below) that takes you to a page where you can manage rooms. Each room can be configured with a lot of useful options such as automatic private rooms for your Nextcloud users. The room is entered by simply clicking the play button for the appropriate room. You can copy a link for inviting other users too.
Note that by default a room you create will not show up in the list for any of the other users in your Nextcloud. You need to add them as moderators and then click the share icon to the right of each moderator to make them all admins for the room.
Troubleshooting
ICE error 1107, video not working
After initial installation, room members couldn’t activate video, all getting Connection failed: ICE error 1107, which is a known issue in Github. This is most likely that UDP is not getting through to the server. You can test UDP as follows:
On the target machine being tested:
nc -ulp PORT
And on the machine sending the tests:
nc -u SERVER PORT
Then type text and hit enter, it should be echoed on the server.
If it’s not, check the firewall status and disable:
ufw status
ufw disable
If you still are having issues, setup a TURN server which should significantly improve reliability.
Query String API
Security
You will need access to the shared secret in BBB’s configuration:
- First prepend the name of the API call to the string to the query string (no ‘?’ at the start but ‘&’ between parameters).
- Secondly append the shared secret to the the end of the query string
- Hash the resulting string with SHA1
- Add checksum=<SHA1> to the original query string parameters.
- https://docs.bigbluebutton.org/dev/api.html#usage
Resources
- Installation of BBB 2.3 onto Ubuntu 18.04
- BBB 2.2 troubleshooting
See also
- Setting up a TURN server
- Jitsi
- Matrix
Connection failure (ICE error 1107) 3-4 weeks ago, we could no longer share webcams using the BBB #14698
Comments
AndrewBrooks56 commented Mar 30, 2022
Connection failure (ICE error 1107)
3-4 weeks ago, we could no longer share webcams using the BBB.
Tests have been conducted with students and teachers from office computers (wired Ethernet) and laptops connected with WiFi (eduroam). Tests have been conducted using mobile hotspot connections.
All tests resulted in the Connection failure (ICE error 1107) when trying to share webcams.
NOTE: BBB works OK at my home using a 5G router and a public IPv6 address.
I have sent a last round of emails to our service providers.
Possibilities:
a. A middle-box or server (BBB?) somewhere is not configured correctly for dual stack IPv4/IPv6.
b. Company X have misconfigured our firewall. (I doubt this is the case.)
c. Company Y have misconfigured the BBB server. (I doubt this is the case.)
d. A good old-fashioned bug in the version of BBB being used.
The text was updated successfully, but these errors were encountered:
prlanzarin commented Mar 31, 2022 •
@AndrewBrooks56 have you set up your own coturn instance with TURN+STUN?
Review your server firewall policies, make sure your TURN instance is working.
I also suggest reviewing this checklist if you’re using Kurento as your media server:
- Add the networkInterfaces config option to your install scripts. It’s configured in /etc/kurento/modules/kurento/WebRtcEndpoint.conf.ini. You should set it to whichever is the default, public network interface in your server (in this case, ens2).
- If the NIF has unwanted IPs (ie private intranet IPs for VPS comms which are not used for media exchange), you can add them to ipIgnoreList
- Please set niceAgentIceTcp (/etc/kurento/modules/kurento/WebRtcEndpoint.conf.ini) to 0 if you’re not using TCP for media comm (that’s BBB’s default, so it can be set to 0)
- /etc/kurento/modules/kurento/WebRtcEndpoint.conf.ini -> Set externalIPv4 if your server is behind NAT
- /etc/kurento/modules/kurento/WebRtcEndpoint.conf.ini -> stunServerAddress/stunServerPort: this config is superseded by externalIPv4 the absolute majority of scenarios, so you don’t need to set it. Cases where you do need to set it is on premises deployments where you need media to work both over the intranet and the internet at the same time.
@henriquebol the described behavior is certainly not similar to the OP’s, so please try not to add noise to unrelated issues. I suggest going to the mailing lists first and preferably send relevant logs. For starters, look at #14198.
prlanzarin commented Mar 31, 2022
@AndrewBrooks56 now I see that you’re dealing with a BBB instance provided to you by a 3rd party, so most of things I sent might be a bit difficult to do if you’re not the administrator of the system.
Given the scenario, I’m closing the issue. Can we move the discussion back to the the mailing list topic Connection failure (ICE error 1107) in bbb-users? We can continue to engage there.
Footer
© 2023 GitHub, Inc.
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Источник
Сетевая ошибка 1107 в Sony Bravia что делать
Современная бытовая техника дарит нам не только удовольствие и комфорт, но и причиняет некоторые неудобства, а именно возникновение различных сбоев в работе. К таким ситуациям, например, относится потеря интернет-соединения и появление на экране соответствующего сообщения. Сейчас мы обсудим, из-за чего возникает сетевая ошибка 1107 в Sony Bravia и что нужно делать, чтобы ее исправить. К сожалению, компания Sony не дает по этому поводу никаких комментариев, поэтому попробуем сделать все, что под силу обычному пользователю.
Выявляем причины сетевой ошибки
Причиной сетевой ошибки 1107, которая говорит о потере интернет-соединения, может быть сбой в работе самого телевизора либо серверов. Для начала следует обратиться в техническую поддержку и, подробно объяснив ситуацию, подождать официального ответа. Возможно, на сервере ведутся профилактические либо ремонтные работы и необходимо спокойно выждать какое-то время, чтобы вернуться к просмотру телевизора.
Так же желательно связаться с провайдером и узнать, имеются ли проблемы на их стороне. Если на серверах и у поставщика интернет-услуг все нормально, то, возможно, происходит сбой в работе самого гаджета или устройств, к нему подключенных. В наших силах произвести несколько действий по налаживанию работы телевизора Sony Bravia. Необходимо только внимательно следовать всем инструкциям.
Также может возникать ошибка в Sony Bravia с кодом 2200.
Пытаемся исправить ошибку 1107 в Sony Bravia
Для начала попробуем проверить работоспособность сетевого соединения, как рекомендует компания Sony на официальном сайте. Диагностику проводим в разделе “Справка” (Help), предварительно нажав на пульте ДУ кнопку Home.
Выбираем “Признаки интернет-соединения” (Internet Connectivity Symptoms) либо “Сеть” –> “ “Настройка и диагностика сетевых подключений” и диагностируем выход в сеть.
Результатом может быть как диагноз “Неисправно “ (Failed), так и “Все OK”. Если есть проблемы с интернет-соединением, то сначала пробуем просто обесточить и телевизор, и маршрутизатор. Через несколько минут проверяем работоспособность. Если сетевая ошибка 1107 на телевизоре Sony Bravia продолжает появляться и не дает подключиться к интернету, то, возможно, необходимо сделать одно или все из предложенных ниже действий:
- Обновить программное обеспечение телевизора.
- Вернуть телевизору заводские параметры.
- Ограничить количество подключенных к маршрутизатору гаджетов, так как это может тормозить работу интернета.
Указанные действия не помогли? Действуем следующим образом.
Изменяем настройки канала
Если мы получили ответ от техподдержки Sony либо своего провайдера о временных проблемах, то пробуем их обойти при помощи введения новых параметров для прокси. Для этого входим в настройки телевизора Sony Bravia и ищем раздел, в котором говорится о прокси. Затем действуем так:
- Открываем любой поисковик (Google, Яндекс) и набираем free proxy list.
- Мониторим первые сайты в выдаче и находим выложенные актуальные данные прокси.
- Применяем последние как новые точки доступа к сети. Там, где нужно будет указать свою страну, выбираем ту, где находимся (!).
- Обязательно сохраняем все данные и обновляемся.
Может быть, к некоторым приложениям доступ останется закрытым, в этом случае необходимо просто дождаться, когда наладится работа серверов или провайдер восстановит работу линии.
Блокировка IP
Так же причиной возникновения сетевой ошибки 1107 в ТВ Sony Bravia может быть деятельность Роскомнадзора, вызвавшая шумиху среди пользователей в последнее время. Если IP-адрес телевизора случайно попадет в списки подозрительных соединений, то в этом случае от наших действий ничего не зависит. Остается только ждать, пока IP разблокируют. Сейчас уже идут активные работы по восстановлению нормальной работы сервисов, случайно попавших под санкции, введенные против мессенджера Телеграм.
Меняем тип выхода в сеть
А что делать, если мы узнали об отсутствии проблем на серверах и со стороны провайдера? Значит, дело в нашем телевизоре либо устройствах, к нему подключенных. Если обычно мы используем подключение Sony Bravia к сети через Wi-Fi, то меняем тип выхода на кабель.
Причина в том, что кое-какие из обновлений не “дружат” с беспроводным соединением. После смены подключения на кабель начнется автозагрузка новых системных файлов. Ждем завершения процесса и для корректной установки обязательно перезагружаем телевизор Sony Bravia.
Общаемся на форумах
При возникновении любого рода ошибок полезно посещать тематические форумы и общаться с другими пользователями – возможно, кто-то уже разобрался с оптимальным решением сетевой ошибки 1107 в Sony Bravia и готов поделиться опытом. Также необходимо мониторить официальный сайт Sony (раздел “Поддержка по продуктам”) в поисках решения.
Источник
ICE 1107 error with webcam on clean Ubuntu 20.04 due to libcurl3 / kurento / gstream error about bbb-install HOT 7 OPEN
Comments (7)
jona-es commented on January 11, 2023
I’m not sure if this is a general issue. @ffdixon is already involved.
I’ve tried to install it a few times, but I always face the same issue.
bpetit commented on January 11, 2023
It seems I have the exact same error, on
ffdixon commented on January 11, 2023
We just did a new install on Ubuntu 20.04 using Digital Ocean and it worked.
blank ubuntu 20.04 LTS system which runs as a virtual machine on ESXi
We’re thinking the issue is running it under ESXi. @bpetit Are you installing in this environment?
bpetit commented on January 11, 2023
I am. But it is a KVM host, not an ESXi one.
As a first guess, I’d say it would be interesting to look at the base VM images, rather than the VMM or hypervisor.
In my case this is an ubuntu 20.04 «minimal». Maybe «complete» ubuntu images already include what’s needed for bbb-install, which explains you get a clean installation ?
ffdixon commented on January 11, 2023
I would try the complete ubuntu images. We’re seeing no problem installing on Digital Ocean.
bpetit commented on January 11, 2023
I tried with the complete image, no good.
To better understand, what’s the exact version of ubuntu you had on DO ?
In the mean time I tried to identify the root cause. It seems that kurento media server, needs libcurl3 to start properly (at least in the version installed by bbb-install 2.5), while BBB needs libcurl4 (at least bbb-conf —check says so). The two are incompatible (from apt point of view) and libcurl3 is not available as a package in 20.04.5.
I managed to successfully start kurento media server, after having hackishly installed libcurl3 (and broke bbb as libcurl4 had to be removed). So it’s not satisfying at all, but it seems to indicate that libcurl3 vs libcurl4 is root problem.
Did you have libcurl3 still on your ubuntu VM ? I wonder what was the difference.
Related Issues (20)
- Error running wget -qO- command https://ubuntu.bigbluebutton.org/bbb-install.sh | bash -s — -v bionic-240 -s bbb.example.com -e [email protected] -a -w HOT 5
- Test installation HOT 3
- Check for Apache’s installation should be a warning HOT 1
- Enable HSTS on https installations
- Enable X-Content-Type-Options
- ./bbb-install-2.5.sh: line 209: [: missing `]’ HOT 1
- bbb-install for 2.5 messes up greenlight HOT 2
- Websocket Error with bigbluebutton code#1002 HOT 2
- certbot not renewing on 2.6 install due to nginx directory change HOT 1
- problem with installation: Depends: bbb-config but it is not going to be installed
- Add an option to install webhooks HOT 2
- don’t set PROXY PORT HOT 1
- Improve NAT configuration HOT 1
- issue with installing turn server HOT 1
- Sanity check for `-d` (/local/certs/)
- BigBlueButton errors 1107
- [2.6-beta3] Installation script does not respect -p option HOT 2
- bbb-install.sh stuck during update HOT 4
- Ruby 2.5 fails rubygems-update on ubuntu 18.04.6 LTS HOT 3
Recommend Projects
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
TensorFlow
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
Recommend Topics
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
server
A server is a program made to process requests and deliver data to clients.
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Visualization
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Recommend Org
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Источник
Big Blue Button
This article or section is a stub. Stubs are articles that have not yet received substantial attention from the authors. They are short or insufficient pieces of information and require additions to further increase the article’s usefulness. The project values stubs as useful first steps toward complete articles.
|
Contents
Configuring TURN
Configuration
The configuration files can be found on the BBB Configuration page.
Disable Echo Test
Edit /etc/bigbluebutton/bbb-html5.yml — if this file does not exist then run:
Then edit the properties you want.
Testing configuration
Run the configuration test script to see some potential issues and solutions.
Nextcloud integration
BBB has a Nextcloud integration that makes organising calls much easier if you already use a Nextcloud instance. It adds a new icon on the taskbar (shown at the top of the image below) that takes you to a page where you can manage rooms. Each room can be configured with a lot of useful options such as automatic private rooms for your Nextcloud users. The room is entered by simply clicking the play button for the appropriate room. You can copy a link for inviting other users too.
Note that by default a room you create will not show up in the list for any of the other users in your Nextcloud. You need to add them as moderators and then click the share icon to the right of each moderator to make them all admins for the room.
Troubleshooting
ICE error 1107, video not working
After initial installation, room members couldn’t activate video, all getting Connection failed: ICE error 1107, which is a known issue in Github. This is most likely that UDP is not getting through to the server. You can test UDP as follows:
On the target machine being tested:
And on the machine sending the tests:
Then type text and hit enter, it should be echoed on the server.
If it’s not, check the firewall status and disable:
If you still are having issues, setup a TURN server which should significantly improve reliability.
Query String API
Security
You will need access to the shared secret in BBB’s configuration:
Источник
If you encountered any problems with the installation of BigBlueButton, this section covers how to resolve many of the common issues.
If you have not already done so, read through the getting help section.
Introduction
Start here: run sudo bbb-conf --check
We’ve built in a BigBlueButton configuration utility, called bbb-conf
, to help you configure your BigBlueButton server and troubleshoot your setup if something doesn’t work right.
If you think something isn’t working correctly, the first step is enter the following command.
This will check your setup to ensure the correct processes are running, the BigBlueButton components have correctly started, and look for common configuration problems that might prevent BigBlueButton from working properly.
If you see text after the line ** Potential problems described below **
, then it may be warnings (which you can ignore if you’ve change settings) or errors with the setup.
Recording
Recording not processing after upgrading
If after updating from BigBlueButton 2.0 to BigBlueButton 2.2 your recordings are not processing, and if you are seeing Permission denied
errors in /var/log/bigbluebutton/bbb-rap-worker.log
I, [2019-06-07T14:26:09.034878 #14808] INFO -- : /usr/lib/ruby/2.5.0/logger.rb:754:in `initialize': Permission denied @ rb_sysopen - /var/log/bigbluebutton/presentation/process-02feca80700b3e95b877af85db972904397857a1-1559909318977.log (Errno::EACCES)
You can resolve the errors with the following command
$ sudo chown -hR bigbluebutton:bigbluebutton /var/log/bigbluebutton/presentation /var/log/bigbluebutton/screenshare
and then rebuild the recordings that had not yet processed. You can see the list of recordings with
and then to rebuild a recording, use sudo bbb-record --rebuild <internal_meeting_id>
, as in
$ sudo bbb-record --rebuild 298b06603719217df51c5d030b6e9417cc036476-1559314745219
Webcams/screen sharing aren’t working
Certify that appropriate external addresses have been set for mediasoup. When installed via packages, mediasoup IPs are normally misconfigured. If installed via bbb-install, then IPv4 is generally correct, but IPv6 might be absent.
Nonetheless, we recommend double-checking the instructions in Updating mediasoup.
Configure mediasoup to use IPv6
mediasoup (bbb-webrtc-sfu) does not come with a IPv6 enabled by default when installed either via packages or bbb-install.
To configure IPv6, bbb-webrtc-sfu’s override configuration file (located in /etc/bigbluebutton/bbb-webrtc-sfu/production.yml
) should be used.
See Updating mediasoup for instructions and examples on how to do so.
I’m having troubles seeing webcams or screen sharing in Firefox
That’s usually the symptom of a known Firefox issue where it doesn’t comply with ICE-lite implementations (and mediasoup is one).
This issue can be worked around by forcing TURN usage in Firefox user agents. To achieve that, set the public.kurento.forceRelayOnFirefox
configuration to true
in /etc/bigbluebutton/bbb-html5.yml
. For example:
public:
kurento:
forceRelayOnFirefox: true
How often does this Firefox issue happens?
Short (non) answer: that’s difficult to measure.
Every Firefox installation is prone to the lack of ICE-lite spec compliance. However, the issue doesn’t manifest itself on all Firefox installations as it is dependent on how the end user’s network topology is organized. It’s generally a small subset of Firefox users, but that can vary depending on the user base.
Where can I track progress on a definitive solution or better workaround?
This is a Firefox bug, so the best place to get an overview on progress and what the issue is about is Mozilla’s issue.
You can also track BigBlueButton’s issue for updates on additional workarounds.
Why isn’t forceRelayOnFirefox enabled by default?
It’s not on by default because bigbluebutton does not come with a TURN server by default, and that’s what versioned-in-code setting presumes.
How do I know if mediasoup is being used?
The most direct and precise way to figure out whether mediasoup is being used is checking about:webrtc (Firefox) or chrome://webrtc-internals. For example: open one of those, share a camera. Look for the remote description (SDP); see if it contains mediasoup-client in the SDP header. If it does, you’re using mediasoup.
Regardless of that: mediasoup is the default in 2.5 and should always be used unless default settings were explicitly changed.
mediasoup is the default in 2.5. Why is Kurento still around?
Because Kurento is still used for stream recording. It should be removed as a dependency as soon as this issue is addressed.
Is single-core performance still important with mediasoup?
Yes.
How can I control the number of mediasoup workers?
To control the number of mediasoup workers, bbb-webrtc-sfu’s override configuration file (located in /etc/bigbluebutton/bbb-webrtc-sfu/production.yml
) should be used.
There are a couple of configurations of interest here:
mediasoup.workers
This configuration controls the number of mediasoup workers intended for general use (media type agnostic, shared pool).
Accepted values are:
"auto"
(default): createsceil((min(nproc,32) * 0.8) + (max(0, nproc - 32) / 2))
workers;"cores"
: creates workers up to the host’s core count (as provided by os.cpus().length);- <Number>: overrides the number of workers with a fixed value;
- The default and fallback values are
auto
.
For example:
- To set the number of workers to
cores
:yq w -i /etc/bigbluebutton/bbb-webrtc-sfu/production.yml mediasoup.workers "cores"
mediasoup.dedicatedMediaTypeWorkers
This configuration controls the number of mediasoup workers to be used by specific media types.
If a dedicated pool is set, streams of its media type will always land on it. Otherwise, they will use the shared pool.
The configuration is an object of the following format:
mediasoup.dedicatedMediaTypeWorkers:
audio: "auto"|"cores"|<Number>
main: "auto"|"cores"|<Number>
content: "auto"|"cores"|<Number>
The semantics of auto
, cores
and Number
are the same as in the mediasoup.workers
configuration. Default values for all media types are 0
(no dedicated workers).
The media types semantics are:
audio
: audio (listen only, microphone) streams;main
: webcam video streams;content
: screen sharing streams (audio and video).
For example:
- To set the number of dedicated audio workers to
auto
:yq w -i /etc/bigbluebutton/bbb-webrtc-sfu/production.yml mediasoup.dedicatedMediaTypeWorkers.audio "auto"
Can I scale the number of streams up indefinitely with mediasoup?
No. Scalability improves a lot with mediasoup, but there are still a couple of bottlenecks that can be hit as far as far as the media stack is concerned. Namely:
- The signaling server (bbb-webrtc-sfu): it does not scale vertically indefinitely. There’s always work ongoing on this area that can be tracked in this issue;
- The mediasoup worker balancing algorithm implemented by bbb-webrtc-sfu is still focused on multiparty meetings with a restrained number of users. If your goal is thousand-user 1-N (streaming-like) meetings, you may max out CPU usage on certain mediasoup workers even though there are other idle oworkers free.
Kurento
WebRTC video not working with Kurento
Check the value for /proc/sys/net/ipv4/tcp_syncookies
that it contains the value 1
.
$ cat /proc/sys/net/ipv4/tcp_syncookies
1
If not, edit /etc/sysctl.conf
and set the value for net.ipv4.tcp_syncookies
to 1
.
net.ipv4.tcp_syncookies = 1
Save the file and restart.
Unit kurento-media-server.service is masked
If sudo bbb-conf --check
returns the warning
Restarting BigBlueButton 2.0.0-RC9 (and cleaning out all log files) ...
Stopping BigBlueButton
... cleaning log files
Starting BigBlueButton
Failed to start kurento-media-server.service: Unit kurento-media-server.service is masked.
You can unmask Kurento using the command
$ systemctl unmask kurento-media-server.service
The default installation of BigBlueButton should work in most netowrk configurations; however, if your users ae behind a restrictive network that blocks outgoing UDP connections, they may encounter 1020 errors (media unable to reach server).
If you get reports of these errors, setup TURN server to help their browsers send WebRTC audio and video streams via TCP over port 443 to the TURN server. The TURN server will then relay the media to your BigBlueButton server.
See Configure TURN.
FreeSWITCH
Configure BigBluebutton/FreeSWITCH to support IPV6
The HTML5 client now enables users on mobile devices to connect to a BigBlueButton server. However, on some cellular networks iOS devices only receive an IPV6 address.
To enable BigBlueButton (FreeSWITCH) to accept incoming web socket connections on IPV6, the BigBlueButton server must have an IPV6 address. You also need to make the following changes to the server.
First, create the file /etc/nginx/conf.d/bigbluebutton_sip_addr_map.conf
with this content:
map $remote_addr $freeswitch_addr {
"~:" [2001:db8::1];
default 192.0.2.1;
}
replacing the ip addresses 192.0.2.1
with the system’s external IPV4 addresses, and replace 2001:db8::1
with the system’s external IPV6 address. Next, edit the file /etc/bigbluebutton/nginx/sip.nginx
to have the following:
proxy_pass https://$freeswitch_addr:7443;
Next, ensure all of the following params are present in freeswitch’s sip_profiles/external-ipv6.xml
:
- ws-binding
- wss-binding
- rtcp-audio-interval-msec
- rtcp-video-interval-msec
- dtmf-type
- liberal-dtmf
- enable-3pcc
If any are missing, copy them from sip_profiles/external.xml
, then restart BigBlueButton (sudo bbb-conf --restart
).
FreeSWITCH fails to bind to IPV4
In rare occasions after shutdown/restart, the FreeSWITCH database can get corrupted. This will cause FreeSWITCH to have problems binding to IPV4 address (you may see error 1006 when users try to connect).
To check, look in /opt/freeswitch/var/log/freeswitch/freeswitch.log
for errors related to loading the database.
2018-10-25 11:05:11.444727 [ERR] switch_core_db.c:108 SQL ERR [unsupported file format]
2018-10-25 11:05:11.444737 [ERR] switch_core_db.c:223 SQL ERR [unsupported file format]
2018-10-25 11:05:11.444759 [NOTICE] sofia.c:5949 Started Profile internal-ipv6 [sofia_reg_internal-ipv6]
2018-10-25 11:05:11.444767 [CRIT] switch_core_sqldb.c:508 Failure to connect to CORE_DB sofia_reg_external!
2018-10-25 11:05:11.444772 [CRIT] sofia.c:3049 Cannot Open SQL Database [external]!
If you see these errors, clear the FreeSWITCH database (BigBlueButton doesn’t use the database and FreeSWITCH will recreate it on startup).
$ sudo systemctl stop freeswitch
$ rm -rf /opt/freeswitch/var/lib/freeswitch/db/*
$ sudo systemctl start freeswitch
Forward calls from an Asterisk server to FreeSWITCH
Let’s assume the following:
asterisk server ip: 192.168.1.100
bigbluebutton/freeswitch ip: 192.168.1.200
Changes to your Asterisk server
Setup your gateway to BigBlueButton/FreeSWITCH. in /etc/asterisk/sip.conf
add
[fs-gw]
type=peer
username=fs-gw
insecure=very
contactpermit=192.168.1.200/255.255.255.255
qualify=no
nat=yes
host=192.168.1.200
canreinvite=no
disallow=all
allow=ulaw
Route the calls to the gateway. In /etc/asterisk/extensions.conf
context where your calls are being handled, forward the calls to the gateway. Here, when someone dials 85001, the call is sent to the fs-gw
defined above.
exten => 85001,1,Dial(SIP/fs-gw/${EXTEN})
exten => 85001,2,Hangup
Changes to your BigBlueButton/FreeSWITCH server
In BigBlueButton/FreeSWITCH, make the following changes:
Lock down so that only Asterisk can forward calls to FreeSWITCH. In /opt/freeswitch/conf/autoload_configs/acl.conf.xml
, add the following ACL. We also need to allow BigBlueButton to call into FreeSWITCH, that’s why we add the IP of BigBlueButton/FreeSWITCH into the ACL.
<list name="asterisk-gw" default="deny">
<node type="allow" cidr="192.168.1.200/32"/>
<node type="allow" cidr="192.168.1.100/32"/>
<node type="allow" cidr="127.0.0.1/32"/>
</list>
Then we apply the ACL into the profile that receives the calls from external gateways. In /opt/freeswitch/conf/sip_profiles/external.xml
, add the ACL under <settings>
<settings>
<!-- Apply ACL from asterisk-gw -->
<param name="apply-inbound-acl" value="asterisk-gw"/>
...
</settings>
To debug, try connecting to FS CLI and increase logging level. Once connected, make your call and see what the logs say.
$ /opt/freeswitch/bin/fs_cli -p $(xmlstarlet sel -t -m 'configuration/settings/param[@name="password"]' -v @value /opt/freeswitch/etc/freeswitch/autoload_configs/event_socket.conf.xml)
Once connected:
help -- shows the available commands
console loglevel <level> -- change log level
Ctrl-D to exit
FreeSWITCH fails to bind to port 8021
FreeSWITCH supports both IPV4 and IPV6. However, if your server does not support IPV6, FreeSWITCH will be unable to bind to port 8021. If you run sudo bbb-conf --check
and see the following error
# Error: Found text in freeswitch.log:
#
# Thread ended for mod_event_socket
#
# FreeSWITCH may not be responding to requests on port 8021 (event socket layer)
# and users may have errors joining audio.
#
it might be that your server has IPV6 disabled (or does not support it). You can check this by running the following command
$ sudo ip addr | grep inet6
inet6 ::1/128 scope host
...
If you do not see the line inet6 ::1/128 scope host
, then your server has IPV6 disabled. In this case, we need to disable FreeSWITCH’s support for IPV6. First, edit /opt/freeswitch/etc/freeswitch/autoload_configs/event_socket.conf.xml
and change the line
<param name="listen-ip" value="::"/>
to
<param name="listen-ip" value="127.0.0.1"/>
This tells FreeSWITCH that instead of binding port 8021 to the local IPV6 address, bind to the IPV4 address 127.0.0.1. Next, execute the following two commands
$ 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_
and then restart BigBlueButton with the commands
$ sudo bbb-conf --clean
$ sudo bbb-conf --check
FreeSWITCH fails to start with a SETSCHEDULER error
When running in a container (like a chroot, OpenVZ or LXC), it might not be possible for FreeSWITCH to set its CPU priority to real-time round robin. If not, it will result in lower performance compared to a non-virtualized installation.
If you running BigBlueButton in a container and an error starting FreeSWITCH, try running systemctl status freeswitch.service
and see if you see the error related to SETSCHEDULER
$ systemctl status freeswitch.service
● freeswitch.service - freeswitch
Loaded: loaded (/lib/systemd/system/freeswitch.service; enabled; vendor preset: enabled)
Active: inactive (dead) (Result: exit-code) since Mon 2017-10-02 16:17:29 UTC; 18s ago
Process: 10967 ExecStart=/opt/freeswitch/bin/freeswitch -u freeswitch -g daemon -ncwait $DAEMON_OPTS (code=exited, status=214/SETSCHEDULER)
Main PID: 3327 (code=exited, status=0/SUCCESS)
Oct 02 16:17:29 scw-9e2305 systemd[1]: Failed to start freeswitch.
Oct 02 16:17:29 scw-9e2305 systemd[1]: freeswitch.service: Unit entered failed state.
Oct 02 16:17:29 scw-9e2305 systemd[1]: freeswitch.service: Failed with result 'exit-code'.
Oct 02 16:17:29 scw-9e2305 systemd[1]: freeswitch.service: Service hold-off time over, scheduling restart.
Oct 02 16:17:29 scw-9e2305 systemd[1]: Stopped freeswitch.
Oct 02 16:17:29 scw-9e2305 systemd[1]: freeswitch.service: Start request repeated too quickly.
Oct 02 16:17:29 scw-9e2305 systemd[1]: Failed to start freeswitch.
If you see SETSCHEDULER
in the error message, edit /lib/systemd/system/freeswitch.service
and comment out the line containing CPUSchedulingPolicy=rr
(round robin)
IOSchedulingPriority=2
#CPUSchedulingPolicy=rr
CPUSchedulingPriority=89
Save the file, run systemctl daemon-reload
, and then restart BigBlueButton. FreeSWITCH should now startup without error.
Users not able to join Listen Only mode
When doing sudo bbb-conf --check
, you may see the warning
voice Application failed to register with sip server
This error occurs when bbb-apps-sip
isn’t able to make a SIP call to FreeSWITCH. You’ll see this in BigBlueButton when users click the headset icon and don’t join the voice conference.
One possible cause for this is you have just installed BigBlueButton, but not restarted it. The packages do not start up the BigBlueButton components in the right order. To restart BigBlueButton, do the following:
$ sudo bbb-conf --restart
$ sudo bbb-conf --check
If you don’t want FreeSWITCH to bind to 127.0.0.1, you need to figure out which IP address its using. First, determine the IP address FreeSWITCH is monitoring for incoming SIP calls with the following command:
$ netstat -ant | grep 5060
You should see an output such as
tcp 0 0 234.147.116.3:5060 0.0.0.0:* LISTEN
In this example, FreeSWITCH is listening on IP address 234.147.116.3. The IP address on your server will be different.
Next, edit /usr/share/red5/webapps/sip/WEB-INF/bigbluebutton-sip.properties
and set the value for sip.server.host
to the IP address returned from the above command. Save the changes (you’ll need to edit the file as root to save changes).
Restart BigBlueButton using the commands and run the built-in diagnostics checks.
$ sudo bbb-conf --clean
$ sudo bbb-conf --check
Unable to connect using fs_cli
As of BigBlueButton 2.2.18, the packaging now replaces the default ClueCon
password for connecting to the FreeSWITCH command line interface (fs_cli
) with a random password.
(By default, FreeSWITCH only allowed unauthenticated connections from 127.0.0.1, but it’s still good security practice to not use default passwords).
To connect to fs_cli
, use the following command which supplies the password for authenticating.
/opt/freeswitch/bin/fs_cli -p $(xmlstarlet sel -t -m 'configuration/settings/param[@name="password"]' -v @value /opt/freeswitch/etc/freeswitch/autoload_configs/event_socket.conf.xml)
We also added /usr/local/bin/fs_clibbb
with the contents
#!/bin/bash
/opt/freeswitch/bin/fs_cli -p $(xmlstarlet sel -t -m 'configuration/settings/param[@name="password"]' -v @value /opt/freeswitch/etc/freeswitch/autoload_configs/event_socket.conf.xml)
that will let you type fs_clibbb
at the command prompt to get into FreeSWITCH console.
Echo test hangs upgrading BigBlueButton 2.2
The install scripts now change the default CLI password for FreeSWITCH and the other parts of BigBlueButton need to use this new password. For a new installation, the install scripts will automatically set this new password.
If you upgrade using bbb-install.sh, the script will update the FreeSWITCH password using sudo bbb-conf --setip <hostname>
.
If you upgraded using manual steps, be sure to do ao sudo bbb-conf --setip <hostname>
to sync all the FreeSWITCH passwords.
FreeSWITCH using default stun server
For many years, in BigBlueButton’s FreeSWITCH configuration file /opt/freeswitch/etc/freeswitch/vars.xml
, the default value for external_rtp_ip
was stun.freeswitch.org
<X-PRE-PROCESS cmd="set" data="external_rtp_ip=stun:stun.freeswitch.org"/>
However, this is not a reliable choice for stun server. Recommend either changing it to your servers external IP address or setup your own stun/turn server. For example, if your server has an external IP at 234.32.3.3
<X-PRE-PROCESS cmd="set" data="external_rtp_ip=234.32.3.3"/>
You can add a line in /etc/bigbluebutton/bbb-conf/apply-conf.sh
to always apply this value even if the FreeSWITCH package upgrades.
xmlstarlet edit --inplace --update '//X-PRE-PROCESS[@cmd="set" and starts-with(@data, "external_rtp_ip=")]/@data' --value "external_rtp_ip=234.32.3.3" /opt/freeswitch/conf/vars.xml
Note: If your server has an internal/exteral IP address, such as on AWS EC2 server, be sure to set it to the external IP address configure a dummy network interface card (see Update FreeSWITCH).
HTML5 Server
bbb-html5 fails to start with a SETSCHEDULER error
As of 2.2.31, the systemd unit file for bbb-html5.service
now contains the following lines
CPUSchedulingPolicy=fifo
Nice=19
You can override this with creating the following directory
mkdir /etc/systemd/system/bbb-html5.service.d
and creating /etc/systemd/system/bbb-html5.service.d/override.conf
with the following contents
[Service]
CPUSchedulingPolicy=other
Nice=-10
Then do systemctl daemon-reload
and restart BigBlueButton.
Installation and packages
The following packages have unmet dependencies
When installing the latest build of BigBlueButton, the package bbb-conf
now uses yq
to manage YAML files.
You need to add the repository ppa:rmescandon/yq
to your server. For steps on how to do this, see Update your server in the BigBlueButton 2.2 install guide.
Alternatively, if you have not made any customizations to BigBlueButton (outside of using bbb-conf
), you can use bbb-install.sh to install/upgrade to the latest version (the bbb-install.sh
script will automatically install the repository for yq
).
No Symbolic Link
If you’ve installed/uninstalled BigBlueButton packages, you may get a No Symbolic Link
warning from bbb-conf --check
:
** Potential Problems **
nginx (conf): no symbolic link in /etc/nginx/sites-enabled for bigbluebutton
To solve this, add a symbolic link to nginx for the BigBlueButton site:
$ sudo ln -s /etc/nginx/sites-available/bigbluebutton /etc/nginx/sites-enabled/bigbluebutton
$ sudo /etc/init.d/nginx restart
Package install fails with sed error
Some of the BigBlueButton packages use sed
scripts to extract contents from configuration files. If the file does not exist at the time of the script’s execution, or the sed script matches multiple entries in a file (such as when a configuration line is commented out), you can see an error such as
Setting up bbb-client (1:2.0.0-374) ...
sed: -e expression #1, char 42: unterminated `s' command
dpkg: error processing package bbb-client (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of bbb-config:
bbb-config depends on bbb-client; however:
Package bbb-client is not configured yet.
dpkg: error processing package bbb-config (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
bbb-client
bbb-config
E: Sub-process /usr/bin/dpkg returned an error code (1)
In the above example, the /var/lib/dpkg/info/bbb-client.postinst
failed to finish. To debug, edit this file and change the first line to read
and run
$ sudo apt-get install -f
You should now see each command in bbb-conf.postinst
as it executes upto the line in which the error occurs. Post this output to https://groups.google.com/forum/#!forum/bigbluebutton-setup
for help in resolving the issue.
Errors with packages
Some hosting providers do not provide a complete /etc/apt/source.list
. If you are finding your are unable to install a package, try replacing your /etc/apt/sources.list
with the following
deb https://archive.ubuntu.com/ubuntu xenial main restricted universe multiverse
deb https://archive.ubuntu.com/ubuntu xenial-updates main restricted universe multiverse
deb https://security.ubuntu.com/ubuntu xenial-security main restricted universe multiverse
then do
and try installing BigBlueButton again from the beginning.
WebRTC errors (1001, 1002,…)
WebRTC offers very high-quality audio. However, the user’s network settings (or firewall) may not allow WebRTC to connect (or keep connected).
Here are the following lists the possible WebRTC error messages that a user may encounter:
- 1001: WebSocket disconnected — The WebSocket had connected successfully and has now disconnected. Possible Causes:
- Loss of internet connection
- Nginx restarting can cause this
- 1002: Could not make a WebSocket connection — The initial WebSocket connection was unsuccessful. Possible Causes:
- Firewall blocking ws protocol
- Server is down or improperly configured
- See potential solution here.
- 1003: Browser version not supported — Browser doesn’t implement the necessary WebRTC API methods. Possible Causes:
- Out of date browser
- 1004: Failure on call — The call was attempted, but failed. Possible Causes:
- For a full list of causes refer here
- There are 24 different causes so I don’t really want to list all of them
- Solution for this issue outlined here.
- 1005: Call ended unexpectedly — The call was successful, but ended without user requesting to end the session. Possible Causes:
- Unknown
- 1006: Call timed out — The library took too long to try and connect the call. Possible Causes:
- Previously caused by Firefox 33-beta on Mac. We’ve been unable to reproduce since release of FireFox 34
- 1007: ICE negotiation failed — The browser and FreeSWITCH try to negotiate ports to use to stream the media and that negotiation failed. Possible Causes:
- NAT is blocking the connection
- Firewall is blocking the UDP connection/ports
- 1008: Call transfer failed — A timeout while waiting for FreeSWITCH to transfer from the echo test to the real conference. This might be caused by a misconfiguration in FreeSWITCH, or there might be a media error and the DTMF command to transfer didn’t go through (In this case, the voice in the echo test probably didn’t work either.)
- 1009: Could not fetch STUN/TURN server information — This indicates either a BigBlueButton bug (or you’re using an unsupported new client/old server combination), but could also happen due to a network interruption.
- 1010: ICE negotiation timeout — After the call is accepted the client’s browser and the server try and negotiate a path for the audio data. In some network setups this negotiation takes an abnormally long time to fail and this timeout is set to avoid the client getting stuck.
- 1020: Media cloud could not reach the server — See how to solve this here.
Networking
Server running behind NAT
The following issue might be helpful in debugging if you run into errors and your server is behind NAT.
Could not get your microphone for a WebRTC call
Chrome requires (As of Chrome 47) that to access the user’s microphone for WebRTC your site must be serving pages via HTTPS (that is, nginx is configured with a SSL certificate).
If the user attempts to share their microphone and your BigBlueButton sever is not configured for SSL, Chrome will block access and BigBlueButton will report the following error
WebRTC Audio Failure: Detected the following WebRTC issue: Could not get your microphone for a WebRTC call. Do you want to try flash instead?
To enable Chrome to access the user’s microphone, see Configure HTTPS on BigBlueButton.
The browser is not supported
When you attempt to join a BigBlueButton session, the client looks for supported browsers before fully loading. The client gets its list of supported browsers from /usr/share/meteor/bundle/programs/server/assets/app/config/settings.yml
. You can see the list of supported browsers at the bottom. For example,
- browser: mobileSafari
version:
- 11
- 1
states that Mobile Safari
version 11.1 or later is supported (notice the first letter is lower case and concatenated with the remainder of the browser name).
To add a browser to the list, first find your browser’s useragent. You could use a tool like https://wtools.io/check-my-user-agent as well. For example, with the Vivaldi browser you might see
Vivaldi 2.8.1664 / Linux 0.0.0
Next, to add this as a supported browser, append to settings.yml
- browser: vivaldi
version:
- 2
- 8
save the updated settings.yml
file, and then restart your BigBlueButton server with sudo bbb-conf --restart
. Note any browser you add must support WebRTC libraries (not all do), so be sure to check it first with https://test.webrtc.org/.
Tomcat shows “Cannot assign requested address on startup”
If your server has multiple IP addresses, Tomcat might not pick the right address to bind. This could throw an error on installation when tomcat is attempting to install.
Check /var/log/tomcat7/catalina.out
for the following error
Jan 30, 2018 9:17:37 AM org.apache.catalina.core.StandardServer await
SEVERE: StandardServer.await: create[localhost:8005]:
java.net.BindException: Cannot assign requested address (Bind failed)
at java.net.PlainSocketImpl.socketBind(Native Method)
If you see this, first ensure that there isn’t another copy of tomcat running by doing ps -aef | grep tomcat7
. If you do see another copy running, try killing it and then restarting tomcat.
If you still see the same error in catalina.out
, then /etc/tomcat7/server.xml
and change
<Server port="8005" shutdown="SHUTDOWN">
<Server address="0.0.0.0" port="8005" shutdown="SHUTDOWN">
Restart tomcat7 again and it should start normally.
nginx not running
The common reasons for nginx not running are inability to bind to port 80 and configuration errors. To check if port 80 is already in use, use
to see if any process is currently bound to port 80. If so, check to see if another web server is installed. If so, then stop the web server and try to restart nginx. One of the server requirements before you install BigBlueButton is that port 80 is not in use by another application (such as Apache). For details on why this is a requirements, see We recommend running BigBlueButton on port 80.
If port 80 is free, check if your nginx configuration file has errors. Try a restart of nginx
$ sudo systemctl restart nginx
and look for the output of
[ OK ]
If you see [ Fail ]
, then your nginx configuration files might have a syntax error. Check the syntax of the nginx configuration files using the command
and see if it reports any errors. You can also check the error.log file for nginx to see what errors it gives on startup
$ sudo cat /var/log/nginx/error.log
“Welcome to nginx”
During installation of BigBlueButton the packaging scripts attempt to assign the correct IP address during setup. However, if the IP address changes (such as when rebooting a VM), or the first IP address was not the correct IP address for the server, you may see a “Welcome to nginx” page.
To reconfigure the BigBlueButton to use the correct IP address or hostname, see BigBlueButton does not load.
bbb-web
404 Error when loading the client
BigBlueButton 2.2 requires Java 8 as the default Java. Recently, some Ubuntu 16.04 distributions have switched the default version of Java to Java 9 (or later).
Use java -version
to check that the default version of 1.8.0
.
~/dev$ java -version
openjdk version "1.8.0_242"
OpenJDK Runtime Environment (build 1.8.0_242-8u242-b08-0ubuntu3~16.04-b08)
OpenJDK 64-Bit Server VM (build 25.242-b08, mixed mode)
If not, do the following
sudo apt-get install openjdk-8-jre
update-alternatives --config java # Choose java-8 as default
Run java -version
and confirm it now shows the default as 1.8.0
, and then restart BigBlueButton with sudo bbb-conf --restart
Blank presentation area on create or upload
If you join a meeting and the default presentation is not visible or your uploaded presentation doesn’t display, then this is most likely due to a permissions error. To solve this, ensure that /var/bigbluebutton/
is owned by bigbluebutton
rather than root
or any other account. See this issue for more explanation.
Unable to create presentation
If you see the following error in /var/log/bigbluebutton/bbb-web.log
failed to map segment from shared object: Operation not permitted
use the command mount
to check that the /tmp
director does not have noexec
permissions (which would prevent executables from running in the /tmp directory). If you see noexec
for /tmp
, you need to remount the directory with permissions that enable processes (such as the slide conversion) to execute in the /tmp
directory.
Too many open files
On servers with greater than 8 CPU cores, bbb-web
log (/var/log/bigbluebutton/bbb-web.log
) may throw an error of Too many open files
Caused by: java.io.IOException: Too many open files
To resolve, create an override file that increases the number of open files for bbb-web
$ sudo mkdir -p /etc/systemd/system/bbb-web.service.d/
$ sudo cat > /etc/systemd/system/bbb-web.service.d/override.conf << HERE
[Service]
LimitNOFILE=
LimitNOFILE=8192
HERE
$ sudo systemctl daemon-reload
bbb-web takes a long time to startup
bbb-web
relies on the SecureRandom class (which uses available entropy) to provide random values for its session IDs. On a virtualized server, however, the available entropy can run low and cause bbb-web to block for a long period before it finishes it’s startup sequence (see Slow startup of tomcat).
To provide bbb-web
with more entropy, you can install haveged
$ sudo apt-get install haveged
For more information see How to Setup Additional Entropy for Cloud Servers Using Haveged.
Error installing bbb-web
If you get the following error during upgrade to BigBlueButton
Unpacking bbb-web (1:2.2.0-67) over (1:2.2.0-66) ...
dpkg: error processing archive /var/cache/apt/archives/bbb-web_1%3a2.2.0-67_amd64.deb (--unpack):
trying to overwrite '/etc/bigbluebutton/nginx/web', which is also in package bbb-client 1:2.2.0-28
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/bbb-web_1%3a2.2.0-67_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)```
Then first uninstall bbb-client
$ sudo apt-get purge bbb-client
and try installing BigBlueButton again.
Other errors
Root partition too small
If the root partition on your BigBlueButton server is too small (for disk space requirements see Before you install), we recommend moving the following directories to an external partition with sufficient disk space.
BigBlueButton processing and storage of recordings:
Location of all media directories on disk available here.
To make the move, we’ll first stop BigBlueButton, then move the above directories to a new location on the external partition, create symbolic links from the original locations to the new locations, and restart BigBlueButton.
In the following example, the external partition is mounted on /mnt
.
$ sudo bbb-conf --stop
$ sudo mv /var/freeswitch/meetings /mnt
$ sudo ln -s /mnt/recordings /var/freeswitch/meetings
$ sudo mv /usr/share/red5/webapps/video/streams /mnt
$ sudo ln -s /mnt/streams /usr/share/red5/webapps/video/streams
$ sudo /var/bigbluebutton /mnt
$ sudo ln -s /mnt/bigbluebutton /var/bigbluebutton
$ sudo bbb-conf --start
BigBlueButton does not load
If your has changed it’s network connection (such as on reboot), you can clean most of BigBlueButton’s configuration files with the following steps.
$ sudo bbb-conf --setip <ip_address_or_hostname>
$ sudo bbb-conf --clean
$ sudo bbb-conf --check
For more information see bbb-conf options.
Running within an LXD Container
LXD is a very powerful container system for Ubuntu lets you run full Ubuntu 16.04 servers within a container. Because you can easily clone and snapshot LXD containers, they are ideal for development and testing of BigBlueButton.
However, if you install BigBlueButton within an LXD container, you will get the following error from sudo bbb-conf --check
** Potential problems described below **
#
# Error: Unable to connect to the FreeSWITCH Event Socket Layer on port 8021
You’ll also get an error from starting FreeSWITCH with bbb-conf --restart
. When you try systemctl status freeswitch.service
, you’ll see an error with SETSCHEDULER.
$ sudo systemctl status freeswitch.service
● freeswitch.service - freeswitch
Loaded: loaded (/lib/systemd/system/freeswitch.service; enabled; vendor preset: enabled)
Active: inactive (dead) (Result: exit-code) since Wed 2017-04-26 16:34:24 UTC; 23h ago
Process: 7038 ExecStart=/opt/freeswitch/bin/freeswitch -u freeswitch -g daemon -ncwait $DAEMON_OPTS (code=exited, status=214/SETSCHEDULER)
Apr 26 16:34:24 big systemd[1]: Failed to start freeswitch.
Apr 26 16:34:24 big systemd[1]: freeswitch.service: Unit entered failed state.
Apr 26 16:34:24 big systemd[1]: freeswitch.service: Failed with result 'exit-code'.
Apr 26 16:34:24 big systemd[1]: freeswitch.service: Service hold-off time over, scheduling restart.
Apr 26 16:34:24 big systemd[1]: Stopped freeswitch.
Apr 26 16:34:24 big systemd[1]: freeswitch.service: Start request repeated too quickly.
Apr 26 16:34:24 big systemd[1]: Failed to start freeswitch.
This error occurs because the default systemd unit script for FreeSWITCH tries to run with permissions not available to the LXD container. To run FreeSWITCH within an LXD container, edit /lib/systemd/system/freeswitch.service
and replace with the following
[Unit]
Description=freeswitch
After=syslog.target network.target local-fs.target
[Service]
Type=forking
PIDFile=/opt/freeswitch/var/run/freeswitch/freeswitch.pid
Environment="DAEMON_OPTS=-nonat"
EnvironmentFile=-/etc/default/freeswitch
ExecStart=/opt/freeswitch/bin/freeswitch -u freeswitch -g daemon -ncwait $DAEMON_OPTS
TimeoutSec=45s
Restart=always
WorkingDirectory=/opt/freeswitch
User=freeswitch
Group=daemon
[Install]
WantedBy=multi-user.target
Then enter the following commands to load the new unit file and restart BigBlueButton.
$ sudo systemctl daemon-reload
$ sudo bbb-conf --restart
You can run BigBlueButton within a LXD container.
Unable to connect to redis
The packages bbb-apps-akka
, bbb-fsesl-akka
, and bbb-transcode-akka
are packaged by sbt, but they need to have redis-server running before they startup. If sudo bbb-conf --debug
shows redis connection errors
Sep 22 15:32:12 sv21 bbb-apps-akka[7804]: Exception in thread "main" io.lettuce.core.RedisConnectionException: Unable to connect to 127.0.0.1:6379
Sep 22 15:32:12 sv21 bbb-apps-akka[7804]: #011at io.lettuce.core.RedisConnectionException.create(RedisConnectionException.java:78)
Sep 22 15:32:12 sv21 bbb-apps-akka[7804]: #011at io.lettuce.core.RedisConnectionException.create(RedisConnectionException.java:56)
Sep 22 15:32:12 sv21 bbb-apps-akka[7804]: Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /127.0.0.1:6379
Sep 22 15:32:12 sv21 bbb-apps-akka[7804]: Caused by: java.net.ConnectException: Connection refused
Sep 22 15:32:12 sv21 bbb-fsesl-akka[7893]: Exception in thread "main" io.lettuce.core.RedisConnectionException: Unable to connect to 127.0.0.1:6379
Sep 22 15:32:12 sv21 bbb-fsesl-akka[7893]: #011at io.lettuce.core.RedisConnectionException.create(RedisConnectionException.java:78)
Sep 22 15:32:12 sv21 bbb-fsesl-akka[7893]: #011at io.lettuce.core.RedisConnectionException.create(RedisConnectionException.java:56)
Sep 22 15:32:12 sv21 bbb-fsesl-akka[7893]: Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /127.0.0.1:6379
Sep 22 15:32:12 sv21 bbb-fsesl-akka[7893]: Caused by: java.net.ConnectException: Connection refused
Sep 22 15:32:13 sv21 bbb-transcode-akka[8001]: Exception in thread "main" io.lettuce.core.RedisConnectionException: Unable to connect to 127.0.0.1:6379
Sep 22 15:32:13 sv21 bbb-transcode-akka[8001]: #011at io.lettuce.core.RedisConnectionException.create(RedisConnectionException.java:78)
Sep 22 15:32:13 sv21 bbb-transcode-akka[8001]: #011at io.lettuce.core.RedisConnectionException.create(RedisConnectionException.java:56)
Sep 22 15:32:13 sv21 bbb-transcode-akka[8001]: Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /127.0.0.1:6379
Sep 22 15:32:13 sv21 bbb-transcode-akka[8001]: Caused by: java.net.ConnectException: Connection refused
you can add overrides for these three packages to ensure they start after redis.server. Run the following script.
#!/bin/bash
mkdir -p /etc/systemd/system/bbb-apps-akka.service.d
cat > /etc/systemd/system/bbb-apps-akka.service.d/override.conf <<HERE
[Unit]
Requires=redis-server.service
After=redis-server.service
HERE
mkdir -p /etc/systemd/system/bbb-fsesl-akka.service.d
cat > /etc/systemd/system/bbb-fsesl-akka.service.d/override.conf <<HERE
[Unit]
Requires=redis-server.service
After=redis-server.service
HERE
mkdir -p /etc/systemd/system/bbb-transcode-akka.service.d
cat > /etc/systemd/system/bbb-transcode-akka.service.d/override.conf <<HERE
[Unit]
Requires=redis-server.service
After=redis-server.service
HERE
The script bbb-install
now creates these overrides by default.
500 Internal Server Error
It is most likely an error on GreenLight. Check the log file according to Troubleshooting Greenlight.
If this error occurrs on just a small number of PCs accessing a BigBlueButton server within a LAN through a proxy server and you find the description “Error::Unsafe Host Error (x.x.x.x is not a safe host)” (where x.x.x.x is an IP address) in the log file, check if the “Don’t use the proxy server for local (intranet) addresses” (in the Windows proxy setting) is ticked.
Legacy errors
Conference not found errors
The command sudo bbb-conf --debug
searches through the red5, tomcat7, and nginx logs looking for errors and exceptions. However, the messages such as
-- ERRORS found in /usr/share/red5/log/* --
/usr/share/red5/log/bigbluebutton.log:2015-05-02 13:50:37,681-04:00 [pool-17-thread-1] ERROR o.b.w.v.f.a.PopulateRoomCommand - Not XML: [Conference 78505 not found]
are innocuous and can be ignored.
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
2.6 RC1 — Nginx not working after running the script
Closed 10 days agoComments count4
Add option to not install HAProxy + TURN in bbb-install-2.6.sh
Updated 13 days ago
Installing a TURN server behind NAT
Updated 14 days ago
Upgrading from 2.5 to 2.6-turn
Updated 16 days agoComments count1
ICE 1107 error with webcam on clean Ubuntu 20.04 due to libcurl3 / kurento / gstream error
Updated a month agoComments count7
issue with installing turn server
Updated a month agoComments count1
Ruby 2.5 fails rubygems-update on ubuntu 18.04.6 LTS
Closed a month agoComments count3
install BBB with certum ssl
Updated a month agoComments count3
bbb-install.sh stuck during update
Updated 2 months agoComments count4
[2.6-beta3] Installation script does not respect -p option
Updated 2 months agoComments count2
BigBlueButton errors 1107
Updated 2 months ago
Sanity check for `-d` (/local/certs/)
Updated 2 months ago
Add an option to install webhooks
Updated 3 months agoComments count2
don’t set PROXY PORT
Updated 3 months agoComments count1
Improve NAT configuration
Updated 3 months agoComments count1
Websocket Error with bigbluebutton code#1002
Updated 3 months agoComments count2
problem with installation: Depends: bbb-config but it is not going to be installed
Updated 4 months ago
Changing the certificates for new hostname using the install script
Updated 4 months agoComments count1
certbot not renewing on 2.6 install due to nginx directory change
Closed 4 months agoComments count1
bbb-install for 2.5 messes up greenlight
Closed 5 months agoComments count2
./bbb-install-2.5.sh: line 209: [: missing `]’
Closed 5 months agoComments count1
502 Bad Gateway (nginx) on fresh Ubuntu 18.04
Closed 9 months agoComments count9
Failed to install bbb 2.3: Error on building bbb-libreoffice docker image
Updated 6 months agoComments count11
Check for Apache’s installation should be a warning
Closed 6 months agoComments count1
Enable X-Content-Type-Options
Updated 6 months ago
Enable HSTS on https installations
Updated 6 months ago
Only install Greenlight
Updated 6 months agoComments count1
Error running wget -qO- command https://ubuntu.bigbluebutton.org/bbb-install.sh | bash -s — -v bionic-240 -s bbb.example.com -e info@example.com -a -w
Closed 6 months agoComments count5
Test installation
Closed 6 months agoComments count3
Does not receive an external ip address
Closed 6 months ago
Scalelite Recording Post Processing Dependencies missing
Updated 7 months ago
Enhance performance
Closed 7 months agoComments count3
Could not get lock; Docker did not install
Closed 7 months agoComments count4
404 Not Found nginx
Closed 10 months agoComments count1
Script installation is pointing on out of date TOMCAT Version
Closed 8 months agoComments count4
Running apt autoremove removes tomcat9
Updated 8 months agoComments count2
Wrong determination of local IP address
Updated 8 months agoComments count2
Install and use coTURN during BBB installation
Updated 8 months agoComments count1
Install coTURN with provided SSL certificate
Updated 8 months ago
Long options
Updated 8 months ago
Split counter-intuitive coTURN option `-c` into two options
Updated 8 months ago
Improve the detection of which BBB version to install
Updated 8 months ago
bbb-install-2.5 / [ERR] libpng not installed
Updated 8 months agoComments count4
Can’t build deb packages from a git worktree
Closed 9 months agoComments count1
File permission bbb-webrtc-sfu/production.yml
Closed 10 months agoComments count6
File permission error with bbb-install-2.5
Updated 10 months ago
Kurento key is needed?
Closed 10 months ago
2.5 install not allowing media
Closed 10 months agoComments count4
«You are now muted» sound in spanish?
Closed 10 months agoComments count1
Error with bbb-libreoffice-docker package
Closed a year agoComments count1