The update server allows one key per URL. If you have a development copy (e.g., dev.helpdesk.local) and a production copy (helpdesk.prod.com), they need different keys.
Solution: Delete the old instance from your services.glpi-network.com profile and regenerate the key. glpi registration key
During the final steps of the GLPI installation wizard (step 4 or 5 depending on version), the installer prompts for a "Registration Key." Plugin key not accepted:
Example: The "GLPI Inventory" plugin (formerly FusionInventory) is free. However, a "SLA Dashboard Pro" plugin might cost €99/year and require a separate key. API token authentication fails:
Always read the plugin documentation. If a plugin asks for a key and you did not pay for it, you likely have the wrong file.
A common point of confusion is the difference between the registration key and software license keys managed within GLPI.
| Aspect | Registration Key | Software License Key (managed by GLPI) | |--------|------------------|------------------------------------------| | Purpose | Authenticate inventory agents | Track commercial software entitlements (e.g., Windows, Office) | | Location | Set in GLPI server configuration | Stored in the "Licenses" module | | Used by | GLPI Agent, FusionInventory Agent | IT asset managers, compliance reports | | Open source? | Yes (feature of GLPI) | Depends on the software being tracked |