Skip to main content

6. Troubleshooting

Nobody can sign in, the code never arrives

Check, in this order: Setup > Notifications has Enable email notifications on; the notification One-Time Security Code generated - MFA is active; the mail server of GLPI works (use the test of Email notifications configuration); the automatic action Send mails in queue is enabled and runs; and the user has an e-mail address. The code form says when the mail server refused the message, and reloading the form sends a new code. If you are locked out of GLPI, deactivate the plugin from the command line and fix the setup: php bin/console plugin:deactivate mfa.

The settings refuse to turn a type on

The plugin does not allow it while codes cannot be delivered, because those users would not be able to sign in. The message tells what is missing: e-mail notifications off, the notification of the code inactive, or the automatic action that sends the queued mails disabled. Fix it and save again. Turning a type off is always possible.

A user says "Your account has no e-mail address"

The user is covered by MFA but has no e-mail address in GLPI, so no code can be sent. Add the address in Administration > Users, or turn the type of that account off.

The code is refused as incorrect

A code can be used once and is valid for up to 10 minutes; a newer code replaces the previous one, so use the last mail. Reloading the code form sends a new code. After five wrong codes in 15 minutes the user is locked out and has to wait; signing out and in does not clear it.

A user is not asked for a code

Check that the switch of the type of that account is Yes (GLPI database, mail server, LDAP, external or CAS/x509) and that the session was opened after MFA was turned on. Accounts of any other type are never asked. Users who signed in with GLPI's own two-factor authentication are not asked twice, but only when that authenticator existed before the sign-in. Also, while GLPI suspends the plugins after a core update, no code is asked until an administrator resumes them.

The API or CalDAV stopped working for a user

For the accounts that need a code, CalDAV with a password, the REST API login with login and password and the OAuth password grant are refused, because they would skip the code. Use an API user token or the tokens issued for the API instead; those are not covered by the code.

I reinstalled the plugin and users cannot sign in

If the plugin folder was deleted without uninstalling it, its tables stay in the database and the old configuration applies again as soon as the plugin is reinstalled. If e-mail cannot be delivered, uninstall properly, or set every type to No in the database first: UPDATE glpi_plugin_mfa_configs SET local = 0, mail = 0, ldap = 0, external = 0, other = 0;.

Generated for MFA 3.0.1 on GLPI 12.0.2 — 2026-11-20.