Error to send inventory by glpi-agent using https

[halexsandrosales]

Bug reporting acknowledgment

Yes, I read it

Professional support

None

Describe the bug

Hello,
is it possible that version 1.5 of glpi-agent has returned with this error?
Using letsencrypt certificates I am having error to use glpi-agent:

[LOG]

<?xml version="1.0" encoding="UTF-8"?>
<REQUEST>
  <DEVICEID>pevtcmtnb2590-2023-07-11-10-37-15</DEVICEID>
  <QUERY>PROLOG</QUERY>
  <TOKEN>12345678</TOKEN>
</REQUEST>
DEBUG: .../IO/Socket/SSL.pm:3011: new ctx 94701719636000
DEBUG: .../IO/Socket/SSL.pm:704: socket not yet connected
DEBUG: .../IO/Socket/SSL.pm:706: socket connected
DEBUG: .../IO/Socket/SSL.pm:729: ssl handshake not started
DEBUG: .../IO/Socket/SSL.pm:773: using SNI with hostname my.glpi.com
DEBUG: .../IO/Socket/SSL.pm:814: request OCSP stapling
DEBUG: .../IO/Socket/SSL.pm:830: set socket to non-blocking to enforce timeout=180
DEBUG: .../IO/Socket/SSL.pm:844: call Net::SSLeay::connect
DEBUG: .../IO/Socket/SSL.pm:3688: * TLSv1.3 (OUT), TLS handshake, Client hello (1)
DEBUG: .../IO/Socket/SSL.pm:847: done Net::SSLeay::connect -> -1
DEBUG: .../IO/Socket/SSL.pm:857: ssl handshake in progress
DEBUG: .../IO/Socket/SSL.pm:867: waiting for fd to become ready: SSL wants a read first
DEBUG: .../IO/Socket/SSL.pm:887: socket ready, retrying connect
DEBUG: .../IO/Socket/SSL.pm:844: call Net::SSLeay::connect
DEBUG: .../IO/Socket/SSL.pm:3688: * TLSv1.3 (IN), TLS handshake, Server hello (2)
DEBUG: .../IO/Socket/SSL.pm:3688: * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8)
DEBUG: .../IO/Socket/SSL.pm:847: done Net::SSLeay::connect -> -1
DEBUG: .../IO/Socket/SSL.pm:857: ssl handshake in progress
DEBUG: .../IO/Socket/SSL.pm:867: waiting for fd to become ready: SSL wants a read first
DEBUG: .../IO/Socket/SSL.pm:887: socket ready, retrying connect
DEBUG: .../IO/Socket/SSL.pm:844: call Net::SSLeay::connect
DEBUG: .../IO/Socket/SSL.pm:847: done Net::SSLeay::connect -> -1
DEBUG: .../IO/Socket/SSL.pm:857: ssl handshake in progress
DEBUG: .../IO/Socket/SSL.pm:867: waiting for fd to become ready: SSL wants a read first
DEBUG: .../IO/Socket/SSL.pm:887: socket ready, retrying connect
DEBUG: .../IO/Socket/SSL.pm:844: call Net::SSLeay::connect
DEBUG: .../IO/Socket/SSL.pm:3688: * TLSv1.3 (IN), TLS handshake, Certificate (11)
DEBUG: .../IO/Socket/SSL.pm:2855: ok=1 [2] /C=US/O=Internet Security Research Group/CN=ISRG Root X1/C=US/O=Internet Security Research Group/CN=ISRG Root X1
DEBUG: .../IO/Socket/SSL.pm:2855: ok=1 [1] /C=US/O=Internet Security Research Group/CN=ISRG Root X1/C=US/O=Let's Encrypt/CN=R3
DEBUG: .../IO/Socket/SSL.pm:2855: ok=1 [0] /C=US/O=Let's Encrypt/CN=R3/CN=my.glpi.com
DEBUG: .../IO/Socket/SSL.pm:1832: scheme=www cert=94701750984800
DEBUG: .../IO/Socket/SSL.pm:1842: identity=my.glpi.com cn=my.glpi.com alt=2 my.glpi.com
DEBUG: .../IO/Socket/SSL.pm:3688: * TLSv1.3 (IN), TLS handshake, CERT verify (15)
DEBUG: .../IO/Socket/SSL.pm:3688: * TLSv1.3 (IN), TLS handshake, Finished (20)
DEBUG: .../IO/Socket/SSL.pm:2902: did not get stapled OCSP response
DEBUG: .../IO/Socket/SSL.pm:3688: * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1)
DEBUG: .../IO/Socket/SSL.pm:3688: * TLSv1.3 (OUT), TLS handshake, Finished (20)
DEBUG: .../IO/Socket/SSL.pm:847: done Net::SSLeay::connect -> 1
DEBUG: .../IO/Socket/SSL.pm:902: ssl handshake done
DEBUG: .../IO/Socket/SSL.pm:3688: * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4)
DEBUG: .../IO/Socket/SSL.pm:3688: * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4)
[debug2] [http client] receiving message:

