> For the complete documentation index, see [llms.txt](https://ghoulsec.gitbook.io/ghoulsec-vault/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ghoulsec.gitbook.io/ghoulsec-vault/security-operations/zabbix-nms/zabbix-proxy.md).

# Zabbix Proxy

In Zabbix, a **proxy** is an intermediary server that collects monitoring data from monitored devices (hosts) and sends it to the Zabbix server. The proxy helps distribute the load, especially in large environments, and can also be used to monitor devices in remote locations where a direct connection to the Zabbix server is not feasible.

<details>

<summary>Proxy types</summary>

In Zabbix, **active** and **passive proxies** refer to different ways a proxy communicates with the Zabbix server.

#### 1. **Active Proxy**:

* The **proxy initiates communication** with the Zabbix server.
* It sends collected data to the server and also fetches configuration updates.
* Useful when the proxy is behind a firewall or in a remote location where the server cannot initiate connections.
* **Pros**: No need for the Zabbix server to reach the proxy, making it ideal for networks with restricted inbound access.
* **Cons**: Slightly more complex to configure in some environments with strict firewalls.

#### 2. **Passive Proxy**:

* The **Zabbix server initiates communication** with the proxy.
* The proxy waits for the server to request data from it.
* Useful when the Zabbix server has access to the proxy, but the proxy cannot easily initiate communication with the server (e.g., due to NAT or firewall restrictions).
* **Pros**: Simpler to set up when the server can reach the proxy directly.
* **Cons**: Requires the server to be able to pull data from the proxy.

#### Summary:

* **Active Proxy**: Proxy pushes data to the server.
* **Passive Proxy**: Server pulls data from the proxy.

In practice, active proxies are more commonly used, as they are more flexible in various network environments.

</details>

## Installating Zabbix Proxy

We can follow the documentation on the official zabbix page to install the lastest zabbix proxy packages and intrgrate it with zabbix sever.

{% hint style="info" %}
<https://www.zabbix.com/download>
{% endhint %}

Once zabbix proxy is installed we will make the following configuration changes :&#x20;

```bash
sudo nano /etc/zabbix/zabbix_proxy.conf
```

> Note : Proxy has its own database server which is configured while installation.

We will change the following parameters :&#x20;

```bash
# Proxy Mode (0=Active 1=Passive)
ProxyMode = 0
# Connectivity
Server = <zabbix_server_ip>
Server Active = <zabbix_server_ip>
ListenPort = 10051 # CHANGE THIS IF MULTIPLE PROXY
# Hostname 
Hostname = <hostname>
# DB Configuration 
DBHost = <database_ip>
DBName = <database_name>
DBUser = <database_user>
DBPassword = <database_password>
```

Once done we will restart the zabbix proxies and add the zabbix proxies on the zabbix server dashboard.

```bash
sudo systemctl enable zabbix-proxy
sudo systemctl start zabbix-proxy
```

***

On the Zabbix dashboard we will add the proxies inside `Administration > Proxies` on the zabbix dashboard.

<figure><img src="/files/DkfYIPQ7n4esPxddDg6v" alt=""><figcaption></figcaption></figure>

After some time the proxies will enabled and start getting data throught the proxy.

***

## Proxy Groups&#x20;

Once proxies are deployed we can add them into groups which will act as the HA and load balancer for the zabbix hosts.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://ghoulsec.gitbook.io/ghoulsec-vault/security-operations/zabbix-nms/zabbix-proxy.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.