Note:

If you want to create a new page for developers, you should create it on the Moodle Developer Resource site.

MNet Errors

From MoodleDocs

Introduction

This wiki page attempts to document all the MNET error codes, what they mean, where they're called from, and what cases can trigger them. As MNET is theoretically pluggable, this does not cover all exhaustive cases, just ones that are included in the core Moodle distribution.

System/Verification errors

712, "phperror"

This is called from the main mnet xmlrpc server (mnet/xmlrpc/server.php) when $_SERVER is unset.

7025

This is triggered when the peer used an older public key. This sends the xmlrpc server fault, with 7025 as the code, and the current public key as the text of the error message.

7021, "forbidden-transport"

This is triggered if a non-encrypted request is sent, and plaintext is disallowed (plaintext can be enabled for trusted hosts within a designated subnet)

711, "verifysignature-error"

This is triggered if a request wasn't signed

710, "verifysignature-invalid"

This is triggered if a request was signed, but not able to be verified

7020, "wrong-wwwroot"

This is triggered if the host record is unable to be found, based on the wwwroot inside the xmlrpc request. This can sometimes happen if you use www.mysite.com and mysite.com

7023, "encryption-invalid"

This is triggered if Moodle can't decrypt the message either with the current key, or with any of the keys in the history.


Dispatch errors

713, "nosuchfunction"

This is triggered if the function given in the xmlrpc request doesn't match the regular expression of allowed function calls (which must be of the form auth/mnet/auth.php/function_name)


704, "nosuchservice"

This is triggered if "Networking" is disabled in Admin -> Advanced Features, or $CFG->mnet_dispatcher_mode is "off".

Authentication errors

Enrolment errors

Portfolio errors

Repository errors