Forums | Mahara Community

Mahara/Moodle integration /
Mahara cant retrieve Moodle public key


anonymous profile picture
Account deleted
Posts: 2

29 December 2009, 7:06

Mahara cant retrieve the public key from Moodle. Mahara already configured as a peer at moodle networking. Firewall and mod_security havent logs about this, just this Apache error:

[Tue Dec 29 08:50:54 2009] [error] [client 189.71.13.70] [DBG] 03 (auth/xmlrpc/lib.php:844) Error retrieving public key, failed with error code 503: An error occurred at the remote server. Code: , referer: http://ioduc.com/comum/admin/users/addauthority.php?add=1&i=ioduc&p=xmlrpc
anonymous profile picture
Account deleted
Posts: 1

13 January 2010, 15:13

Gledson,

   Its hard to tell exactly what the issue is from the vague error your getting but what you might want to check is the expiration date of the public key in Moodle.  I had problems retreiving this key and it was because it had already passed its expiration date and not automatically renewed.  To fix this I just deleted the old key and Moodle automatically generated  a new one for me.  Hope this helps.

-Dean

anonymous profile picture
Account deleted
Posts: 2

14 January 2010, 7:28

Dean,

Thanks for reply =D

This is a new installation, the keys are in the validity. One detail that I forgot to comment, is that both are installed on the same server. yet the error persists and I can not identify what prevents them from exchanging keys

anonymous profile picture
Account deleted
Posts: 5

14 March 2010, 17:56

Hey Dean,

How did you delete the old key?

I have a problem where key has expiry of 1970 so maybe this might fix my problem here:

http://mahara.org/interaction/forum/topic.php?id=1615

anonymous profile picture
Account deleted
Posts: 5

17 March 2010, 9:34

Hi - this is the same problem with IIS7 both on same server under post http://mahara.org/interaction/forum/topic.php?=id=1597  I have yet to crack it and they do seem to be talking but Maraha will not let me set up XMLRPC plugin

 (The old date problem was fixed by adding the environment variable to the ssl config listed elsewhere)

5 results