get API URL and key

[mokkin]

I'd like to connect BBB to Nextcloud via https://github.com/sualko/cloud_bbb

Is there a way to get the URL and secret via bb-conf --secret as described even in the docker environment?

[alangecker]

the URL is always https://yourdomain.org/bigbluebutton/api and the secret/key is stored as SHARED_SECRET inside the .env file ;)

[mokkin]

I supposed the SHARED_SECRET could be the key, but with the URLs I am not lucky :(

I tried https://bbb.example.de/bigbluebutton/api https://bbb.example.de/api https://bbb.example.de/b/bigbluebutton/api https://bbb.example.de/b/api but the answer is always:

[qroac]

I had the same riddle.
According to docs of the NC integration, I tried https://bbb.mydoma.in/bigbluebutton, without trailing api, and it works :)

[mokkin]

Now with 2.3 the NC integration is working - at least for us. If @qroac can acknowledge this, we can close the issue.

[qroac]

Using the url path without trailing /api/ already worked on my server at the time of my comment ;)

[ZelphirKaltstahl]

What is not clear to me is: How do I get the BIGBLUEBUTTON_SECRET mentioned at https://docs.bigbluebutton.org/greenlight/gl-install.html#setting-bigbluebutton-credentials of my own setup? Is it the same as SHARED_SECRET in the .env file then?

the URL is always https://yourdomain.org/bigbluebutton/api and the secret/key is stored as SHARED_SECRET inside the .env file ;)

This makes it sound like they are the same.

Edit: Even if I set those 2 values in my .env file:

# no /api at the end as per comment in this issue
BIGBLUEBUTTON_ENDPOINT=https://mysubdomain.mydomain.com/bigbluebutton
# copied from SHARED_SECRET
BIGBLUEBUTTON_SECRET=some_secret here

and running docker-compose up -d, I still get to see this:

[rottaran]

@ZelphirKaltstahl: This may not be caused by the shared key. I get this error message when the greenlight container cannot connect to the respective bbb container. greenlight needs to access https://mysubdomain.mydomain.com/bigbluebutton. Without extra settings, this is translated to your public IP address, but the docker container cannot connect to that.

Solution depends on how you set up your http frontend. bbb-docker's template has the nginx frontend as network:host. I am not sure why this is sufficient. If your nginx frontend is just a container with the usual port binding for 80 and 443 the following setup will work. 172.17.0.1 is docker's host-gateway and yes it is fine to bind ports to that.

services:
  frontend:
    build: nginx # or something elso
    ports:
      # expose to outside
      - $(EXTERNAL_IP):80:80
      - $(EXTERNAL_IP):443:443
      # make accessible to other docker containers, likely there is a better way
      - 172.17.0.1:80:80
      - 172.17.0.1:443:443
   # ...and other settings

and to all bbb-docker services I have added a /etc/hosts entry. This translates your public server name to the internal IP address:

    extra_hosts:
      - ${DOMAIN}:host-gateway

Maybe there is a more elegant solution.

[astral0pitek]

I downloaded this docker compose project, made all steps of setup and run docker compose. As the fact I have not working rooms in Greenlight and not working link https://my.domain/bigbluebutton/api.

I watched your issues and this problem happening permanently since 2021 year!!! Just wtf? Why this problem still happening?

[yurikoles]

I watched your issues and this problem happening permanently since 2021 year!!! Just wtf? Why this problem still happening?

May I ask your IBAN number? I can't find you in our paid customers list.

[yurikoles]

@alangecker offensive language ^^^.