Replies: 1 comment
-
Hi @kluaneit first, as you didn't obfuscate you glpi nurl, and in the case you're using a public glpi, be sure to use the latest version to include all latest security fixes. The currently latest version in 10.0.9. Then I don't see here any evidence of glpi-agent bug. A 406 error is probably related to a server configuration issue involved by the migration. You should investigate your http server configration. Regarding your glpi-agent About SSL support, try to not use Also don't forget to update to latext glpi-agent v1.5 version. |
Beta Was this translation helpful? Give feedback.
-
Bug reporting acknowledgment
Yes, I read it
Professional support
Yes, I know
Describe the bug
I have a problem when I did a domain migration to another hosting, in the old hosting the GLPI worked great but when migrating to the new one it no longer works for me and I did all the clean installation with the restoration of the database and I couldn't get the Agent to communicate with the Web Server
To reproduce
Expected behavior
to register on the web server
Operating system
Windows
GLPI Agent version
1.4
GLPI version
10.0.x (See additional context below)
GLPIInventory plugin or FusionInventory for GLPI plugin version
GLPI Inventory v1.0.x (See additional context below)
Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions