Simple checks: ambiguous results

[banzayats]

Hello

I have the following issue. I use simple checks (net.tcp.service[service_name]) to monitor general services such as http, https, ftp, pop etc.

But some checks (https and ftp) behave very strangely. All hossts notify me that I have the problem: 'HTTPS (FTP) service is down on {HOST.NAME}'
And indeed - the status of these checks is equal to 0.
But at the same time, if I run zabbix_get from Zabbix server or proxy:

zabbix_get -s myhostname.com -k "net.tcp.service[ftp]"

or

zabbix_get -s myhostname.com -k "net.tcp.service[https]"

the result is 1!
How can this be?

[Atsushi]

Simple check will check if it can connect to the port from Zabbix server.
It is can be retrieved using the zabbix_get, check the service in the host from the Zabbix agent.

Can you connect the server and protocol(port) specified from Zabbix server?
Do not limit by Firewall?

[banzayats]

Simple check will check if it can connect to the port from Zabbix server.
It is can be retrieved using the zabbix_get, check the service in the host from the Zabbix agent.

Can you connect the server and protocol(port) specified from Zabbix server?
Do not limit by Firewall?

Telnet to port 443 works fine. So the firewll rules do not restrict access from zabbix server/proxy.