Dear Forum members,
If you will receive below message after you have initiated a test within the Zabbix Host's WEB.GET(cert) item and
by "zabbix_agent2 -t web.certificate.get[<website_DNS_name>]" command executed at the web server
and also "zabbix_get -s <web server ip address> -k web.certificate.get[<website_DNS_name>]"
"ZBX_NOTSUPPORTED: Cannot fetch data: dial tcp <IP ADDRESS>:443: i/o timeout." ,
please at first hand, check your firewall rules for the web server if the web server is behind the public IP NAT'ed by a local IP.
If your web server is NAT'ted, you have to create a "U-TURN NAT" policy for the web server if your web server is behind the PALO ALTO firewall,
or you have to create a "NAT TURN - HAIR PINNING" policy for the web server if your web server is behind the FORTIGATE firewall.
After you will enable the those above policies, if the other configs have been well set, you will see the SSL certificate data has been fetched successfully.
Hope, this will help.
Kind Regards,
Nuri.
If you will receive below message after you have initiated a test within the Zabbix Host's WEB.GET(cert) item and
by "zabbix_agent2 -t web.certificate.get[<website_DNS_name>]" command executed at the web server
and also "zabbix_get -s <web server ip address> -k web.certificate.get[<website_DNS_name>]"
"ZBX_NOTSUPPORTED: Cannot fetch data: dial tcp <IP ADDRESS>:443: i/o timeout." ,
please at first hand, check your firewall rules for the web server if the web server is behind the public IP NAT'ed by a local IP.
If your web server is NAT'ted, you have to create a "U-TURN NAT" policy for the web server if your web server is behind the PALO ALTO firewall,
or you have to create a "NAT TURN - HAIR PINNING" policy for the web server if your web server is behind the FORTIGATE firewall.
After you will enable the those above policies, if the other configs have been well set, you will see the SSL certificate data has been fetched successfully.
Hope, this will help.
Kind Regards,
Nuri.
since to make zabbix-agent2 work as expected, beside copying certificate files and running update-ca-trust, it was needed only restart of the agent!!
Comment