cannot connect to 127.0.0.1:10051

[mario_rossi]

Hi,
I'm having problems connecting the windows machine with active agent to the zabbix server. I receive the following errors in the .log file

2024/08/22 20:02:49.734818 Zabbix Agent2 hostname: [HQ]
2024/08/22 20:02:50.739746 [101] cannot connect to [127.0.0.1:10051]: dial tcp :0->127.0.0.1:10051: connectex: Impossibile stabilire la connessione. Rifiuto persistente del computer di destinazione.
2024/08/22 20:02:50.739746 [101] active check configuration update from host [HQ] started to fail
2024/08/22 20:02:50.739746 [101] cannot connect to [127.0.0.1:10051]: dial tcp :0->127.0.0.1:10051: connectex: Impossibile stabilire la connessione. Rifiuto persistente del computer di destinazione.
2024/08/22 20:02:50.739746 [101] sending of heartbeat message for [HQ] started to fail

Can you help me solve the problem?

[Markku]

Zabbix agent is not correctly configured with ServerActive directive as it is trying to connect to localhost (127.0.0.1) instead of your Zabbix server.

Or, you need to restart the agent after changing the configuration file.

Markku

[idkmyusername]

Hi,
Did you open port 10051 in firewall on that Windows machine?

[Markku]

Zabbix agent is not correctly configured with ServerActive directive as it is trying to connect to localhost (127.0.0.1) instead of your Zabbix server.

Or, you need to restart the agent after changing the configuration file.

Markku

[yylinnn]

Maybe you should paste the config of zabbix agent

[mario_rossi]

Hi guys, thanks so much for your help. It was a configuration error with the active server, it was not configured correctly.
Thanks, problem solved.

[robin_bolli]

Hi Mario,

I believe I have the same issue with my Zabbix server. Could you please tell me how you solved it?

Thank you!

Best regards,
Robin

[robin_bolli]

Solved, i forgot to set StartVMwareCollectors=1

[ModularConfusion]

Having the same issue. There is a proxy running on localhost, so I do want it to connect to localhost. However, there are numerous proxies here in a proxy group, so my guess is this is the issue.