Quote from: Victor Kirhenshtein on January 31, 2023, 06:03:16 PMHi!Thank you for your prompt response!
I was unable to reproduce telnet service check issue. "[ 136] INT32 2" in response indicates connection problem, so agent was unable to connect to given address and port. Could it be that address is a loopback?
For HTTPS checks - it could be certificate issue. Unfortunately agent do not log exact failure reason (I fixed it already in development branch). Try to do same request with curl from command line (using URL exactly as logged - https://x.x.x.x:443/api/status) - will you get any errors?
Best regards,
Victor
Regarding HTTPS check, the thing is netsvc does the check against the IP address, instead of the URL that i have in my request field, so naturally the SSL certificate check would fail. (e.g sending to https://$IP_ADDRESS:443/api/status instead of https://my.host/api/status). As about the telnet check it does say it sends it to the public ip address. ( ** 000000: [ 8] INETADDR $REMOTE_PUBLIC_IP_ADDR). Note that all of the tests were working fine with previous version 4.2 (portcheck).