Web monitoring via a proxy

[patrick]

Hi,

I want to test web access with a simple web scenario.
Everything is OK with Intranet Web servers but if I try to test Internet Web Servers I get this status "...Error: Timeout was reached" and in the zabbix_server.log "Error doing curl_easy_perform [Timeout was reached]".

If I try thie curl command like "curl www.google.com" It's OK.

I have created a .curlrc file for zabbix user with this line:
--proxy "http://myproxy:3128/"

Who could help me?

Thanks

[patrick]

I've found

To monitor a web site via a proxy it's OK with a http_proxy variable , not using a curlrc file.

[simonc]

Hello,

could you please detail your method ?
Did you put the http_proxy variables in the Variables field on the "scenario config" page ?

It is possible to use a login/password to authenticate to the proxy ?

Thanks.
Regards

Simon

[Kevin312]

I've got web proxy connectivity working, with usernames and passwords (proxy authentication). I had to modify the "httppoller" library to enable proxy support in libcurl.

See https://www.zabbix.com/forum/node/14938 for my patch, written for v1.6.5 (should be trivial to port).

[simonc]

I've got web proxy connectivity working, with usernames and passwords (proxy authentication). I had to modify the "httppoller" library to enable proxy support in libcurl.

See https://www.zabbix.com/forum/node/14938 for my patch, written for v1.6.5 (should be trivial to port).

Hi, thanks for your patch

In my case, i solved my problem with curl and UserParameter :

curl --proxy-ntlm -U userName:Password -x http://192.168.0.1:8080 --url http://www.google.com

[saugerle]

curl solution questions

Hi,

How to apply your solution please? http_proxy is not working for me very well.
Can this be done per step somehow, too?

I have to monitor several hundred production application environments each at serveral levels.

Once the direct server instances reachable via external Apache port without going through a proxy.

Secondly, I have to monitor the same instances via internal application server port to read out if the instance feels fine or not.

Instances are usually clustered and load balanced. So another step to monitor is the load balancer, usually no proxy is needed for this.

The last and trouble-making level is a external or internal proxy (or reverse proxy) for which the access through the company web proxy is required.
Many are HTTPS URL's, some certificates, internal type, are self signed.
So even wget with the http_proxy setting runs into problems without additional parameter.

Could you solution help here?

Regards,

saugerle

[r0k5t4r]

Sorry to pick up on this old thread but I'm trying to setup a web monitoring scenario but this is not working and I'm pretty sure it has to do with the proxy auth...

We have a proxy server that requires authentication and I created a local .curlrc file for the zabbix user on the zabbix server. The file works great if I use the curl command line command. However the zabbix server doesn't seem to use this file?

I'm using Zabbix 1.8.2.