Why am I seeing a "membership service encountered some errors" message in Moodle LTI 1.3?

When creating Moodle LTI 1.3 assignments, you may encounter the error message: 

The membership service encountered some errors

Note on impact: This message should not prevent students from submitting to LTI 1.3 assignments. However, student enrollments may not appear in the assignment roster until after the students have submitted their work.

Troubleshooting Steps

This error and the associated student roster sync issues typically stem from unsupported Moodle roles, network firewalls, or local server configurations. Please review the following settings with your IT or server administrator.

1. Check Moodle Roles

Turnitin officially supports three standard roles: Administrator, Instructor (Teacher), and Student.

If the error is being generated under a custom role (such as Master or Module Leader), please test the integration using one of the three supported roles to see if the error resolves.

2. Verify Firewall Settings

Please verify with your IT or network team that there is no firewall within your institutional LMS environment blocking calls to the domain: https://lti.int.turnitin.com.

3. Check Apache & PHP Server Configuration

If your roles and firewalls are correctly configured, 401 unauthorized errors and the "membership service" prompt are likely originating from your local server's Apache or PHP configuration. When a server strips out authorization headers or mismanages path info, it blocks Moodle from communicating successfully with Turnitin.

Verify Apache Configuration:

  • Ensure AcceptPathInfo On is set in your Apache configuration.
  • Add CGIPassAuth On to your .htaccess or httpd.conf file to prevent the server from stripping Authorization headers.
  • Confirm which version of PHP is currently installed.

Run a PHP Header Test:

To confirm if Apache is passing headers correctly, your IT team can create a simple PHP test file on the server designed to print out the authorization headers. If the headers are missing in the test output, it confirms the configuration is actively stripping them before they reach Moodle.

Note: Because these settings are hosted on your institution's servers, your internal IT team will need to resolve them locally. Turnitin is unable to modify them or bypass the resulting errors from our end.

Still experiencing issues?

If your IT team confirms that the server configurations above are correct, please contact Turnitin Support for deeper investigation.

To help us escalate your ticket to our engineering team quickly, please confirm in your message that your Moodle Roles and Firewalls are correct, and provide both your current PHP version and the successful PHP header test results proving the authorization headers are passing.

Was this article helpful?
0 out of 0 found this helpful

Articles in this section