Category: Mahara

Categories
Mahara Moodle Uncategorized

MAHOODLE Payload not encryptedERROR 1:1:Payload not encrypted

When trying to export an assignment document to Mahara and we get the following error:

Payload not encryptedERROR 1:1:Payload not encryptedDebug: \nError code: failedtopingline 280 of /portfolio/mahara/lib.php: portfolio_export_exception thrown
line 57 of /portfolio/mahara/preconfig.php: call to portfolio_plugin_mahara->send_intent()\n, referer: http://moodle.appi.bme.hu/mod/assign/view.php

Most likely we are behind a firewall. If both Moodle and Mahara servers are behind the firewall simply add the inner IP address of the Mahara server to the Moodle server /etc/hosts file like this:

192.168.x.x<-->mahara.example.org

Or if you have a DNS inside the firewall, check the settings of it.

Categories
Mahara Moodle

MAHOODLE Sorry, could not log you in… :( when we are behind a firewall or a proxy

Installing MAHOODLE is easy and there is a very good install guide. Btw If we are behind a firewall / proxy and we have separated the application to different machines or VMs in the same sub network it could happen that we can not log in to Mahara from Moodle. We get an apache error like this:

[Sun Aug 25 10:23:12 2013] [warn] [client 192.168.1.2] mod_fcgid: stderr: * log_message("Curl error: 7: couldn't connect to host", 8, true, true) at /var/www/mahara.example.org/docs/lib/errors.php:109, referer: http://moodle.example.org/

192.168.1.2 is the gateway address.

The fact is that our sub network does not have it’s own DNS just a public one so when we try to connect to the Moodle machine we get the public IP address of it. So it tries to connect via XMLRPC across the firewall but that is not allowed of course.

The solution is simple add Moodle to the /etc/hosts file of the Mahara machine.

192.168.1.x moodle.example.org
Categories
Mahara

Mahara Moodle SSO – Unknown error 710

I have got a mail from one of our students, that she can not log in using SSO from Moodle. The Apache log said:

[Thu Oct 10 10:46:38 2013] [warn] [client 192.168.1.2] mod_fcgid: stderr: [WAR] fe (api/xmlrpc/client.php:173) Unknown error occurred: 710: Az al\xc3\xa1\xc3\xadr\xc3\xa1s-ellen\xc5\x91rz\xc3\xa9s sikertelen; az azonos\xc3\xadt\xc3\xa1st feltehet\xc5\x91leg nem \xc3\x96n \xc3\xadrta al\xc3\xa1., referer: http://moodle.appi.bme.hu/
[Thu Oct 10 10:46:38 2013] [warn] [client 192.168.1.2] mod_fcgid: stderr: Call stack (most recent first):, referer: http://moodle.example.org/
[Thu Oct 10 10:46:38 2013] [warn] [client 192.168.1.2] mod_fcgid: stderr: * Client->send("http://moodle.example.org") at /var/www/e-portfolio.appi.bme.hu/docs/auth/xmlrpc/lib.php:119, referer: http://moodle.example.org/
[Thu Oct 10 10:46:38 2013] [warn] [client 192.168.1.2] mod_fcgid: stderr: * AuthXmlrpc->request_user_authorise("f5d3148ab41b07113f47f79458596a5425b73895", "http://moodle.appi.bme.hu") at /var/www/e-portfolio.example.org/docs/auth/xmlrpc/land.php:94, referer: http://moodle.example.org/

The solution was to change the public keys on both Moodle and Mahara. After it the SSO worked again.