{"expiration":"4","status":"ok"}
[error] [http client] unexpected content, starting with: 
[error] No supported answer from server at https://my.glpi.com/front/inventory.php
DEBUG: .../IO/Socket/SSL.pm:3060: free ctx 94701719636000 open=94701719636000
DEBUG: .../IO/Socket/SSL.pm:3064: free ctx 94701719636000 callback
DEBUG: .../IO/Socket/SSL.pm:3071: OK free ctx 94701719636000

If I disable HTTPS on the system, communication happens normally.

But, if I use glpi-injector to force the XML file to be sent manually, it works normally.

glpi-injector -f pevtcmtnb2590-2023-07-11-10-37-15.xml -u https://meu.glpi.com

To reproduce

Just run in the computer:
glpi-agent -f

Expected behavior

updated inventory in glpi

Operating system

Windows, Linux

GLPI Agent version

Other (See additional context below)

GLPI version

10.0.x (See additional context below)

GLPIInventory plugin or FusionInventory for GLPI plugin version

No response

Additional context

After updating the glpi-agent to version 1.5, the computers stopped being updated in the GLPi system. Both Linux and Windows machines.

In tests, I identified that the glpi-injector is working normally, which leads me to believe that there is no error on the site.
Test with Injector:

    **glpi-injector** -f /tmp/pevtcmtnb2590-2023-07-11-10-37-15.xml -u https://my.glpi.com

Another test I performed was to rollback some machines to version 1.4. All with glpi-agent 1.4 returned to communicate normally with the inventory.

When debugging via the command line, I am getting the following error:

**glpi-agent -f**
...
<?xml version="1.0" encoding="UTF-8"?>
<REQUEST>
  <DEVICEID>pevtcmtnb2590-2023-07-11-10-37-15</DEVICEID>
  <QUERY>PROLOG</QUERY>
  <TOKEN>12345678</TOKEN>
