web.page.regexp on Windows 2012 R2 - Unsupported scheme: https.

[Hy3n4]

Hi,

I've run into a problem with web.page.regexp monitoring on Windows. I get NOT SUPPORTED with result Unsupported scheme: https.

Only issue I can thing of is that agent is not compiled with curl ssl support.

Here is example from actual discovery item.

{
"{#SCHEME}": "https",
"{#SSL}": true,
"{#SITEPORT}": 443,
"{#SITEPATH}": "",
"{#SITEDNS}": "hidden-url.ltd"
},

Here is item:

web.page.regexp[{#SCHEME}://{#SITEDNS}:{#SITEPORT}/{#SITEPATH},,,"(HTTP/1\.1 )([0-9]{3})( .*)",12,"\2"]

Can anybody help me figure out what is causing this?

Thanks

Installed versions:
Zabbix Server: 4.2.4
Zabbix Agent: 4.2.4 OpenSSL (from Zabbix download page)
OS: 6.3.9600 Microsoft Windows Server 2012 R2 Standard x64

[Hamardaban]

From https://www.zabbix.com/documentation...s/zabbix_agent :

⁵ SSL (HTTPS) is supported only if agent is compiled with cURL support. Otherwise the item will turn unsupported.

[Hy3n4]

That’s exactly what I thought. But I was unable to find any explicit info how is Windows agent compiled by default.

Thanks

[Timkaz]

Hi.

Where i can get zabbix agent for Windows x64 compiled with cURL support?
I tried many 4.x (zips and msi: 4.0.14,4.2.3,4.2.4,4.2.8,4.4.0,4.4.1) precompiled versions for windows from https://www.zabbix.com/download_agents , but found no one with support scheme https

[Hy3n4]

Have the same problem.

[seanwasere]

For checking https endpoints from windows agents using web.page. keys,
one option you have is to set up a port 80 -->443 redirect on your endpoint.
eg, a 301 redirect directive in your endpoints nginx config
or possibly an iptables prerouting rule ( I havent tested this using a prerouting rule myself)