Zabbix 1.8.4 web monitoring proxy trouble

[r0k5t4r]

Hi,

I can't get web monitoring working behind our proxy.

I setup /etc/profile on Zabbix server as follows:

export https_proxy=http://ssl-cache.local:8080
export http_proxy=http://www-cache.local:8080
export ftp_proxy=http://ftp-cache.local:8080
export HTTP_PROXY=$http_proxy
export HTTPS_PROXY=$https_proxy
export FTP_PROXY=$ftp_proxy
export NO_PROXY=localhost,127.0.0.1,172.*,192.168.202.*

This works fine using curl on the command line, but Zabbix doesn't seem to make use of it. I can monitor Zabbix Server just fine but not e.g. google.de

Can you please confirm that I can set the env variables and zabbix makes use of it. The libcurl manual says:

NOTE: libcurl respects the following environment variables:
http_proxy, HTTPS_PROXY, FTP_PROXY, GOPHER_PROXY, ALL_PROXY, NO_PROXY
If any of those is set, they they will be used by the library for the appropriate protocols.
The tCurl.Proxy property, if set, overrides the environment variables.
Note also that reading this property does not reflect the state of environment.

Please help I have been trying the whole day to get this working....

[r0k5t4r]

Ok, using IP instead of hostname seems to work just for the http_proxy env variable. But this is useless since i need to monitor https and also websites that I excluded from the proxy!

I found a patch that was written by someone in the forum but I can't get it working with 1.8.4.

Maybe it would be a good idea to officially support this patch since it makes sense?

http://www.zabbix.com/forum/showthread.php?t=11475&highlight=web+monitoring+proxy

[r0k5t4r]

Sorry but without proxy supprt this feature is absolutely useless. I can't believe that there are many companies out there not using a proxy server???

[jacifr09]

Monitor External sites

Hi

did you get anywhere with this?, I'm also trying to monitor an external https site with no luck using the exported http/https settings

rgds

Ja

[untergeek]

You ought to have your Zabbix Server in a DMZ which can do an end-run around the proxy. That's what we have in our environment. You should probably see if your network can do the same. It doesn't make sense to put production monitoring equipment behind the user-land proxy.