Stumped - zabbix_proxy-cannot-connect-13-permission-denied

[steeladept]

I have 6 proxy servers (really 7, but one is irrelevant) all setup the same as best as I can tell. 2 connect to the Application Server just fine, the other 4 are getting the Proxy Cannot Connect error shown in the subject line. I did research and found this entry: https://www.zabbix.com/forum/zabbix-...mission-denied but that did not solve the issue. SELinux is already set to permissive mode on all boxes.

In addition, I have verified communication between the Application Server and the Proxy servers on both ports 10050 and 10051 in both directions (even though that isn't strictly necessary - 10050 from Application Server to Proxy and 10051 from Proxy to Application server *should* be sufficient).

So with all firewalls out of the way, and SELinux out of the way, and the config file being exactly the same across all Proxies - what else could I be missing?

[steeladept]

ANSWER - Digging deeper, I figured it out. The machine name (in the application) included the domain name, but the proxy was looking for it without the domain name. Once I made them match it started working. For those who have a similar issue, you can resolve it several ways, but the way I did it was to use nmtui, change the machine name to the FQDN name, then deleted the device in the Application and let my Auto-registration rules find it. If you setup the machine manually instead of the auto-registration, you can just change it, if necessary, to make them match.