Before you start
- An up-to-date Debian 13 virtual machine or server, with root or sudo access
- A DNS name for the service, for example support.example.lan
- The basics of the Linux command line (see Linux commands for beginners)
In plain words
GLPI is both the health record of the IT estate and the IT department's front desk. The health record lists every computer, screen, printer, piece of software and contract, with its history. The front desk receives users' requests as tickets, assigns them to a technician and keeps track of what was done. The two are linked: when someone reports a fault, you immediately see which machine it is.
1. GLPI at a glance
GLPI (Gestionnaire Libre de Parc Informatique, "free IT asset manager") is open source software (GPLv3 licence) developed by the French company Teclib'. It covers:
| Module | What it does |
|---|---|
| Assets | Inventory of computers, servers, network equipment, phones, printers, software and licences |
| Assistance | Tickets (incidents and requests), problems, changes, service levels (SLA), satisfaction |
| Management | Contracts, suppliers, budgets, documents, hardware lifecycle |
| Tools | Knowledge base, projects, equipment reservations, reminders |
| Automatic inventory | Machines report in through the GLPI agent, built in natively since GLPI 10 |
Which version? As of 20 October 2026:
- GLPI 11.0 is the stable branch to install (11.0.11 released on 1 October 2026; avoid 11.0.10, replaced because of a regression).
- GLPI 10.0.28 is the last version of branch 10: it will receive no more fixes once GLPI 12 is released. If you're still on 10, plan the upgrade.
- GLPI 12 has been a release candidate since September 2026, with in particular a reworked knowledge base, a session manager and a "sudo" mode for sensitive actions. Wait for the stable release and its first fixes before using it in production.
Check the latest version
Look at the GLPI releases page before you start, and use the latest version of the 11.0 branch. Security updates are frequent.
2. What we'll build
| Element | Choice | Why |
|---|---|---|
| System | Debian 13 | Stable, PHP 8.4 and MariaDB 11.8 in the official repositories |
| Web server | Apache with PHP-FPM | Configuration documented by GLPI, PHP separate from the web server |
| Database | MariaDB | GLPI 11 requires MySQL 8.0 or MariaDB 10.6 at least |
| File locations | Code in /var/www/glpi, configuration in /etc/glpi, data in /var/lib/glpi, logs in /var/log/glpi |
Sensitive files are never reachable from the web |
| Access | https://support.example.lan |
A dedicated name, over HTTPS |
Starting size for a few hundred machines: 2 vCPUs, 4 GB of RAM, 30 GB of disk. Increase RAM and disk if you store a lot of attachments or if the estate exceeds a few thousand devices.
Exposure to the internet
GLPI holds the complete inventory of the estate and sometimes confidential exchanges. Keep it on the internal network or behind a VPN. If outside users need access, go through a reverse proxy with HTTPS, two-factor authentication on, and apply every security update without delay.
3. Install the packages
Update the system, then install Apache, PHP-FPM, MariaDB and the PHP extensions GLPI 11 requires:
sudo apt update && sudo apt full-upgrade -y
sudo apt install -y apache2 mariadb-server php8.4-fpm \
php8.4-curl php8.4-gd php8.4-intl php8.4-mysql php8.4-zip \
php8.4-bcmath php8.4-mbstring php8.4-xml php8.4-bz2 php8.4-ldap
The php8.4-ldap extension is only useful for authentication through Active Directory or an LDAP directory, but it saves coming back to install a package later. Check the PHP version:
php -v
4. Prepare the database
Secure MariaDB (root password, removal of anonymous accounts and the test database):
sudo mariadb-secure-installation
Load the time zones into MariaDB. GLPI uses them to show dates in each user's time zone:
mariadb-tzinfo-to-sql /usr/share/zoneinfo | sudo mariadb mysql
sudo systemctl restart mariadb
Create the database and a dedicated account, with rights on this database only. Replace the password with a long, unique value, kept in your password manager:
sudo mariadb
CREATE DATABASE glpi CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
CREATE USER 'glpi'@'localhost' IDENTIFIED BY 'LongUniquePassword';
GRANT ALL PRIVILEGES ON glpi.* TO 'glpi'@'localhost';
GRANT SELECT ON mysql.time_zone_name TO 'glpi'@'localhost';
FLUSH PRIVILEGES;
EXIT;
5. Download GLPI
Put the latest version number in a variable, download the official archive and extract it:
VERSION=11.0.11
cd /tmp
wget "https://github.com/glpi-project/glpi/releases/download/\
${VERSION}/glpi-${VERSION}.tgz"
sudo tar -xzf glpi-${VERSION}.tgz -C /var/www/
The /var/www/glpi folder is created.
6. Move sensitive files out of the web folder
By default, the configuration (database credentials, encryption key) and the data (attachments, sessions) are in the application folder. We move them to the standard Linux locations, as GLPI's documentation recommends.
Move the configuration and data, and create the logs folder:
sudo mv /var/www/glpi/config /etc/glpi
sudo mkdir -p /var/lib/glpi
sudo mv /var/www/glpi/files /var/lib/glpi/
sudo mkdir -p /var/log/glpi
Tell GLPI where its configuration is, with the file /var/www/glpi/inc/downstream.php:
sudo tee /var/www/glpi/inc/downstream.php > /dev/null <<'EOF'
<?php
define('GLPI_CONFIG_DIR', '/etc/glpi/');
if (file_exists(GLPI_CONFIG_DIR . '/local_define.php')) {
require_once GLPI_CONFIG_DIR . '/local_define.php';
}
EOF
Then set the location of the data and logs in /etc/glpi/local_define.php:
sudo tee /etc/glpi/local_define.php > /dev/null <<'EOF'
<?php
define('GLPI_VAR_DIR', '/var/lib/glpi/files');
define('GLPI_LOG_DIR', '/var/log/glpi');
EOF
Apply permissions on the least privilege principle: the code belongs to root and can't be modified by the web server, only the folders that must be written to belong to www-data (the Apache and PHP-FPM account):
sudo chown -R root:root /var/www/glpi
sudo chown -R www-data:www-data /var/www/glpi/marketplace
sudo chown -R www-data:www-data /etc/glpi /var/lib/glpi /var/log/glpi
sudo chmod 750 /etc/glpi /var/lib/glpi /var/log/glpi
The marketplace folder stays writable so you can install plug-ins from GLPI's interface.
7. Configure Apache
Create the virtual host /etc/apache2/sites-available/glpi.conf. Only the public folder is served: the rest of the application can't be reached from the browser.
<VirtualHost *:80>
ServerName support.example.lan
DocumentRoot /var/www/glpi/public
<Directory /var/www/glpi/public>
Require all granted
RewriteEngine On
# Pass on the Authorization header (API, inventory)
RewriteCond %{HTTP:Authorization} ^(.+)$
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
# Every address goes through GLPI's router
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^(.*)$ index.php [QSA,L]
</Directory>
<FilesMatch \.php$>
SetHandler "proxy:unix:/run/php/php8.4-fpm.sock|fcgi://localhost/"
</FilesMatch>
ErrorLog ${APACHE_LOG_DIR}/glpi-error.log
CustomLog ${APACHE_LOG_DIR}/glpi-access.log combined
</VirtualHost>
Enable the site and the modules, disable the default site, then check the syntax before reloading:
sudo a2enmod rewrite proxy_fcgi setenvif
sudo a2enconf php8.4-fpm
sudo a2ensite glpi.conf
sudo a2dissite 000-default.conf
sudo apache2ctl configtest
sudo systemctl reload apache2
The configtest command must answer Syntax OK.
8. Configure PHP
Settings go in the PHP-FPM file, /etc/php/8.4/fpm/php.ini (not Apache's, which isn't used here). Change or add these lines:
session.cookie_httponly = On
session.cookie_samesite = Lax
upload_max_filesize = 20M
post_max_size = 20M
memory_limit = 256M
date.timezone = Europe/London
Adapt date.timezone to your time zone, then restart PHP-FPM:
sudo systemctl restart php8.4-fpm
session.cookie_secure = On will be added at the HTTPS step: enabling it earlier would prevent any login over HTTP.
9. Install GLPI
Two methods, your choice.
Through the browser. Open http://support.example.lan, choose the language, accept the licence, then Install. GLPI checks the prerequisites: everything must be green, orange warnings are to be read. Then enter localhost, the user glpi and its password, select the glpi database and let the initialisation finish.
On the command line, faster and reproducible. The command runs with the www-data account, and -p with no value asks for the password without leaving it in the history:
cd /var/www/glpi
sudo -u www-data php bin/console db:install \
-H localhost -d glpi -u glpi -p -L en_GB
Then check that every prerequisite is met:
sudo -u www-data php bin/console glpi:system:check_requirements
10. Secure it right after installation
GLPI creates four default accounts, with passwords known to everyone (glpi/glpi, tech/tech, normal/normal, post-only/postonly):
| Account | Profile | Action |
|---|---|---|
glpi |
Super-Admin | Change the password immediately, then keep it for emergencies |
tech |
Technician | Disable or delete |
normal |
User | Disable or delete |
post-only |
Simple requester | Disable or delete |
- Log in as
glpi, change its password, and create your own named administrator account, for examplespo. - Disable the
tech,normalandpost-onlyaccounts in Administration > Users. -
Delete the installer, which must no longer be reachable:
sudo rm /var/www/glpi/install/install.php -
Turn off the demonstration data offered on the dashboard.
- Enable two-factor authentication for administrator accounts (GLPI 11 has built-in TOTP code authentication, see two-factor authentication).
-
Once installation is finished, make the configuration read-only for the web server:
sudo chown -R root:www-data /etc/glpi && sudo chmod -R g-w /etc/glpi
The encryption key
The file /etc/glpi/glpicrypt.key encrypts the passwords stored by GLPI (mail accounts, LDAP directories). Without it, a database restore is useless for these items. It must be part of every backup, and must never be published.
11. Enable automatic actions
GLPI has background tasks: sending notifications, collecting email, calculating service levels, cleaning up. By default, they're triggered by users' visits, which is unreliable. Have the system run them every minute, with the web server's account:
echo '* * * * * www-data /usr/bin/php /var/www/glpi/front/cron.php' \
| sudo tee /etc/cron.d/glpi
In GLPI, then open Setup > Automatic actions and switch the tasks to CLI mode. After a few minutes, check that the "Last run" column updates.
12. Switch to HTTPS
Credentials and tickets mustn't travel in clear text.
- Internal network: use a certificate issued by the company's certificate authority (for example AD CS) or by an internal authority such as step-ca.
- Public name: a Let's Encrypt certificate through
certbot(packagepython3-certbot-apache) is fine.
Add a virtual host on port 443 with SSLEngine on and the certificate paths (ssl module, sudo a2enmod ssl), and redirect port 80 to HTTPS. Then:
- Add
session.cookie_secure = Onin/etc/php/8.4/fpm/php.iniand restart PHP-FPM. - In Setup > General, update the URL of the application to
https://support.example.lan: it's used in the links in notifications.
13. Collect the inventory with the GLPI agent
First enable inventory in Administration > Inventory, Enable inventory box.
Download the agent from the GLPI Agent releases page, then install it on the computers.
Windows, silent installation from the Command Prompt (not PowerShell, which can interfere with passing the parameters), replacing the file name with the version you downloaded:
msiexec /i GLPI-Agent-x.y-x64.msi /quiet ^
SERVER=https://support.example.lan/front/inventory.php RUNNOW=1
For a fleet, deploy the same MSI through group policy, Intune or your usual deployment tool.
Linux, with the installation script provided on the same page:
sudo perl glpi-agent-x.y-linux-installer.pl \
--server=https://support.example.lan/front/inventory.php --runnow
Machines appear in Assets > Computers after their first report. The agent can also discover the network and query equipment over SNMP (switches, printers): these tasks are configured afterwards in the same inventory menu.
14. First settings
In order, to start on a clean base:
- Entities: if you manage several companies or sealed-off sites, create one entity per scope before importing anything. Otherwise, keep the root entity.
- Authentication: connect Active Directory or the LDAP directory in Setup > Authentication > LDAP directories so users sign in with their usual account. Use LDAPS (port 636) and a read-only service account.
- Profiles: start from the existing profiles (Self-Service, Technician, Supervisor, Admin) and adjust the rights rather than creating new ones from scratch.
- Ticket categories: about ten to start with (Workstation, Email, Printer, Access and accounts, Network, Software…). Too many categories discourage requesters.
- Mail receiver: in Setup > Receivers, an address such as
support@example.comturns every message received into a ticket. - Notifications: configure SMTP sending in Setup > Notifications, then keep only the useful notifications.
- Service levels (SLA): define realistic response and resolution times, and link them to categories.
- Knowledge base: publish the answers to frequent questions, visible to users from the simplified interface. For richer internal documentation, see knowledge bases and wikis.
15. Back up
Three items are essential: the database, the data and the configuration. Example script, to schedule every night:
#!/bin/bash
# /usr/local/sbin/backup-glpi.sh
set -euo pipefail
DEST=/var/backups/glpi
DAY=$(date +%F)
mkdir -p "$DEST"
mariadb-dump --single-transaction glpi | gzip > "$DEST/glpi-db-$DAY.sql.gz"
tar -czf "$DEST/glpi-files-$DAY.tar.gz" /etc/glpi /var/lib/glpi
find "$DEST" -type f -mtime +14 -delete
The script runs as root, which connects to MariaDB without a password through the local socket. Then copy /var/backups/glpi off the server (see the 3-2-1 rule), and run a restore test on a test machine at least once a quarter.
16. Updating GLPI
A minor version update (11.0.x to 11.0.y) goes like this. Test on a copy first if you can.
Step 1. Run a full backup (step 15) and take a snapshot of the virtual machine.
Step 2. Temporarily make the configuration writable, then put GLPI into maintenance mode:
sudo chown -R www-data /etc/glpi
sudo -u www-data php /var/www/glpi/bin/console glpi:maintenance:enable
Step 3. Replace the code, keeping downstream.php and the plug-ins:
VERSION=11.0.12 # the new version
cd /tmp
wget "https://github.com/glpi-project/glpi/releases/download/\
${VERSION}/glpi-${VERSION}.tgz"
sudo mv /var/www/glpi /var/www/glpi-old
sudo tar -xzf glpi-${VERSION}.tgz -C /var/www/
sudo rm -rf /var/www/glpi/config /var/www/glpi/files
sudo cp /var/www/glpi-old/inc/downstream.php /var/www/glpi/inc/
sudo cp -a /var/www/glpi-old/marketplace/. /var/www/glpi/marketplace/
sudo chown -R root:root /var/www/glpi
sudo chown -R www-data:www-data /var/www/glpi/marketplace
Step 4. Update the database, leave maintenance mode and lock the configuration again:
cd /var/www/glpi
sudo -u www-data php bin/console db:update
sudo -u www-data php bin/console glpi:maintenance:disable
sudo chown -R root:www-data /etc/glpi
Step 5. Delete install/install.php, check that everything works, then delete /var/www/glpi-old.
Major version changes (10 to 11, then 11 to 12) follow the same principle, but read the release notes first: plug-ins must be compatible with the new version.
17. Troubleshooting
| Symptom | Likely cause | Solution |
|---|---|---|
| Blank page or error 500 | PHP error | Read /var/log/glpi/php-errors.log and /var/log/apache2/glpi-error.log |
| Error 404 on every page except the home page | rewrite module missing or wrong DocumentRoot |
sudo a2enmod rewrite, check that the root is /var/www/glpi/public |
| PHP code is displayed or downloaded | PHP-FPM not connected to Apache | sudo a2enconf php8.4-fpm, check the socket path in the SetHandler |
| "The configuration folder is not writable" during installation | Permissions on /etc/glpi |
sudo chown -R www-data /etc/glpi for the duration of the installation |
| Time zone warning | Time zone tables not loaded or missing right | Redo the loading from step 4 and the GRANT SELECT on mysql.time_zone_name |
| Notifications aren't sent | Automatic actions not running | Check /etc/cron.d/glpi and the actions' CLI mode |
| The agent reports nothing | Inventory disabled, URL or certificate rejected | Enable inventory, check the URL, run the agent by hand with glpi-agent --debug |
18. Checklist
| Item | Done? |
|---|---|
| Debian up to date, automatic security updates on | ☐ |
Dedicated MariaDB account, with rights limited to the glpi database |
☐ |
| Configuration, data and logs outside the web folder | ☐ |
Application code not writable by www-data |
☐ |
DocumentRoot on /var/www/glpi/public |
☐ |
install/install.php deleted |
☐ |
glpi account password changed, tech, normal and post-only accounts disabled |
☐ |
| Named administrator accounts, with two-factor authentication | ☐ |
| Automatic actions in CLI mode through cron | ☐ |
HTTPS active, session.cookie_secure on, application URL up to date |
☐ |
Backup of the database, /var/lib/glpi and /etc/glpi (with glpicrypt.key) tested |
☐ |
| Subscribed to GLPI's security announcements to apply updates quickly | ☐ |
Sources
- GLPI: installation documentation (prerequisites)
- GLPI: installation and file locations
- GLPI: command-line tools
- GLPI: time zone support
- GLPI: automatic actions
- GLPI Agent: command-line installation on Windows
- GLPI: releases
- IT-Connect (France): GLPI 11.0.10, 10.0.28 and the end of GLPI 10 (in French)
- GLPI: GLPI 12 release candidate