HTTP Agent check works on Server but not on Proxy

[TheFactor82]

Hi everyone,
I've a weird situation where a simple template with some http agent checks is applied to a host monitored by my Zabbix Server, and they works as expected.
But when I try to link this template to a host monitored by Zabbix Proxy (and that's what I need), http check seems to "sleep" all the time.
In the "Latest data" section they are without any data, but the ITEM doesn't go in an "unsupported" status. Simply they stay there, It seems like the proxy doesn't take care of these items.
The Zabbix administration - QUEUE shows these items as delayed.

Someone can help me to understand what I'm missing?
Thanks a lot in advance!

[tim.mooney]

But when I try to link this template to a host monitored by Zabbix Proxy (and that's what I need), http check seems to "sleep" all the time.
In the "Latest data" section they are without any data, but the ITEM doesn't go in an "unsupported" status. Simply they stay there, It seems like the proxy doesn't take care of these items.
The Zabbix administration - QUEUE shows these items as delayed.

That is strange. I looked at the http agent documentation https://www.zabbix.com/documentation...itemtypes/http just to verify that this isn't a type of check that can only run on the zabbix server, and the documentation says that the proxy can do it.

A couple things I would check:

1. if you built your own proxy package or binaries, are you sure it was built with libcURL support? That's a requirement for http agent checks.
2. can you sucessfully use curl or wget from a command line directly on the proxy to access the web page in question? I'm just wondering if the problem is a more general "proxy can't access the web server on host A" issue, rather than being something specific to Zabbix or the check.

[TheFactor82]

Documentations indeed says that proxies can do http agents checks...

Answering to your questions:
1. No, I've installed the proxy on a Centos machine with the classic yum package.
2. Yes, I can succesfully curl from command line the url required.

I don't know what I can check for this problem...