Invalid BigBlueButton Endpoint and Secret

[mamair]

Thanks für containerized BBB, because my server runs debian, not ubuntu ;-)

After installing BigBlueButton 2.3 container I get following error after login:

_Server Error
Invalid BigBlueButton Endpoint and Secret

Please make sure the proper steps have been taken. Learn more__

but the link goes only to the instruction for installing BBB on ubuntu server not the containerized BBB. My containerized BBB doesnt work with "bbb-conf --secret" (results - not surprising - in "command not found").

I cant find any instructions here about setting credentials at

Maybe its becaus I run behind a firewall, where the short instruction say, to manually set external IP for Kurento.

In the code example the device has the name ens3, but this seems not to be the name of my device. How can I find out the name of the prober device. With command "mount" I get a lot of "devices", which is the right one?

So what can I do?

Please help and give also instructrion in the setup guide here!

[mamair]

Just found issue #35 alangecker#35

I run debian 10

curl http://localhost:8080/bigbluebutton/api works well but not
curl https://yourhost.name/bigbluebutton/api

Strangely I can website with Browser with https and Letsencrypt-certificates work in my Browser

In logfile I find

fsesl-akka_1 | 2021-06-23T14:39:24.925Z WARN o.f.e.c.i.InboundClientHandler - connection timed out
fsesl-akka_1 | 2021-06-23T14:39:26.911Z ERROR o.b.f.v.f.ConnectionManager - Failed to connect to ESL
fsesl-akka_1 | 2021-06-23T14:39:29.909Z INFO o.b.f.v.f.ConnectionManager - Attempting to connect to FreeSWITCH ESL

webrtc-sfu_1 | 2021-06-23T15:47:52.512Z - error: [mcs-freeswitch-esl-wrapper] FreeSWITCH ESL connection received error ETIMEDOUT errno=-110, code=ETIMEDOUT, syscall=connect, address=10.7.7.1, port=8021
webrtc-sfu_1 | reconnect to server 0 100 undefined
webrtc-sfu_1 | reconnect to server 4 500 undefined
webrtc-sfu_1 | 2021-06-23T15:47:54.976Z - error: [mcs-balancer] Failed to connect to media server url=ws://kurento:8888/kurento, ip=, mediaType=undefined, retries=4685

free -h
total used free shared buff/cache available
Mem: 31Gi 10Gi 1.5Gi 407Mi 19Gi 19Gi
Swap: 4.0Gi 167Mi 3.8Gi

ulimit -a
-t: cpu time (seconds) unlimited
-f: file size (blocks) unlimited
-d: data seg size (kbytes) unlimited
-s: stack size (kbytes) 8192
-c: core file size (blocks) 0
-m: resident set size (kbytes) unlimited
-u: processes 127635
-n: file descriptors 1024
-l: locked-in-memory size (kbytes) 65536
-v: address space (kbytes) unlimited
-x: file locks unlimited
-i: pending signals 127635
-q: bytes in POSIX msg queues 819200
-e: max nice 0
-r: max rt priority 0
-N 15: unlimited

docker exec -it bbb-docker_core_1 bash -c 'ulimit -a' results in "Error: No such container: bbb-docker_core_1"

hm, with "docker-compose up -d" I got no problem, all containers running up:

bbb-docker_kurento_1 is up-to-date
bbb-docker_jodconverter_1 is up-to-date
bbb-docker_postgres_1 is up-to-date
bbb-docker_redis_1 is up-to-date
bbb-docker_mongodb_1 is up-to-date
bbb-docker_freeswitch_1 is up-to-date
bbb-docker_prometheus-exporter_1 is up-to-date
bbb-docker_greenlight_1 is up-to-date
bbb-docker_webhooks_1 is up-to-date
bbb-docker_fsesl-akka_1 is up-to-date
bbb-docker_bbb-web_1 is up-to-date
bbb-docker_webrtc-sfu_1 is up-to-date
bbb-docker_apps-akka_1 is up-to-date
bbb-docker_etherpad_1 is up-to-date
bbb-docker_periodic_1 is up-to-date
bbb-docker_html5-frontend-2_1 is up-to-date
bbb-docker_html5-frontend-1_1 is up-to-date
bbb-docker_html5-backend-1_1 is up-to-date
bbb-docker_nginx_1 is up-to-date

but there ist no bbb-docker_core_1 !!! VERY STRANGE

cat /proc/sys/kernel/threads-max 255270

cat /proc/loadavg
0.59 0.74 0.81 1/2505 31716