[Q&A] ESX Task error internal response: 500 Can't connect to localhost:80 (Connection refused)

[mikilt92]

Documentation & bug reporting acknowledgment

Yes, I read it

Describe your problem

Hi All,

I'm experiencing issues with a VMware type task using the GLPI agent. I have followed these steps:

1. Created credentials for VMware authentication:
   
2. Created a Remote Device.
   
3. Enabled the VMware module on the agent:
   
4. Created a Task and Job, assigning the Target and the agent:
   

The job remains in a pending state and the agent does not take charge of the job:

When I try to execute the Task on the agent, I encounter the following error message:

Mar 18 18:27:25 miki-ubuntu glpi-agent[242352]: [info] target server0: server https://myfqdn.local/plugins/glpiinventory/
Mar 18 18:27:25 miki-ubuntu glpi-agent[242352]: [info] sending contact request to server0
Mar 18 18:27:25 miki-ubuntu glpi-agent[242352]: [info] sending prolog request to server0
Mar 18 18:27:25 miki-ubuntu glpi-agent[244238]: [info] running task Inventory
Mar 18 18:27:25 miki-ubuntu glpi-agent[244238]: [info] New inventory from miki-ubuntu-2025-03-18-15-51-25 for server0
Mar 18 18:27:32 miki-ubuntu glpi-agent[244518]: [info] running task ESX
Mar 18 18:27:32 miki-ubuntu glpi-agent[244518]: [error] [http client] internal response: 500 Can't connect to localhost:80 (Connection refused)
Mar 18 18:27:32 miki-ubuntu glpi-agent[244528]: [info] running task Deploy
Mar 18 18:27:32 miki-ubuntu glpi-agent[244528]: [info] No Deploy job enabled or Deploy support disabled server side.
Mar 18 18:27:32 miki-ubuntu glpi-agent[244540]: [info] running task Collect
Mar 18 18:27:33 miki-ubuntu glpi-agent[244540]: [info] No Collect job enabled or Collect support disabled server side.
Mar 18 18:27:33 miki-ubuntu glpi-agent[242352]: [info] target server0: next run: Wed Mar 19 18:10:45 2025 - https://myfqdn.local/plugins/glpiinventory/

The agent is able to execute other Inventory or Remote Inventory tasks, such as network scans and inventory via SNMP credentials. It seems that the problem is specific to VMware-related tasks.

My configuration:

• GLPI Agent (1.13-1)
• GLPI 10.0.17

Does anyone have any idea what might be causing this error?

Thank you,
Michele

[g-bougard]

Hi Michele,

you should first enable debug=2 in your agent and check if you have more reliable information against that error 500.

You can also try to use glpi-esx script to see if you are able to manually run the ESX task. If you can, it probably means something is not fully correct in the task configuration GLPI side.

But as glpi-agent tries to connect on "localhost", this still may be a name resolution problem. You configured ESX ip with "thmzn-vcsa.thaumazon.local". Is is possible this address is resolved to "localhost" on glpi-agent side ?

[mikilt92]

Hi Guillaume,

Thank you for your response. I enabled debug mode and tried again. Here's the relevant log portion for the ESX task:

