-
Notifications
You must be signed in to change notification settings - Fork 33
Invalid BigBlueButton Endpoint and Secret #35
Comments
maybe check following:
if yes to all, than BBB is running fine -> the problem lies at greenlight itself. |
Yes I think everything is running:
It seems to be that the BBB API is not reachable:
|
Actually, the webhooks container doesn't seem to be running on your machine. With your setup it should be called "bbb-docker_webhooks_1". Had a similar issue a while ago, that the webhook container kept restarting and there was a duplicate line in one of the configs (mod/webhooks/config.yml). |
Hey, so I made a cheout on the develop branch. Made a deleted the .env file and made a I am still on this list:
the difference is that now when I navigate to my URL I get a 502 Bad Gateway, so its getting worse... |
still no "bbb-docker_webhooks_1" .. did you set the flag in den .env file? bigbluebutton-docker/sample.env Line 20 in 8b921bc
|
@cjhille probably the webhooks are disabled. most people won't need them, so can also be intended ;)
|
@alangecker I should really read the issues more carefully. I was somehow convinced that the "Endpoint and Secret" issue was referring to webhooks and an obviously unrelated error message I encountered. Sorry |
./scripts/compose logs core | grep bbb-web
Whats stange is that I deleted the images manually and made a new setup. And end up the the 502 Gateway error. When I reinstall the whole server and build everything I at least get to open greenlight. |
Ok nevermind greenlight is running again and Im back at:
|
there are quite a lot of how much RAM do you have? 😄 (you can check the total and free amount with |
Should have 16GB Maybe docker can't use it all?
|
okay, thats wird. which OS do you use and are there other services running on that machine? could you send us the output of following commands:
there is a nice guide about debugging this error: |
It's an Ubuntu 18.04 V-Server
Current count 2524 I had the html5 version running once, when I switched from 18.04 to 16.04 problem is, that docker is not supported when installing Ubuntu 16.04 so greenlight wasn't working well, I was able to install greenlight with rubyOnRails and without the docker once and the whole thing worked but only for a short time (tried to open some ports and everything went down from there it lost the rails version etc). So the server is technically able to host BBB. |
@PeerConradi provided me with ssh access, so I could have a look into it:
Seems like it isn't a direct issue of BBB / bbb-docker. maybe ubuntu 18.04 (which is used here) has some wired settings? Would still be nice to understand the issue, but currently I'm not able to do that. |
So I installed Debian 10 now. Back at the same issue: Compose ps
root@h2868180:~/bbb-docker# ./scripts/compose logs core | grep bbb-web
|
I had exactly the same problem. My Server was behind a NAT so I had to add to the server the public ip address to the same interface. see https://github.com/alangecker/bigbluebutton-docker/blob/v2.2.x/docs/behind-nat.md |
I had the same problem. domain.net/bigbluebutton/api is not accessible. I tracked this down into the core docker. If I ran:
Port 8090 wasn't in use (the port nginx forwards to). After switching from branch v2.2.x to v2.2.22 and then to v2.2.24 and running the "./scripts/upgrade" script the problem disappeared. I am still not sure what caused this as I ran into this problem a few times with a clean ubuntu 16.04 installation |
Thanks @devluz . That also did the trick for me. |
I had the same problem and port 8090 wasn't in use in bb-docker_core. Switching to v2.2.24 branch and running "./scripts/upgrade" fixed the problem. Host OS: Centos 8 |
I can also confirm that |
@goekce, @mghadam, @jwijffels and @devluz |
/bbb-docker# curl http://localhost:8080/bigbluebutton/api Server Error Server Rooms: |
docker run --rm --env-file .env bigbluebutton/greenlight:v2 bundle exec rake conf:check Tasks: TOP => conf:check => environment (See full trace by running task with --trace) |
I think this is the same as #18 but the answer:
"It was a DNS Mapping error" was not very helpful.
I have a clean Ubuntu 18.04 and just followed the tutorial (haven't changed the secrets) and ran into this error.
then I made a decompose changed the secrets inside the .env file and made another compose, same issue.
The text was updated successfully, but these errors were encountered: