Moodle 4.0 setup out of the box gets a "unable to enter the room" error

[jacke...@gmail.com]

First use on Moodle 4.0 on a managed host. Also tested with another installation fresh out of the box and I get the same error. Following this guide https://docs.moodle.org/30/en/error/bigbluebuttonbn/view_error_unable_join

Step 1 : I try running the test server and everything works fine. Room launches with no issues.

Step 2 : The URL I am using is a direct copy/paste straight off the guide and also exactly matches the Moodle default value, including the trailing slash. I tried both the http and the https versions just in case. Strangely enough, going to the same URL in a web browser results in a 404 error so I have a feeling that the system default webpage may be wrong somehow.

Step 3: This part is a bit confusing to me. As far as I understand, since Moodle core uses a 'beginner level' free account from blindside network, I do not have access to the server directly. bbb-conf is running on the blindside networks host, not on my own host? Right? If thats is the case, there I do not think I have any way of resetting the salt.

Step extra : running the wget for the test server returns success. But running wget with the default value in Moodle returns nothing. This leads me further into thinking that the out-of-the-box setup on Moodle that is suppose to connect automatically to blindside networks is wrong

Checking blindside network I see lots of information about how it is now part of the core function of moodle since version 4.0 has launched, but it makes no mention of any "due to overwhelming demand, our free service is temporally suspended" or any mention of the URL changing. Checking other forum posts on Moodle.org it seems as if everyone else is able to conect just fine right out of the box by just using the system defaults. No mention from anyone else of not being able to enter a room when the defaults are used.

For the moment, there is no critical deadline. I am just checking to be sure I am set up to use for classes in Spring semester. But I would like to figure this out sooner rather than later.

[Mark Ginter]

I'm getting the same error - I have two moodle sites on the same server.  One connects to bbb fine - the other gives this error.  Site/key info in both of their settings are identical.  Kind of at a loss.

[sd...@distancelearning.cloud]

Just installed 4.1 bitnami moodle in ec2 and access to https://test-moodle.blindsidenetworks.com/bigbluebutton/

Worked with recordings appearing as they should.

 

Not sure if the same secret is used for every moodle, mine ends in “ae34”

 

Also, Are you pointing at your own BBB server, If so what version BBB.  If you have access to your bbb server, you can look in the bbbserver nginx logs to see what your moodle is sending to bbb,

 

>cat /var/log/nginx/bigbluebutton.access.log  to see the create call.  Sometimes the / or api is missing, or a typo is causing the meeting to not create.

And that causes the moodle  "unable to enter the room" error.

 

Regards,

Stephen

--
You received this message because you are subscribed to the Google Groups "BigBlueButton-Setup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-s...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bigbluebutton-setup/2e5a25cf-e8ad-493d-a2d9-c82110c9b052n%40googlegroups.com.

[Mark Ginter]

Thanks!  I'll look into that - I am hosting my own.  Oddly enough - I wanted to see what error messages might be present in moodle - so I went to the Development --> Debugging (in Moodle) and set it to Normal and it started working.  Then I turned off debugging and it gave the "cannot connect" error again.  I'll look back into it as soon as I have a chance.