Ошибка 408 bigbluebutton

Hello to all

About 2 months after installing the new version of BigBlueButton on my dedicated server in Ubuntu 1804, I had no problem until today, but from today I encountered «app.error.408».
I followed instructions in GateHub, but I could not solve my problem
please help me

New release ‘20.04.3 LTS’ available.
Run ‘do-release-upgrade’ to upgrade to it.

Last login: Sun Feb 6 00:42:08 2022 from 46.167.141.56
root@server13:~# bbb-conf —check

BigBlueButton Server 2.3.17 (2525)
Kernel version: 4.15.0-163-generic
Distribution: Ubuntu 18.04.6 LTS (64-bit)
Memory: 9986 MB
CPU cores: 12

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

/etc/nginx/sites-available/bigbluebutton (nginx)
server_name: server13.lmsschool.ir
port: 80, [::]:80
port: 443 ssl

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

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

/usr/local/bigbluebutton/core/scripts/bigbluebutton.yml (record and playback)
playback_host: server13.lmsschool.ir
playback_protocol: https
ffmpeg: 4.2.4-1ubuntu0.1bbb2~18.04

/etc/bigbluebutton/nginx/sip.nginx (sip.nginx)
proxy_pass: 91.98.31.166
protocol: http

/usr/local/bigbluebutton/bbb-webrtc-sfu/config/default.yml (Kurento SFU)
kurento.ip: 91.98.31.166
kurento.url: ws://127.0.0.1:8888/kurento
kurento.sip_ip: 91.98.31.166
localIpAddress: 91.98.31.166
recordScreenSharing: true
recordWebcams: true
codec_video_main: VP8
codec_video_content: VP8

/usr/share/meteor/bundle/programs/server/assets/app/config/settings.yml (HTML5 client)
/etc/bigbluebutton/bbb-html5.yml (HTML5 client config override)
build: 1865
kurentoUrl: wss://server13.lmsschool.ir/bbb-webrtc-sfu
enableListenOnly: true
sipjsHackViaWs: true

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

Potential problems described below

Not running: Nginx tomcat8 or grails

Error: Unable to connect to the FreeSWITCH Event Socket Layer on port 8021

curl: (7) Failed to connect to server13.lmsschool.ir port 443: Connection refused
.curl: (7) Failed to connect to server13.lmsschool.ir port 443: Connection refused
.curl: (7) Failed to connect to server13.lmsschool.ir port 443: Connection refused
.^C
root@server13:~#

root@server13:# bbb-conf —status
nginx —————————————————► [✘ — inactive]
freeswitch ————————————► [✘ — failed]
redis-server ——————————► [✘ — deactivating]
bbb-apps-akka —————————► [✘ — failed]
bbb-fsesl-akka ————————► [✘ — failed]
tomcat8 ———————————————► [✘ — inactive]
mongod ————————————————► [✘ — inactive]
bbb-html5 —————————————► [✘ — inactive]
bbb-webrtc-sfu ————————► [✘ — inactive]
kurento-media-server ——► [✘ — inactive]
bbb-html5-backend@1 ———► [✘ — inactive]
bbb-html5-backend@2 ———► [✘ — inactive]
bbb-html5-frontend@1 ——► [✘ — inactive]
bbb-html5-frontend@2 ——► [✘ — inactive]
etherpad ——————————————► [✘ — inactive]
bbb-web ———————————————► [✘ — failed]
root@server13:#
I realized that the above should be active but I do not know how to do it

Describe the bug

/usr/share/meteor/bundle/programs/server/assets/app/config/settings.yml has html5ClientBuild: 1. As this is used for cache busting with the assets served by meteor, using BBB fails with some weird 408 error.

To Reproduce

1. Have 2.5.16
2. Upgrade to 2.5.17
3. See weird errors (408 authentication error)

Expected behavior
A client is served a valid sesssion

Actual behavior
Client receives 408 timeout error (authentication error) after waiting

Additional context
Release notes claim that the client version is 2912. After setting the client version to 2912 and rebooting, the service works as expeced

This is with a cluster proxy setup, but since we are not (yet) caching on the proxy nodes, this is probably a browser caching issue and might thus affect a wider field of installations.

Hotfiles (Ansible)

ansible -m lineinfile -a 'path=/usr/share/meteor/bundle/programs/server/assets/app/config/settings.yml regexp=" *html5ClientBuild: .*" line="    html5ClientBuild: 2919"' -i production --become --diff bbb-node.example.com

BigBlueButton is an opensource video conference software that is becoming increasingly popular during the COVID-19 period. Every day, millions of people take classes online. Users may encounter error codes such as 1001,1006,1007,1020… What does this mean? What should be checked and how should it be fixed?

The advantage of web-based software is that there is no need to download and install anything; simply use a browser, which is very convenient and compatible with all devices. However, the user must configure the browser correctly, and the developer must configure the server correctly as well. Otherwise, error messages will be displayed.

We’ve listed the majority of the most common error messages along with the code to make it easier for you to look up and understand what’s going on when those error messages appear.

1001: WebSocket disconnected — The WebSocket had connected successfully and has now disconnected. 

What need to check: 

• internet connection 

1002: Could not make a WebSocket connection — The initial WebSocket connection was unsuccessful. 

What need to check: 

• The firewall may block was protocol, 
• The server may go down or improperly configured

1003: Browser version not supported — Browser doesn’t implement the necessary WebRTC API methods. 

What needs to check: 

• Is it the latest version of Chrome, Firefox, or Safari? 

1004: Failure on call — The call was attempted, but failed. 

What needs to check: 

• A version of Freeswitch for BBB

1005: Call ended unexpectedly — The call was successful but ended without the user requesting to end the session.

What needs to check: 

• Server down 

1006: Call timed out — The library took too long to try and connect the call.

What needs to check: 

• Is it the latest version of Chrome, Firefox, or Safari? 

1007: ICE negotiation failed — The browser and FreeSWITCH try to negotiate ports to use to stream the media and that negotiation failed. 

What needs to check: 

• TURN Server configuration

1008: Call transfer failed — A timeout while waiting for FreeSWITCH to transfer from the echo test to the real conference. 

What needs to check: 

• FreeSWITCH Configuration 

1009: Could not fetch STUN/TURN server information 

What needs to check: 

• BigBlueButton Version
• Network 

1010: ICE negotiation timeout 

What needs to check: 

• Network 

1020: Media cloud could not reach the server 

 What needs to check:

• Is server overloaded

Those are common BigBlueButton error codes; I’m sure if you’re a BigBlueButton user, you’ve seen them at some point. Also, thanks to the BigBlueButton Developer Community, some of the data is from the official BigBlueButton development document. We listed it here and added some of our own thoughts and experiences to it. I just wanted to make it easier for you to look up that code and hope it helps you detect and fix the problem. If you want to learn more about BigBlueButton troubleshooting, you can visit the official development document at this link.

https://docs.bigbluebutton.org/2.2/troubleshooting.html#Troubleshooting_

If you require additional assistance in resolving those error messages, please contact us via the support channel.