error/bigbluebuttonbn/view error unable join: Difference between revisions
No edit summary |
|||
| (9 intermediate revisions by the same user not shown) | |||
| Line 6: | Line 6: | ||
If you have an auto hosted server, try going to the BigBlueButton server main page and see if you can join to the Demo Meeting. You should have access through a page like the one shown here: http://demo.bigbluebutton.org/ | If you have an auto hosted server, try going to the BigBlueButton server main page and see if you can join to the Demo Meeting. You should have access through a page like the one shown here: http://demo.bigbluebutton.org/ | ||
The plugin comes preconfigured for start using BigBlueButton out of the box. If you are not sure if your BigBlueButton server is working right, try using these credentials: | |||
URL: http://test-install.blindsidenetworks.com/bigbluebutton/ | |||
Secret: 8cd8ef52e8e101574e400365b55e11a6 | |||
'''2. The URL used in the configuration is not correct''' | '''2. The URL used in the configuration is not correct''' | ||
| Line 11: | Line 16: | ||
The URL must follow the format shown as example in the configuration page. This means that it should include the schema or protocol (http://), the domain and port (or hostname) should be valid and it should be solved from the server, and the path should end with a slash (/bigbluebutton/) | The URL must follow the format shown as example in the configuration page. This means that it should include the schema or protocol (http://), the domain and port (or hostname) should be valid and it should be solved from the server, and the path should end with a slash (/bigbluebutton/) | ||
http://test-install.blindsidenetworks.com/bigbluebutton/ | URL: http://test-install.blindsidenetworks.com/bigbluebutton/ | ||
'''3. The Shared Secret (aka Security Salt) used is not correct''' | '''3. The Shared Secret (aka Security Salt) used is not correct''' | ||
| Line 17: | Line 22: | ||
It is a common mistake not to use the correct Shared Secret. | It is a common mistake not to use the correct Shared Secret. | ||
You can retrieve the API | You can retrieve the API parameters (API endpoint and shared secret) using this command in your BigBlueButton server | ||
bbb-conf --secret | |||
You can find more references here http://docs.bigbluebutton.org/dev/api.html#api-security-model | |||
== Exceptions == | == Exceptions == | ||
| Line 27: | Line 32: | ||
Additionally you should verify that your Moodle server can communicate with the BigBlueButton server. You can do this by running this command in a terminal from your Moodle server. | Additionally you should verify that your Moodle server can communicate with the BigBlueButton server. You can do this by running this command in a terminal from your Moodle server. | ||
wget -qO- http://test-install.blindsidenetworks.com/bigbluebutton/api | wget -qO- http://test-install.blindsidenetworks.com/bigbluebutton/api | ||
you should be able to see the XML response in the console like this. | |||
<response><returncode>SUCCESS</returncode><version>0.9</version></response> | |||
<response><returncode>SUCCESS</returncode><version>0. | |||
Latest revision as of 14:58, 13 January 2016
Common cases
This error message is thrown when either of these three conditions occurs.
1. The BigBlueButton server is not available.
If you have an auto hosted server, try going to the BigBlueButton server main page and see if you can join to the Demo Meeting. You should have access through a page like the one shown here: http://demo.bigbluebutton.org/
The plugin comes preconfigured for start using BigBlueButton out of the box. If you are not sure if your BigBlueButton server is working right, try using these credentials:
URL: http://test-install.blindsidenetworks.com/bigbluebutton/ Secret: 8cd8ef52e8e101574e400365b55e11a6
2. The URL used in the configuration is not correct
The URL must follow the format shown as example in the configuration page. This means that it should include the schema or protocol (http://), the domain and port (or hostname) should be valid and it should be solved from the server, and the path should end with a slash (/bigbluebutton/)
URL: http://test-install.blindsidenetworks.com/bigbluebutton/
3. The Shared Secret (aka Security Salt) used is not correct
It is a common mistake not to use the correct Shared Secret.
You can retrieve the API parameters (API endpoint and shared secret) using this command in your BigBlueButton server
bbb-conf --secret
You can find more references here http://docs.bigbluebutton.org/dev/api.html#api-security-model
Exceptions
Additionally you should verify that your Moodle server can communicate with the BigBlueButton server. You can do this by running this command in a terminal from your Moodle server.
wget -qO- http://test-install.blindsidenetworks.com/bigbluebutton/api
you should be able to see the XML response in the console like this.
<response><returncode>SUCCESS</returncode><version>0.9</version></response>