</REQUEST>
DEBUG: .../IO/Socket/SSL.pm:3011: new ctx 94653039790720
DEBUG: .../IO/Socket/SSL.pm:704: socket not yet connected
DEBUG: .../IO/Socket/SSL.pm:706: socket connected
DEBUG: .../IO/Socket/SSL.pm:729: ssl handshake not started
DEBUG: .../IO/Socket/SSL.pm:773: using SNI with hostname my.glpi.com
DEBUG: .../IO/Socket/SSL.pm:814: request OCSP stapling
DEBUG: .../IO/Socket/SSL.pm:830: set socket to non-blocking to enforce timeout=180
DEBUG: .../IO/Socket/SSL.pm:844: call Net::SSLeay::connect
DEBUG: .../IO/Socket/SSL.pm:3688: * TLSv1.3 (OUT), TLS handshake, Client hello (1)
DEBUG: .../IO/Socket/SSL.pm:847: done Net::SSLeay::connect -> -1
DEBUG: .../IO/Socket/SSL.pm:857: ssl handshake in progress
DEBUG: .../IO/Socket/SSL.pm:867: waiting for fd to become ready: SSL wants a read first
DEBUG: .../IO/Socket/SSL.pm:887: socket ready, retrying connect
DEBUG: .../IO/Socket/SSL.pm:844: call Net::SSLeay::connect
DEBUG: .../IO/Socket/SSL.pm:3688: * TLSv1.3 (IN), TLS handshake, Server hello (2)
DEBUG: .../IO/Socket/SSL.pm:3688: * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8)
DEBUG: .../IO/Socket/SSL.pm:3688: * TLSv1.3 (IN), TLS handshake, Certificate (11)
DEBUG: .../IO/Socket/SSL.pm:2855: ok=1 [2] /C=US/O=Internet Security Research Group/CN=ISRG Root X1/C=US/O=Internet Security Research Group/CN=ISRG Root X1
DEBUG: .../IO/Socket/SSL.pm:2855: ok=1 [1] /C=US/O=Internet Security Research Group/CN=ISRG Root X1/C=US/O=Let's Encrypt/CN=R3
DEBUG: .../IO/Socket/SSL.pm:2855: ok=1 [0] /C=US/O=Let's Encrypt/CN=R3/CN=my.glpi.com
DEBUG: .../IO/Socket/SSL.pm:1832: scheme=www cert=94653036786672
DEBUG: .../IO/Socket/SSL.pm:1842: identity=my.glpi.com cn=my.glpi.com alt=2 atendimento.verdanadesk.com
DEBUG: .../IO/Socket/SSL.pm:3688: * TLSv1.3 (IN), TLS handshake, CERT verify (15)
DEBUG: .../IO/Socket/SSL.pm:3688: * TLSv1.3 (IN), TLS handshake, Finished (20)
DEBUG: .../IO/Socket/SSL.pm:2902: did not get stapled OCSP response
DEBUG: .../IO/Socket/SSL.pm:3688: * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1)
DEBUG: .../IO/Socket/SSL.pm:3688: * TLSv1.3 (OUT), TLS handshake, Finished (20)
DEBUG: .../IO/Socket/SSL.pm:847: done Net::SSLeay::connect -> 1
DEBUG: .../IO/Socket/SSL.pm:902: ssl handshake done
DEBUG: .../IO/Socket/SSL.pm:3688: * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4)
DEBUG: .../IO/Socket/SSL.pm:3688: * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4)
[debug2] [http client] receiving message:

{"expiration":"4","status":"ok"}
**[error] [http client] unexpected content, starting with: 
[error] No supported answer from server at https://my.glpi.com/front/inventory.php**
DEBUG: .../IO/Socket/SSL.pm:3060: free ctx 94653039790720 open=94653039790720
DEBUG: .../IO/Socket/SSL.pm:3064: free ctx 94653039790720 callback
DEBUG: .../IO/Socket/SSL.pm:3071: OK free ctx 94653039790720

[g-bougard]

Hi @halexsandrosales

indeed you seems to have the same problem then on #440. Check my comment here: #440 (comment)

In your log output, I can see 2 line feeds in the received messages:

[debug2] [http client] receiving message:

{"expiration":"4","status":"ok"}

So please, check your GLPI server configuration files as explained in my comment.

[halexsandrosales]

Hi,

tks for replay me. In GLPi conf is not closed php tag ( ?> )

root@myserver:~# cat .../glpi/config/config_db.php

<?php
class DB extends DBmysql {
public $dbhost = 'mysql-server';
public $dbuser = 'glpi';
public $dbpassword = '********';
public $dbdefault = 'glpi_db';
public $allow_datetime = false;
public $use_timezones = true;
public $use_utf8mb4 = true;
public $allow_signed_keys = false;
}

there is an other point to check?

the stranger is:

with agent 1.4 is normal. And when I use glpi-injector to send xml file is ok to.

[g-bougard]

For glpi-injector, this is normal, this is just a script and it doesn't try to analyse server answer. For glpi-agent 1.4, this is weird, but maybe the context is not exactly the same.

And indeed, you must check all php configuration files GLPI is expected to loaded. On a linux server, maybe one from /etc subfolders is loaded.

[halexsandrosales]

Hello again,

I used your feedback to research the error. I found the closing php tag "?>" in a private plugin file.
I removed it and it worked perfectly.

I still find it strange to work with agent 1.4 and not work with agent 1.5. But at least the problem was solved.

Thank you very much!

[halexsandrosales]

Hello again,

I used your feedback to research the error. I found the closing php tag "?>" in a private plugin file.
I removed it and it worked perfectly.

I still find it strange to work with agent 1.4 and not work with agent 1.5. But at least the problem was solved.

Thank you very much!