I am doing tests with Moodle 3.4 and the last version of BigBlueButton is in principle installed and configured the activity, but when I try to access this error message appears.
"Bigbluebuttonbn / A meeting already exists with that meeting ID. Please use a different meeting ID. "
Can you explain to me what I'm doing wrong?
...the same for me...
The message is coming from BigBlueButton.
Is this happening every time you join a meeting? Are you using test-install as your BBB server?
Also, can you tell what version of the plugin are you using?
Is this happening every time you join a meeting? YES
Are you using test-install as your BBB server? YES
Also, can you tell what version of the plugin are you using? Moodle 3.4 & BBB 2.2-beta
Moodle 3.3 - BBB 2.2 on a différent server ubuntu 16.04
First message when i try the activity conf room: "You either did not supply a password or the password supplied is neither the attendee or moderator password for this conference."
Then, when i try again: "bigbluebuttonbn/A meeting already exists with that meeting ID. Please use a different meeting ID."
It is happening every time.
I don't know what is "test-version"
Thank you !
I have installed the BBB Version 1.1.0 on my own server and I have configured my Moodle 3.4 with the version of the 2.2 beta plugin, if I try an entry directly to the BBB if it works and I can make a video conference without problems, but when I want to enter from Moodle I see this error message.
Looking at the BBB LOG I see that when creating the videoconference it uses a password, but I have not seen any place where I can enter a password to access as a moderator or as a listener.
All right guys, with those last messages I see where the problem is.
The first thing I have to tell you is that things can be faster if you provide the right versions when asking for help. In this case, along with the 2.2-beta (which doesn't tell much really) there is a 10 digits number. That is the one we really use to identify issues particularly related to a version.
I am assuming you guys had 2017101002 (that may have been the first report).
The issue you have now is telling me that you either have 2017101003 or 2017101004.
Thanks, with this version it works perfectly. I am in test mode, I can update it at any time, I will soon update to version 2017101005
Thank you very much Jesus Frederico...it works perfectly with the ...04 !