Group sessions (breakout rooms) did not open after creating them

[Stefanie Klicks]

Dear All, I need some advise of yours as a had a technical problem yesterday with a group of 12 participants. I wanted to open group rooms / breakout sessions and could open as moderator. 

But after pressing the "create" button - nothing happend and the participants do not get an option to join a group room. 

Just nothing happend and no group rooms opened. 

This also took place after all of us registered and entered newly to BBB.

Does anybody of you has an idea what the problem could be?

In other ocasions it was always possible with the group rooms and I also have had moderator rights.

Thanks for your advise or ideas on this and regards,

Stefanie

[anton.g...@blindsidenetworks.com]

Hi Stefanie,

Could you please share the version of BigBlueButton you are using? (in the client check the About option under the Settings trigger)

Are you able to reproduce this consistently? If yes, could you please try to reproduce while the client language is English?

Anton

[Stefanie Klicks]

Dear Anton,

yes the failure occured also a day after.

My version is:

2.7.16

May it be that it makes a difference whether I use Edge as Browser or Chrome or Firefox?

Regards and thanks,

Steffi

[anton.g...@blindsidenetworks.com]

Hi Steffi,

I am trying to reproduce the issue so any info could help. Please share which browser(s) may have been related to the issue.

Do you know if the viewers see this portion in the interface? (check screenshot)

Also, are you able to reproduce it on the test server we have for BBB 2.7.16 ?

https://test27.bigbluebutton.org/

Anton

[Stefanie Klicks]

Dear Anton,

the users did not see see section after I as host pressed the button of creating the breakout rooms. The section on the left side (above users) of your screenshot just did not show up. Also not for me as moderator.

I use the edge browser. Has this maybe been the mistake?

In another call I could create rooms but not sending the users - they only could chose their own room. Even I did not press the button of "users can chose individually which room" - they still could do it after I created the rooms.

(chrome browser)

Very wired problem which I have also never had before...

Thanks for thinking with me.

Regards

Steffi

[che...@vikasglobal.net]

Hii All

If anybody can tell us why we are getting this below error

2025/01/20 06:57:15 [error] 21256#21256: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 202.83.16.106, server: www.medetel.in, request: "GET / HTTP/2.0", upstream: "http://127.0.0.1:5050/", host: "medetel.in"

2025/01/20 07:00:09 [error] 21256#21256: *11 connect() failed (111: Connection refused) while connecting to upstream, client: 135.181.85.71, server: www.medetel.in, request: "GET / HTTP/2.0", upstream: "http://127.0.0.1:5050/", host: "medetel.in"

2025/01/20 07:02:39 [error] 21256#21256: *14 connect() failed (111: Connection refused) while connecting to upstream, client: 5.181.190.248, server: www.medetel.in, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:5050/", host: "216.48.186.187:443"

 

I have opened 5050 port, restarted nginx service,checked the nginx.config file

 

 

server {

  listen 80;

  listen [::]:80;

  server_name www.medetel.in;

 

  location ^~ / {

    return 301 https://$server_name$request_uri; #redirect HTTP to HTTPS

  }

 

  location ^~ /.well-known/acme-challenge/ {

    allow all;

    default_type "text/plain";

    root /var/www/bigbluebutton-default/assets;

  }

 

  location = /.well-known/acme-challenge/ {

    return 404;

  }

}

 

set_real_ip_from 127.0.0.1;

real_ip_header proxy_protocol;

real_ip_recursive on;

server {

  # this double listening is intended. We terminate SSL on haproxy. HTTP2 is a

  # binary protocol. haproxy has to decide which protocol is spoken. This is

  # negotiated by ALPN.

  #

  # Depending on the ALPN value traffic is redirected to either port 82 (HTTP2,

  # ALPN value h2) or 81 (HTTP 1.0 or HTTP 1.1, ALPN value http/1.1 or no value)

 

  listen 127.0.0.1:82 http2 proxy_protocol;

  listen [::1]:82 http2;

  listen 127.0.0.1:81 proxy_protocol;

  listen [::1]:81;

  server_name www.medetel.in;

 

  # nginx does not know its external port/protocol behind haproxy, so use relative redirects.

  absolute_redirect off;

 

  # HSTS (uncomment to enable)

  #add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;

 

  access_log  /var/log/nginx/bigbluebutton.access.log;

 

  # This variable is used instead of $scheme by bigbluebutton nginx include

  # files, so $scheme can be overridden in reverse-proxy configurations.

  set $real_scheme "https";

 

  # BigBlueButton landing page.

  location / {

    root   /var/www/bigbluebutton-default/assets;

    try_files $uri @bbb-fe;

  }

 

  # Include specific rules for record and playback

  include /etc/bigbluebutton/nginx/*.nginx;

--
You received this message because you are subscribed to the Google Groups "bigbluebutton-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bigbluebutton-users/0f063c97-ca63-4fa9-9e92-b1f852c7b796n%40googlegroups.com.