I just finished setting up two GLPI servers and had the same issue on both. After much slogging though google with very little help, I found mention of ownership issues (not to be confused with permissions issues). The glpi folder and all files and subfolders must be owned by the user and group the web server is running as. (Typically “nobody”, “www-data”, or “apache”.) It doesn’t matter even if you set your permissions chmod 777, the ownership is what makes the difference.

Assuming your httpd’s user/group is www-data here’s what you need to do: (Bold is a command, regular is the output, highlights are added for emphasis.)

htdocs # ls -l
total 2
drwxrwxrwx 15
root root 4096 Nov 30 06:04 glpi
-rw-r–r– 1 root root 44 Nov 20 15:22 index.html
htdocs#
chown -R www-data:www-data glpi
htdocs # ls -l
total 2
drwxrwxrwx 15
www-data www-data 4096 Nov 30 06:04 glpi
-rw-r–r– 1 root root 44 Nov 20 15:22 index.html

This is something very simple but was not immediately obvious to me. I am setting up a Zabbix server as part of my consulting work and have many servers behind firewalls that need to use active checks. (Connect from server behind firewall/nat to the zabbix server, rather than have the zabbix server connect out to the monitored agents.) When you create the host set the name and dns name to the server’s name you put into the zabbix_agentd.conf file on the server you want to do active checks on. It will show up as unknown availability but that is erroneous.

Also, you need to create items with active checks. I recommend cloning a template and copying the items and triggers over. Then do a Mass Update and set all the items to “Zabbix Agent (Active)”