System health check - Revision history

Antonio: /* Joomla URL seems to be misconfigured in Joomdle auth plugin in Moodle */

2019-10-28T16:27:09Z

Joomla URL seems to be misconfigured in Joomdle auth plugin in Moodle

← Older revision		Revision as of 16:27, 28 October 2019
Line 71:		Line 71:
	* Check Joomla multi-language configuration and enter appropiate parameters in Moodle side if necessary		* Check Joomla multi-language configuration and enter appropiate parameters in Moodle side if necessary
	* Check any mod_security rules that may deny XMLRPC traffic		* Check any mod_security rules that may deny XMLRPC traffic
	* Disable any Joomla security extensions you may have installed		* Disable any Joomla security extensions you may have installed and test
			** If it works, you should whitelist site IP address in your security extension and enable it back
	* Disable any Joomla SEF extensions you may have		* Disable any Joomla SEF extensions you may have

Antonio: /* Joomdle Web Services */

2018-06-07T07:12:09Z

Joomdle Web Services

← Older revision		Revision as of 07:12, 7 June 2018
Line 48:		Line 48:
	===It seems the Joomdle auth plugin is not enabled in Moodle===		===It seems the Joomdle auth plugin is not enabled in Moodle===
	You must enable the Joomdle auth plugin in Moodle Admin->Users->Authentication->Manage Authentication.		You must enable the Joomdle auth plugin in Moodle Admin->Users->Authentication->Manage Authentication.

	~~===Moodle networking is not enabled===~~
	~~You must enable Moodle Networking in Moodle Admin->Networking->Settings~~

	~~===You need to add your site IP to Moodle XML-RPC trusted hosts list===~~
	~~You must add your site IP to the Moodle trusted XML-RPC hosts list, in Moodle Admin->Networking->XML-RPC Hosts~~

	===Something is wrong with Joomdle Web Services setup===		===Something is wrong with Joomdle Web Services setup===
Line 109:		Line 103:
	For example, my local configuration is:		For example, my local configuration is:
	error_reporting = E_ALL & ~E_DEPRECATED		error_reporting = E_ALL & ~E_DEPRECATED


	=Raw replies=		=Raw replies=

Antonio at 21:58, 13 March 2018

2018-03-13T21:58:29Z

← Older revision		Revision as of 21:58, 13 March 2018
Line 131:		Line 131:


	Miloud, a Joomdle user, also contributes this information about Apache's mod_pagespeed:		Miloud, a Joomdle user, also contributes this information about Apache's mod_pagespeed for Joomdle versions < 1.2:

	In case anybody having similar <head /> problem the fix is very simple, but kind of hidden and some how seems not realted, but it is the casue of the problem.		In case anybody having similar <head /> problem the fix is very simple, but kind of hidden and some how seems not realted, but it is the casue of the problem.

Antonio: /* Raw replies */

2018-02-14T16:52:04Z

Raw replies

← Older revision		Revision as of 16:52, 14 February 2018
Line 136:		Line 136:

	This problem was caused by Apache cache. So in httpd.conf there is :		This problem was caused by Apache cache. So in httpd.conf there is :

	Include conf/pagespeed.conf		Include conf/pagespeed.conf

	Include conf/pagespeed_libraries.conf		Include conf/pagespeed_libraries.conf

	If not commented just comment them and restart Apache or your server.		If not commented just comment them and restart Apache or your server.
	~~# Include conf/pagespeed.conf~~
	~~# Include conf/pagespeed_libraries.conf~~

Antonio: /* Raw replies */

2018-02-14T16:48:19Z

Raw replies

← Older revision		Revision as of 16:48, 14 February 2018
Line 118:		Line 118:
	* joomla_folder/logs/joomdle_system_check.xml		* joomla_folder/logs/joomdle_system_check.xml
	* moodledata_folder/temp/joomdle_system_check.xml		* moodledata_folder/temp/joomdle_system_check.xml


			If you have errors in system check, you should check these files.

			You need to read them carefully, looking for unwanted tags, code, etc.
			For example, you may find an HTML "<head>" tag in the XML file.


			If you find any wrong tags, not belonging to XML, in the file in moodledata folder, you should check your Joomla installation:
			* Try changing front end template for a moment and run system check again. If it solves the issue, it indicates some problem with the HTML generated by the template
			* Try disabling any non-core plugins, starting with those of type "system"


			Miloud, a Joomdle user, also contributes this information about Apache's mod_pagespeed:

			In case anybody having similar <head /> problem the fix is very simple, but kind of hidden and some how seems not realted, but it is the casue of the problem.

			This problem was caused by Apache cache. So in httpd.conf there is :
			Include conf/pagespeed.conf
			Include conf/pagespeed_libraries.conf

			If not commented just comment them and restart Apache or your server.
			# Include conf/pagespeed.conf
			# Include conf/pagespeed_libraries.conf

