error/bigbluebuttonbn/view error unable join: Difference between revisions
(Created page with "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...") |
No edit summary |
||
| Line 1: | Line 1: | ||
== Common cases == | |||
This error message is thrown when either of these three conditions occurs. | This error message is thrown when either of these three conditions occurs. | ||
1. The BigBlueButton server is not available. | '''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/ | 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/ | ||
2. The URL used in the configuration is not correct | '''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/) | 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/) | ||
| Line 11: | Line 13: | ||
http://test-install.blindsidenetworks.com/bigbluebutton/ | 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''' | ||
It is a common mistake not to use the correct Shared Secret. | |||
You can retrieve the API paramters (API endpoint and shared secret) using the command | |||
bbb-conf --secret | |||
You can find more references here https://code.google.com/p/bigbluebutton/wiki/API#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. | 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. | ||
Revision as of 18:46, 10 October 2014
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/
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/)
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 paramters (API endpoint and shared secret) using the command bbb-conf --secret
You can find more references here https://code.google.com/p/bigbluebutton/wiki/API#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. <response><returncode>SUCCESS</returncode><version>0.81</version></response>
