connection refused on second proxy

[andreaf-it]

Hello, I have a server on cluod and a proxy on local network and work properly.
I added a second proxy on other lan with the same configuration of the first one but receive always

Unable to connect to the server SERVERIP]:10051 [cannot connect to [[SERVERIP]:10051]: [111] Connection refused]

[tim.mooney]

Does the firewall on your cloud-based Zabbix server allow incoming connections on port 10051 from the IP address for your new Zabbix proxy?

Did define the new proxy as an "Active" proxy in Administration->Proxies on your Zabbix server?

[andreaf-it]

Hi Tim,
attach the screen of firewall on azure server, for the moment I have a single rule that open 10051 port from any
Attach also teh screen of active proxy configuration

[tim.mooney]

I was expecting that it would be required that you specify the proxy address for an active proxy, but the proxy setup documentation implies that if you leave it blank then any active proxy can connect. I guess I would never do that when running the Zabbix server in the cloud, because it allows anyone to impersonate a proxy and potentially download information about your clients that are monitored by the proxy.

What happens if you fill in the IP address of the new proxy and update that proxy config in Administration->Proxies? Does it make any difference?

Also, does the HostName on the proxy exactly match the (obscured) proxy name in the Proxies config? The docs say that's a requirement.

[andreaf-it]

Hi Tim, I just tried to adding public proxy IP address and tried with local proxy IP address on server interface but receive always

Unable to connect to the server [SERVERIP]:10051 [cannot connect to [[SERVERIP]:10051]: [111] Connection refused]

Confirm that hostname on the server and in the setting file on the proxy is exaclty the same (for exclude error I use copy/past :-) )

For exclude that anyone to impersonate proxy, when the proxy will work properly, I will set psk encryption and will set IP filter on the server firewall but for the test prefer leave open.

[andreaf-it]

Hi tim, good news, the problem was on the company firewall, also if i opened 10050 and 10051 ports, proxy cannot connect with server but the stranger thing is that from an other windows machine the same ports worked properly. I tried to open all port and work properly. Now I'm trying to shrink the range ports but I don't yet foud the right port :-)
Thank you for your support and above all for your opinion about set ip on proxy configuration.
Ciao

SOLVED :-)