Ad Widget

Collapse

7.4.6 - SSL certificate monitoring on Zabbix Agent 2 not creating items

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Adam Stadnick
    Junior Member
    • Feb 2021
    • 14

    #1

    7.4.6 - SSL certificate monitoring on Zabbix Agent 2 not creating items

    I'm trying to set up SSL certificate monitoring on Windows hosts. The hosts are all running Zabbix Agent 2.

    Running zabbix_get with web.certificate.get directly on the host returns a valid response for each host. While it took several hours of waiting before discovery started working, the hosts do all have items to monitor with the correct names. However, those items are blank. (I missed my window to update the topic title, I apologize for the confusion - initially, no hosts would create items over a span of several hours, but right after I posted this, they started working)

    The "Get data" item has data in it, in the following format:

    {"error":{"message":"","code":0},"data":[{"hostname":"<FQDN>","port":"443","ip":"<FQDN>" ,"k ey":"<FQDN>, <FQDN>"}]}

    (Note: I am using the FQDN of the web service rather than the IP. This is the same methodology I used with zabbix_get, which returned a valid certificate, but doesn't seem to be working via Zabbix proper. However, using the IP of the host instead doesn't return any data at all and I'm not sure why).

    I've tried reuploading the template, which returned 'no changes' when I uploaded it. Just to be safe, I deleted the template and all related items off all hosts and re-uploaded a fresh copy of the template from the official repo, but the behavior is the same.

    Edited post multiple times, as behavior has changed - all hosts are now running discovery (eventually), but not returning valid data yet.
    Last edited by Adam Stadnick; 13-01-2026, 23:01.
  • Adam Stadnick
    Junior Member
    • Feb 2021
    • 14

    #2
    After waiting over a day, the items are all still blank on both hosts. The "Get data" item returns the same values as in the previous post:

    {"error":{"message":"","code":0},"data":[{"hostname":"<value of hostname macro>","port":"443"," ip":"<value of IP macro>","key":"<value of hostname macro>, <value of IP macro>"}]}

    I'm stumped. Running web.certificate.get on the agent with the same values still works and returns the expected certificate data. It just doesn't work when invoked from the server for some reason.

    I'd love any help figuring out what I am doing wrong, or if there's something wrong with the environment.

    Comment

    • Adam Stadnick
      Junior Member
      • Feb 2021
      • 14

      #3
      Okay, rereading the syntax of web.certificate.get, it looks like the issue is that the server is requesting <FQDN, IP> where the agent is expecting <FQDN, port>. This seems to be caused by specifying both the DNS name and IP in the macros. Removing the IP didn't work, but I'm continuing to test various combinations of macros being set/unset to see if I can get a working configuration.

      Comment

      Working...