Forum GLPI-Project

wolfsden3

Member

Registered: 2010-04-05

Posts: 28

The results could not be loaded

I just updated to the latest GLPI 10.0.10

I can't load results from many drop downs and I can't seem to add users to groups.

I'm running:

nginx
php 8.1 fpm
mariadb

Everything seems fine but I just can't get the drop down to show results.  When clicking it it says "The results could not be loaded" even though you can click on the "i"  (show users) icon and go into the users which has a big list.

I don't see many errors related to this in:  /var/www/html/files/_log

Migration log contents from 10.0.7 > 10.0.10 are here:

0 seconds for "Data migration - glpi_displaypreferences" @ 2023-10-10 14:02:39 [@helpdesk]
1 seconds for "Change of the database layout - glpi_changes" @ 2023-10-10 14:02:39 [@helpdesk]
0 seconds for "Change of the database layout - glpi_users" @ 2023-10-10 14:02:39 [@helpdesk]
0 seconds for "Change of the database layout - glpi_networkportfiberchannels" @ 2023-10-10 14:02:39 [@helpdesk]
0 seconds for "Change of the database layout - glpi_problems" @ 2023-10-10 14:02:39 [@helpdesk]
0 seconds for "Change of the database layout - glpi_queuednotifications" @ 2023-10-10 14:02:39 [@helpdesk]
0 seconds for "Change of the database layout - glpi_computervirtualmachines" @ 2023-10-10 14:02:40 [@helpdesk]
1 seconds for "Change of the database layout - glpi_networkequipments" @ 2023-10-10 14:02:40 [@helpdesk]
0 seconds for "Configuration values added for use_flat_dropdowntree_on_search_result (core)." @ 2023-10-10 14:02:40 [@helpdesk]
0 seconds for "Task Completed."

2023-10-10 14:02:40 [@helpdesk]
0 seconds for "Work in progress..." @ 2023-10-10 14:02:40 [@helpdesk]
0 seconds for "Data migration - glpi_displaypreferences" @ 2023-10-10 14:02:40 [@helpdesk]
0 seconds for "Task Completed."

1 seconds for "Work in progress..." @ 2023-10-10 14:02:41 [@helpdesk]
0 seconds for "Data migration - glpi_displaypreferences" @ 2023-10-10 14:02:41 [@helpdesk]
0 seconds for "Change of the database layout - glpi_mailcollectors" @ 2023-10-10 14:02:41 [@helpdesk]
0 seconds for "Change of the database layout - glpi_itilfollowuptemplates" @ 2023-10-10 14:02:41 [@helpdesk]
0 seconds for "Change of the database layout - glpi_planningexternaleventtemplates" @ 2023-10-10 14:02:41 [@helpdesk]
0 seconds for "Change of the database layout - glpi_solutiontemplates" @ 2023-10-10 14:02:41 [@helpdesk]
0 seconds for "Change of the database layout - glpi_tasktemplates" @ 2023-10-10 14:02:41 [@helpdesk]
0 seconds for "Task Completed."

...might anyone have any ideas?  When I search online others seem to have similar issues but I haven't run into any solutions that work for me.  Perhaps they're running Apache and it works differently than nginx?

I also confirmed my nginx config with the recommended config found here:  https://glpi-install.readthedocs.io/en/ … figuration

I'll comb through that again and reload services.

Thanks.

wolfsden3

Member

Registered: 2010-04-05

Posts: 28

Re: The results could not be loaded

This was resolved by redoing the default nginx config file to the stock glpi version of the file on the link.

Will try and close this.  Looking, I'm not sure I can close it.  Perhaps an admin can.

I think it should be kept so others can find this fix too.

Last edited by wolfsden3 (2023-10-10 20:52:56)

tikoretech

Member

Registered: 2023-11-23

Posts: 7

Re: The results could not be loaded

Friend,

I have the same problem, but I only use Apache under Centos 7 via CWP, I haven't been able to solve it so far... any tips

This was resolved by redoing the default nginx config file to the stock glpi version of the file on the link.

Will try and close this.  Looking, I'm not sure I can close it.  Perhaps an admin can.

I think it should be kept so others can find this fix too.

tikoretech

Member

Registered: 2023-11-23

Posts: 7

Re: The results could not be loaded

Problem resolved.

Through the apache logs, I saw that the installed modsec was seen as a sql injection attack on the server when calling ajax/actors.php

I put the log id in the exceptions, and the problem was resolved.

Friend,

I have the same problem, but I only use Apache under Centos 7 via CWP, I haven't been able to solve it so far... any tips

This was resolved by redoing the default nginx config file to the stock glpi version of the file on the link.

Will try and close this.  Looking, I'm not sure I can close it.  Perhaps an admin can.

I think it should be kept so others can find this fix too.