[comment]: # aside:3

[comment]: # ({2c8167b3-e2c1904c})
# Notes on installation from packages

[comment]: # ({/2c8167b3-e2c1904c})

[comment]: # ({b582c5af-8d855b7c})
#### Overview

Official **pre-release** packages of Zabbix 8.0 are available on the [Zabbix website](https://www.zabbix.com/download?zabbix=8.0&os_distribution=alma_linux&os_version=10&components=server_frontend_agent&db=mysql&ws=apache), where you can select your operating system and Zabbix component to generate installation instructions and commands.

Along with the [package installation notes](#package-installation-notes) below, please also consult the [Installation and setup](/manual/appendix/install) page.

Packages are available for the following Linux distributions:

-   Red Hat Enterprise Linux and its derivatives: AlmaLinux, Amazon Linux 2023, CentOS Stream, CentOS 7, Oracle Linux, Rocky Linux
-   Debian, Ubuntu, Raspberry Pi OS, Raspbian
-   SUSE Linux Enterprise Server, openSUSE Leap

::: noteimportant
Some OS distributions (in particular, Debian-based distributions) provide their own Zabbix packages.
These packages are **not** supported by Zabbix and may be outdated or missing the latest features and bug fixes.
It is recommended to use only official packages from the [Zabbix Official Repository](https://repo.zabbix.com/).
If you previously installed Zabbix from your operating system's repository, see the steps for [upgrading Zabbix packages from OS repositories](/manual/installation/upgrade/packages#zabbix-packages-from-os-repositories).
:::

Packages support MySQL/PostgreSQL database and Apache/Nginx web server.
Note that Zabbix server and proxy cannot share the same database; use different database names if both are installed on the same host.

If necessary, separate packages for Zabbix agent/agent 2, Zabbix get, and Zabbix sender are available at the [Zabbix Official Repository](https://repo.zabbix.com/zabbix/8.0/stable).

Zabbix also provides Zabbix agent pre-compiled binaries for non-Linux operating systems; see:

-   [Windows agent installation from MSI](/manual/installation/install/win_msi)
-   [macOS agent installation from PKG](/manual/installation/install/mac_pkg)
-   [Legacy binaries](https://www.zabbix.com/download_agents?version=2.4&os=HPUX&show_legacy=1) (for older/less common systems, such as HP-UX, NetBSD, Tru64, and older versions of SLES)

[comment]: # ({/b582c5af-8d855b7c})

[comment]: # ({33328630-dc3de2e8})
#### Package installation notes

The following notes apply to all systems:

-   If using PostgreSQL, `DBHost=localhost` (or an IP address) in Zabbix [server](/manual/appendix/config/zabbix_server)/[proxy](/manual/appendix/config/zabbix_proxy#dbhost) configuration makes PostgreSQL use a network socket instead of a local UNIX socket; see [SELinux configuration](#selinux-configuration) for related setup instructions.
-   If using TimescaleDB, see additional [TimescaleDB setup](/manual/appendix/install/timescaledb).
-   If installing Zabbix [Java gateway](/manual/concepts/java) (for monitoring JMX applications), see additional setup instructions for [RHEL-based systems](/manual/concepts/java/from_rhel) and [Debian-based systems](/manual/concepts/java/from_debian_ubuntu).
-   For running Zabbix agent as root, see [Running agent as root](/manual/appendix/install/run_agent_as_root).

The following notes apply to RHEL and its derivatives:

-   If you've enabled the EPEL repository for EL9, which also provides Zabbix packages, it must be excluded from package resolution before installing official Zabbix packages; see [Accidental installation of EPEL Zabbix packages](/manual/installation/known_issues#accidental-installation-of-epel-zabbix-packages).
-   For installing Zabbix packages on Red Hat UBI environments, see [Zabbix packages for RHEL on Red Hat UBI environments](/manual/installation/known_issues#zabbix-packages-for-rhel-on-red-hat-ubi-environments).
-   For using [ICMP ping items](/manual/config/items/itemtypes/simple_checks), packages for `fping` are also available at the [Zabbix Official Repository](https://repo.zabbix.com/third-party).

[comment]: # ({/33328630-dc3de2e8})

[comment]: # ({d731fd80-7e862504})
#### SELinux configuration

Zabbix uses socket-based inter-process communication.
On systems where Security-Enhanced Linux (SELinux) is enabled, you may need to add SELinux rules to allow Zabbix create/use UNIX domain sockets in the SocketDir directory.
Socket files are used by Zabbix server (alerter, preprocessing, IPMI) and Zabbix proxy (IPMI), and they're present while the process is running.

Having SELinux enabled in enforcing mode, execute the following commands to enable communication between Zabbix frontend and server:

For RHEL 7 (and later), AlmaLinux, CentOS Stream, Oracle Linux, Rocky Linux 8 (and later):

```bash
setsebool -P httpd_can_connect_zabbix on
```

If the database is accessed over the network (including `localhost` for PostgreSQL), also allow Zabbix frontend to connect to the database:

```bash
setsebool -P httpd_can_network_connect_db on
```

For RHEL prior to 7:

```bash
setsebool -P httpd_can_network_connect on
setsebool -P zabbix_can_network on
```

After applying SELinux settings, restart Apache:

```bash
systemctl restart httpd
```

Optionally, you can install a pre-defined `zabbix-selinux-policy` package from The [Zabbix Official Repository](https://repo.zabbix.com/zabbix/8.0/stable).
This package is provided for all supported OS versions to simplify Zabbix deployment and prevent users from turning off SELinux because of the configuration complexity.

::: noteimportant
For maximum security, it is recommended to set custom SELinux settings.
:::

The `zabbix-selinux-policy` package contains a basic SELinux policy, allowing Zabbix to create and use sockets and enabling HTTPd connection to PostgreSQL (used by frontend).

The source `zabbix_policy.te` file contains the following rules:

```ini
module zabbix_policy 1.2;

require {
    type zabbix_t;
    type zabbix_port_t;
    type zabbix_var_run_t;
    type postgresql_port_t;
    type httpd_t;
    class tcp_socket name_connect;
    class sock_file { create unlink };
    class unix_stream_socket connectto;
}

#============= zabbix_t ==============
allow zabbix_t self:unix_stream_socket connectto;
allow zabbix_t zabbix_port_t:tcp_socket name_connect;
allow zabbix_t zabbix_var_run_t:sock_file create;
allow zabbix_t zabbix_var_run_t:sock_file unlink;
allow httpd_t zabbix_port_t:tcp_socket name_connect;

#============= httpd_t ==============
allow httpd_t postgresql_port_t:tcp_socket name_connect;
```

[comment]: # ({/d731fd80-7e862504})

[comment]: # ({71fa111b-664f0553})
#### Debuginfo packages

Debuginfo packages contain debugging symbols for Zabbix binaries.
They are not required for normal installation or operation but are useful for advanced troubleshooting.

To enable the `zabbix-debuginfo` repository:

-   On RHEL 7, edit `/etc/yum.repos.d/zabbix.repo` and set `enabled=1` for the `zabbix-debuginfo` section:

```ini
[zabbix-debuginfo]
name=Zabbix Official Repository debuginfo - $basearch
baseurl=http://repo.zabbix.com/zabbix/8.0/stable/rhel/7/$basearch/debuginfo/
enabled=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-ZABBIX-A14FE591
gpgcheck=1
```

-   On SUSE, edit `/etc/zypp/repos.d/zabbix.repo` and set `enabled=1` for the `zabbix-debuginfo` section:

```ini
[zabbix-debuginfo]
name=Zabbix Official Repository debuginfo
type=rpm-md
baseurl=https://repo.zabbix.com/zabbix/8.0/stable/sles/15/$basearch/debuginfo/
gpgcheck=1
gpgkey=https://repo.zabbix.com/zabbix/8.0/stable/sles/15/$basearch/debuginfo/repodata/repomd.xml.key
enabled=0
update=1
```

Once enabled, install the packages:

-   On RHEL, install a single package with debug information for all Zabbix components:

```bash
dnf install zabbix-debuginfo
```

-   On SUSE, install component-specific debuginfo packages:

```bash
zypper install zabbix-<component>-debuginfo
```

[comment]: # ({/71fa111b-664f0553})

[comment]: # ({58e91f3a-b2259b50})
#### Enabling unstable release repositories

[comment]: # ({/58e91f3a-b2259b50})

[comment]: # ({b4905f83-9e4d6713})

The instructions below are for enabling unstable Zabbix release repositories (disabled by default) used for minor Zabbix version release candidates.

First, install or update to the latest zabbix-release package. To enable rc packages on your system do the following:

[comment]: # ({/b4905f83-9e4d6713})

[comment]: # ({05bf7fe3-05fb2800})
##### Red Hat Enterprise Linux

Open the `/etc/yum.repos.d/zabbix.repo` file and set enabled=1 for the `zabbix-unstable` repo.

```ini
[zabbix-unstable]
name=Zabbix Official Repository (unstable) - $basearch
baseurl=https://repo.zabbix.com/zabbix/8.0/unstable/rhel/8/$basearch/
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-ZABBIX-A14FE591
```

[comment]: # ({/05bf7fe3-05fb2800})

[comment]: # ({0df3de7c-f13e36b3})
##### Debian/Ubuntu

Open the `/etc/apt/sources.list.d/zabbix.list` and uncomment "Zabbix unstable repository".

```ini
# Zabbix unstable repository
deb https://repo.zabbix.com/zabbix/8.0/unstable/debian bullseye main
deb-src https://repo.zabbix.com/zabbix/8.0/unstable/debian bullseye main
```

[comment]: # ({/0df3de7c-f13e36b3})

[comment]: # ({48cbd395-37a29df2})
##### SUSE

Open the `/etc/zypp/repos.d/zabbix.repo` file and set enable=1 for the `zabbix-unstable` repo.

```ini
[zabbix-unstable]
name=Zabbix Official Repository
type=rpm-md
baseurl=https://repo.zabbix.com/zabbix/8.0/unstable/sles/15/x86_64/
gpgcheck=1
gpgkey=https://repo.zabbix.com/zabbix/8.0/unstable/sles/15/x86_64/repodata/repomd.xml.key
enabled=1
update=1
```

[comment]: # ({/48cbd395-37a29df2})