Note: You are currently viewing documentation for Moodle 3.1. Up-to-date documentation for the latest stable version of Moodle is probably available here: error/local hub/cannotregisternotavailablesite.

error/local hub/cannotregisternotavailablesite: Difference between revisions

From MoodleDocs
(New page: To register to a hub your Moodle site needs to be accessible by the hub so the two can communicate bi-directionally. Usually this error occurs when your Moodle site has a localhost addres...)
 
mNo edit summary
 
(7 intermediate revisions by 5 users not shown)
Line 1: Line 1:
To register to a hub your Moodle site needs to be accessible by the hub so the two can communicate bi-directionally.
To register with a hub your Moodle site needs to be accessible by the hub so the two can communicate with one another.


Usually this error occurs when your Moodle site has a localhost address or is protected by a proxy or firewall.
The error indicates that the hub could not reach your site. Most often this is because your site is not online, but only exists on your computer.
 
Reasons why you may have seen this error:
 
# Your site has a local address like http://localhost or http://127.0.0.1 - in other words, your site is not on the internet so Moodle cannot see it.
# Your site is protected by a proxy or firewall  
# The hub is being prevented in some other way from accessing your site - for example you have restrictions on certain IP addresses, one of which might be the hub.
 
 
[[Category:Error|Hub]]
[[es:error/local hub/cannotregisternotavailablesite]]

Latest revision as of 19:46, 6 June 2015

To register with a hub your Moodle site needs to be accessible by the hub so the two can communicate with one another.

The error indicates that the hub could not reach your site. Most often this is because your site is not online, but only exists on your computer.

Reasons why you may have seen this error:

  1. Your site has a local address like http://localhost or http://127.0.0.1 - in other words, your site is not on the internet so Moodle cannot see it.
  2. Your site is protected by a proxy or firewall
  3. The hub is being prevented in some other way from accessing your site - for example you have restrictions on certain IP addresses, one of which might be the hub.