Antonio at 17:58, 27 October 2016

2016-10-27T17:58:10Z

← Older revision		Revision as of 17:58, 27 October 2016
Line 22:		Line 22:
	{{End of Section}}		{{End of Section}}

	~~==Joomla Web Services (J1.5 only)==~~
	~~===You must enable Web Services in Joomla Global Configuration===~~
	~~You must enable Web Services in Joomla Global Configuration, in System->Global Configuration, System tab.~~
	~~{{End of Section}}~~

	~~==Joomdle XMLRPC Plugin enabled (J1.5 only)==~~
	~~===You must enable Joomdle XMLRPC Plugin===~~
	~~You must enable the Joomdle XMLRPC Plugin in Joomla backend, Extensions->Manage plugins.~~
	~~{{End of Section}}~~

	==Joomdlehooks User Plugin enabled==		==Joomdlehooks User Plugin enabled==
Line 110:		Line 101:

	If you are sure everything is correct, consider that it may be a connection issue: firewall and other security measures, DNS problems....		If you are sure everything is correct, consider that it may be a connection issue: firewall and other security measures, DNS problems....

	~~===Source IP not allowed===~~
	This means your server is using a non-public IP address for Joomla-Moodle connections. You will need to enter the displayed IP address in the "Internal IP address" config option, which can be found in Joomdle general config in Joomla.

	===E_DEPRECATED errors are enabled in your PHP configuration===		===E_DEPRECATED errors are enabled in your PHP configuration===

Antonio: /* Received empty response from Moodle */

2016-10-27T17:56:43Z

Received empty response from Moodle

← Older revision		Revision as of 17:56, 27 October 2016
Line 105:		Line 105:
	This can be caused by a misconfigured Moodle URL in Joomdle component. Double check that it is correct and that it includes '''http://''' in front.		This can be caused by a misconfigured Moodle URL in Joomdle component. Double check that it is correct and that it includes '''http://''' in front.

	You also need to make sure that the URL you are using is the same as the one ~~define~~ in moodle/config.pgp as $CFG->wwwroot.		You also need to make sure that the URL you are using is the same as the one defined in moodle/config.pgp as $CFG->wwwroot.

	Also check that Networking is enabled in Moodle, as well as Joomdle plugin.		Also check that Networking is enabled in Moodle, as well as Joomdle plugin.

Antonio: /* Received empty response from Moodle */

2016-10-27T17:56:07Z

Received empty response from Moodle

← Older revision		Revision as of 17:56, 27 October 2016
Line 103:		Line 103:

	===Received empty response from Moodle===		===Received empty response from Moodle===
	~~Usually this~~ caused by a misconfigured Moodle URL in Joomdle component. Double check that it is correct and that it includes '''http://''' in front.		This can be caused by a misconfigured Moodle URL in Joomdle component. Double check that it is correct and that it includes '''http://''' in front.
	If you are sure everything is correct, consider that it may be a connection issue (firewall, ~~etc)~~.
			You also need to make sure that the URL you are using is the same as the one define in moodle/config.pgp as $CFG->wwwroot.

			Also check that Networking is enabled in Moodle, as well as Joomdle plugin.

			If you are sure everything is correct, consider that it may be a connection issue: firewall and other security measures, DNS problems....

	===Source IP not allowed===		===Source IP not allowed===

Antonio at 16:36, 11 August 2016

2016-08-11T16:36:32Z

@@ Line 1: / Line 1: @@
 {{Languages}}
 =System Health Check=
 Joomdle includes a system health check tool in Joomla Component, that helps you ensure that you have met all the prerequisites to have Joomdle working correctly.
@@ Line 115: / Line 116: @@
 For example, my local configuration is:
 error_reporting = E_ALL & ~E_DEPRECATED

Antonio: /* Joomla URL seems to be misconfigured in Joomdle auth plugin in Moodle */

2014-10-28T18:18:30Z

Joomla URL seems to be misconfigured in Joomdle auth plugin in Moodle

← Older revision		Revision as of 18:18, 28 October 2014
Line 86:		Line 86:
	* Check any mod_security rules that may deny XMLRPC traffic		* Check any mod_security rules that may deny XMLRPC traffic
	* Disable any Joomla security extensions you may have installed		* Disable any Joomla security extensions you may have installed
			* Disable any Joomla SEF extensions you may have