Ad Widget

Collapse

net.tcp.service not working properly

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • tzzui
    Junior Member
    • Sep 2020
    • 18

    #1

    net.tcp.service not working properly

    I'm using net.tcp.service to monitor a website. Zabbix says that the HTTPS service is down when it is clearly not. I currently have no idea why. I would like to look at the log files and see what kind of error/response zabbix is getting, but i can't seems to find the right one. The only one i found is at /var/log/zabbix/zabbix_server.log ,but that one does not contain the info i want.
  • Hamardaban
    Senior Member
    Zabbix Certified SpecialistZabbix Certified Professional
    • May 2019
    • 2713

    #2
    To check, try connecting using curl



    https

    Uses (and only works with) libcurl, does not verify the authenticity of the certificate, does not verify the host name in the SSL certificate, only fetches the response header (HEAD request). Default port 443 is used if not specified.

    Comment

    • tzzui
      Junior Member
      • Sep 2020
      • 18

      #3
      Originally posted by Hamardaban
      To check, try connecting using curl



      https

      Uses (and only works with) libcurl, does not verify the authenticity of the certificate, does not verify the host name in the SSL certificate, only fetches the response header (HEAD request). Default port 443 is used if not specified.
      running "zabbix_get -s 127.0.0.1 -k 'net.tcp.service[https,URL]'" outputs "1"

      and "curl -I https://URL:443" gives me the complete header with "200" code

      To me as an ine it looks like everything is working well.

      Okay so i did a thing: I just changed the host IP from the external one to our internal IP and now it says that HTTP is down and HTTPS is up whereas if i use the external it says HTTPS is down and HTTP is up?!

      Comment

      Working...