- Error 1007 ICE. Failed joining audio conf. #8418
- Comments
- ikaikai commented Dec 12, 2019 •
- Bigbluebutton не работает микрофон 1007
- Introduction
- Recording
- Recording not processing after upgrading
- Kurento
- WebRTC video not working with Kurento
- Unit kurento-media-server.service is masked
- Unable to share webcam
- FreeSWITCH
- Configure BigBluebutton/FreeSWITCH to support IPV6
- FreeSWITCH fails to bind to IPV4
- Forward calls from an Asterisk server to FreeSWITCH
- Changes to your Asterisk server
- Changes to your BigBlueButton/FreeSWITCH server
- FreeSWITCH fails to bind to port 8021
- FreeSWITCH fails to start with a SETSCHEDULER error
- Users not able to join Listen Only mode
- Unable to connect using fs_cli
- Echo test hangs upgrading BigBlueButton 2.2
- FreeSWITCH using default stun server
- HTML5 Server
- bbb-html5 fails to start with a SETSCHEDULER error
- Installation and packages
- The following packages have unmet dependencies
- No Symbolic Link
- Package install fails with sed error
- Errors with packages
- WebRTC errors (1001, 1002,…)
- Networking
- Server running behind NAT
- Could not get your microphone for a WebRTC call
- The browser is not supported
- Tomcat shows “Cannot assign requested address on startup”
- nginx not running
- “Welcome to nginx”
- bbb-web
- 404 Error when loading the client
- Blank presentation area on create or upload
- Unable to create presentation
- Too many open files
- bbb-web takes a long time to startup
- Error installing bbb-web
- Other errors
- Root partition too small
- BigBlueButton does not load
- Running within an LXD Container
- Unable to connect to redis
- 500 Internal Server Error
- Legacy errors
- Conference not found errors
Error 1007 ICE. Failed joining audio conf. #8418
Comments
ikaikai commented Dec 12, 2019 •
[11:41:24:0464] INFO: clientLogger: Audio call session accepted InviteClientContext.p (https://class.demos.cloud/html5client/23acf17a7f66feccb643e681b6de9fd0361d4c3a.js?meteor_js_resource=true:125:1167498)
sip.js?v=815:1272 SIP.EventEmitter#off is deprecated and may be removed in future SIP.js versions.
Please use removeListener or removeAllListeners instead.
See here for more details:
http://nodejs.org/api/events.html#events_emitter_removelistener_event_listener
off @ sip.js?v=815:1272
p @ 23acf17a7f66feccb643e681b6de9fd0361d4c3a.js?meteor_js_resource=true:125
EventEmitter.emit @ sip.js?v=815:115
accepted @ sip.js?v=815:5641
onSuccess @ sip.js?v=815:6854
(anonymous) @ 23acf17a7f66feccb643e681b6de9fd0361d4c3a.js?meteor_js_resource=true:1
Promise.then (async)
n.then @ 23acf17a7f66feccb643e681b6de9fd0361d4c3a.js?meteor_js_resource=true:21
receiveInviteResponse @ sip.js?v=815:6835
receiveResponse @ sip.js?v=815:3784
InviteClientTransaction.receiveResponse @ sip.js?v=815:7835
onMessage @ sip.js?v=815:8569
ws.onmessage @ sip.js?v=815:8427
sip.js?v=815:2900 Thu Dec 12 2019 11:41:29 GMT+0800 (中国标准时间) | sip.invitecontext.mediahandler | RTCIceChecking Timeout Triggered after 5000 milliseconds
23acf17a7f66feccb643e681b6de9fd0361d4c3a.js?meteor_js_resource=true:9 [11:41:39:0496] ERROR: clientLogger: ICE connection failed before success MediaHandler.g (https://class.demos.cloud/html5client/23acf17a7f66feccb643e681b6de9fd0361d4c3a.js?meteor_js_resource=true:125:1168708)
sip.js?v=815:1272 SIP.EventEmitter#off is deprecated and may be removed in future SIP.js versions.
Please use removeListener or removeAllListeners instead.
See here for more details:
http://nodejs.org/api/events.html#events_emitter_removelistener_event_listener
off @ sip.js?v=815:1272
(anonymous) @ 23acf17a7f66feccb643e681b6de9fd0361d4c3a.js?meteor_js_resource=true:125
g @ 23acf17a7f66feccb643e681b6de9fd0361d4c3a.js?meteor_js_resource=true:125
EventEmitter.emit @ sip.js?v=815:112
peerConnection.oniceconnectionstatechange @ sip.js?v=815:11580
sip.js?v=815:1272 SIP.EventEmitter#off is deprecated and may be removed in future SIP.js versions.
Please use removeListener or removeAllListeners instead.
See here for more details:
http://nodejs.org/api/events.html#events_emitter_removelistener_event_listener
off @ sip.js?v=815:1272
(anonymous) @ 23acf17a7f66feccb643e681b6de9fd0361d4c3a.js?meteor_js_resource=true:125
(anonymous) @ 23acf17a7f66feccb643e681b6de9fd0361d4c3a.js?meteor_js_resource=true:125
exitAudio @ 23acf17a7f66feccb643e681b6de9fd0361d4c3a.js?meteor_js_resource=true:125
d @ 23acf17a7f66feccb643e681b6de9fd0361d4c3a.js?meteor_js_resource=true:125
l @ 23acf17a7f66feccb643e681b6de9fd0361d4c3a.js?meteor_js_resource=true:125
g @ 23acf17a7f66feccb643e681b6de9fd0361d4c3a.js?meteor_js_resource=true:125
EventEmitter.emit @ sip.js?v=815:112
peerConnection.oniceconnectionstatechange @ sip.js?v=815:11580
sip.js?v=815:2900 Thu Dec 12 2019 11:41:39 GMT+0800 (中国标准时间) | sip.inviteclientcontext | terminating Session
sip.js?v=815:2900 Thu Dec 12 2019 11:41:39 GMT+0800 (中国标准时间) | sip.transport | sending WebSocket message:
BYE sip:919667998@44.228.244.151:5060;transport=udp SIP/2.0
Via: SIP/2.0/WSS 33jndlprjgjs.invalid;branch=z9hG4bK5167729
Max-Forwards: 70
To: sip:919667998@class.demos.cloud;tag=75vDUmHFpe78F
From: «w_5sia44tmkbqy_9-bbbID-Tiankai» sip:w_5sia44tmkbqy_9-bbbID-Tiankai@class.demos.cloud;tag=86ejcjj0gc
Call-ID: 6084n2qs56sqd3loqlrh
CSeq: 5768 BYE
Supported: outbound
User-Agent: BigBlueButton
Content-Length: 0
sip.js?v=815:2900 Thu Dec 12 2019 11:41:39 GMT+0800 (中国标准时间) | sip.inviteclientcontext | closing INVITE session 6084n2qs56sqd3loqlrhs31fkqc5q2
sip.js?v=815:2900 Thu Dec 12 2019 11:41:39 GMT+0800 (中国标准时间) | sip.invitecontext.mediahandler | closing PeerConnection
The text was updated successfully, but these errors were encountered:
Источник
Bigbluebutton не работает микрофон 1007
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
You can resolve the errors with the following command
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 , as in
Kurento
WebRTC video not working with Kurento
Check the value for /proc/sys/net/ipv4/tcp_syncookies that it contains the value 1 .
If not, edit /etc/sysctl.conf and set the value for net.ipv4.tcp_syncookies to 1 .
Save the file and restart.
Unit kurento-media-server.service is masked
If sudo bbb-conf —check returns the warning
You can unmask Kurento using the command
Unable to share webcam
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.
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:
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:
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.
If you see these errors, clear the FreeSWITCH database (BigBlueButton doesn’t use the database and FreeSWITCH will recreate it on startup).
Forward calls from an Asterisk server to FreeSWITCH
Let’s assume the following:
Changes to your Asterisk server
Setup your gateway to BigBlueButton/FreeSWITCH. in /etc/asterisk/sip.conf add
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.
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.
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
To debug, try connecting to FS CLI and increase logging level. Once connected, make your call and see what the logs say.
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
it might be that your server has IPV6 disabled (or does not support it). You can check this by running the following command
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
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
and then restart BigBlueButton with the commands
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
If you see SETSCHEDULER in the error message, edit /lib/systemd/system/freeswitch.service and comment out the line containing CPUSchedulingPolicy=rr (round robin)
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
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:
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:
You should see an output such as
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.
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.
We also added /usr/local/bin/fs_clibbb with the contents
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 .
If you upgraded using manual steps, be sure to do ao sudo bbb-conf —setip 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
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
You can add a line in /etc/bigbluebutton/bbb-conf/apply-conf.sh to always apply this value even if the FreeSWITCH package upgrades.
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
You can override this with creating the following directory
and creating /etc/systemd/system/bbb-html5.service.d/override.conf with the following contents
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 :
To solve this, add a symbolic link to nginx for the BigBlueButton site:
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
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
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
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,
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 open the following page https://test.bigbluebutton.org/html5client/useragent with the browser, which will print its useragent string. For example, with the Vivaldi browser you might see
Next, to add this as a supported browser, append to settings.yml
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
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
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
and look for the output of
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
“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 .
If not, do the following
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
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
To resolve, create an override file that increases the number of open files for bbb-web
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
Error installing bbb-web
If you get the following error during upgrade to BigBlueButton
Then first uninstall 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 .
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.
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
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.
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
Then enter the following commands to load the new unit file and restart BigBlueButton.
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
you can add overrides for these three packages to ensure they start after redis.server. Run the following script.
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
Источник