Mar 19 12:12:18 miki-ubuntu glpi-agent[182377]: [debug] forking process 310252 to handle child job
Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: [debug2] child[310252]: forked
Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: [debug] forking process 310252 to handle task ESX
Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: [info] running task ESX
Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: [debug2] [http client] Not using compression
Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: [debug2] https://thmzn-glpi.thaumazon.local/plugins/glpiinventory/?action=getConfig&task[ESX]=2.13&machineid=miki-ubuntu-2025-03-18-15-51-25
Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: DEBUG: .../IO/Socket/SSL.pm:3020: new ctx 109818923267808
Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: DEBUG: .../IO/Socket/SSL.pm:705: socket not yet connected
Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: DEBUG: .../IO/Socket/SSL.pm:707: socket connected
Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: DEBUG: .../IO/Socket/SSL.pm:730: ssl handshake not started
Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: DEBUG: .../IO/Socket/SSL.pm:774: using SNI with hostname thmzn-glpi.thaumazon.local
Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: DEBUG: .../IO/Socket/SSL.pm:815: request OCSP stapling
Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: DEBUG: .../IO/Socket/SSL.pm:831: set socket to non-blocking to enforce timeout=180
Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: DEBUG: .../IO/Socket/SSL.pm:845: call Net::SSLeay::connect
Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: DEBUG: .../IO/Socket/SSL.pm:3700: * TLSv1.3 (OUT), TLS handshake, Client hello (1)
Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: DEBUG: .../IO/Socket/SSL.pm:848: done Net::SSLeay::connect -> -1
Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: DEBUG: .../IO/Socket/SSL.pm:858: ssl handshake in progress
Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: DEBUG: .../IO/Socket/SSL.pm:868: waiting for fd to become ready: SSL wants a read first
Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: DEBUG: .../IO/Socket/SSL.pm:888: socket ready, retrying connect
Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: DEBUG: .../IO/Socket/SSL.pm:845: call Net::SSLeay::connect
Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: DEBUG: .../IO/Socket/SSL.pm:3700: * TLSv1.3 (IN), TLS handshake, Server hello (2)
Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: DEBUG: .../IO/Socket/SSL.pm:3700: * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8)
Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: DEBUG: .../IO/Socket/SSL.pm:3700: * TLSv1.3 (IN), TLS handshake, Certificate (11)
Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: DEBUG: .../IO/Socket/SSL.pm:2864: ok=0 [0] /C=IT/ST=Italy/L=Rome/O=Thaumazon Srl/OU=IT&Security/CN=THMZN Online CA/C=IT/ST=Italy/L=Roma/O=Thaumazon Srl/OU=IT&Security/CN=thmzn-glpi.thaumazon.local
Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: DEBUG: .../IO/Socket/SSL.pm:2864: ok=1 [0] /C=IT/ST=Italy/L=Rome/O=Thaumazon Srl/OU=IT&Security/CN=THMZN Online CA/C=IT/ST=Italy/L=Roma/O=Thaumazon Srl/OU=IT&Security/CN=thmzn-glpi.thaumazon.local
Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: DEBUG: .../IO/Socket/SSL.pm:1840: scheme=www cert=109818923353120
Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: DEBUG: .../IO/Socket/SSL.pm:1850: identity=thmzn-glpi.thaumazon.local cn=thmzn-glpi.thaumazon.local alt=2 thmzn-glpi.thaumazon.local
Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: DEBUG: .../IO/Socket/SSL.pm:3700: * TLSv1.3 (IN), TLS handshake, CERT verify (15)
Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: DEBUG: .../IO/Socket/SSL.pm:3700: * TLSv1.3 (IN), TLS handshake, Finished (20)
Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: DEBUG: .../IO/Socket/SSL.pm:3700: * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1)
Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: DEBUG: .../IO/Socket/SSL.pm:3700: * TLSv1.3 (OUT), TLS handshake, Finished (20)
Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: DEBUG: .../IO/Socket/SSL.pm:848: done Net::SSLeay::connect -> 1
Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: DEBUG: .../IO/Socket/SSL.pm:903: ssl handshake done
Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: DEBUG: .../IO/Socket/SSL.pm:3700: * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4)
Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: DEBUG: .../IO/Socket/SSL.pm:3700: * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4)
Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: [debug2] http://localhost/glpi/plugins/glpiinventory/b/esx/?action=getJobs&machineid=miki-ubuntu-2025-03-18-15-51-25
Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: [error] [http client] internal response: 500 Can't connect to localhost:80 (Connection refused)
Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: DEBUG: .../IO/Socket/SSL.pm:3069: free ctx 109818923267808 open=109818923267808
Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: DEBUG: .../IO/Socket/SSL.pm:3073: free ctx 109818923267808 callback
Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: DEBUG: .../IO/Socket/SSL.pm:3080: OK free ctx 109818923267808
Mar 19 12:12:19 miki-ubuntu glpi-agent[182377]: [debug2] child[310252] finished

I tried running the glpi-esx command, and it successfully collects the information:

The agent resolves the FQDN correctly. What I've noticed is that the job is never actually picked up by the agent; it remains in the "Prepared" state:

Thank you,
Michele

[g-bougard]

Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: [debug2] http://localhost/glpi/plugins/glpiinventory/b/esx/?action=getJobs&machineid=miki-ubuntu-2025-03-18-15-51-25
Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: [error] [http client] internal response: 500 Can't connect to localhost:80 (Connection refused)

On such error, this should means you have a "Agent Base URL" set with a wrong URL in Assets tab of your entity. Just remove that URL as you probably don't need it and this should fix the problem:

[mikilt92]

I did a check and the agent base URL was already empty:

Thanks,
Michele

[g-bougard]

If you have sub-entities, check this field on each sub-entity.

If I remove SSL debug, you have this:

Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: [debug2] https://thmzn-glpi.thaumazon.local/plugins/glpiinventory/?action=getConfig&task[ESX]=2.13&machineid=miki-ubuntu-2025-03-18-15-51-25
Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: [debug2] http://localhost/glpi/plugins/glpiinventory/b/esx/?action=getJobs&machineid=miki-ubuntu-2025-03-18-15-51-25
Mar 19 12:12:18 miki-ubuntu glpi-agent[310252]: [error] [http client] internal response: 500 Can't connect to localhost:80 (Connection refused)

Glpi-agent asked your thmzn-glpi.thaumazon.local server for ESX task config for him. We don't have the detailed config as it is not logged, but the following request is constructed with an url which must have been found in the sent back ESX task config. Glpi-agent then requested the job with http://localhost/glpi as base url in place of https://thmzn-glpi.thaumazon.local. This really means GlpiInventory plugin sent back a wrong url to glpi-agent and as far I know, this config url depends on a wrongly set Agent base URL.

[mikilt92]

I've updated the application URL in GLPI's General Setup:

Now the task is being executed by the agent. Thank you very much for the support.

Thanks,
Michele