en	# 6 Zabbix appliance

en	#### Overview Zabbix appliance provides a way to instantly deploy Zabbix server and frontend, instead of setting them up manually or reusing an existing server for Zabbix. The appliance is based on AlmaLinux 8 (x86\_64) and contains a pre-configured Zabbix server running on MySQL and frontend running on Nginx web server. ::: noteimportant This appliance is designed for evaluating Zabbix. Using it in serious production environments is discouraged. ::: Appliance images are available for [download](http://www.zabbix.com/download_appliance) in the following formats: - Installation CD/DVD (.iso) - VMware (.vmx) - see [notes](#vmware) - Open virtualization format (.ovf) - Microsoft Hyper-V (.vhd/.vhdx) - see [notes](#hyper-v) - KVM, Parallels, QEMU, USB stick, VirtualBox, Xen (.raw) - see [notes](#hddflash-image-raw) - KVM, QEMU (.qcow2) Zabbix installation CD/DVD boot menu: ![](../../assets/en/manual/installation_cd_boot_menu1.png){width="600"}
nb-no	#### Overview As an alternative to setting up manually or reusing an existing server for Zabbix, users may [download](http://www.zabbix.com/download_appliance) a Zabbix appliance or a Zabbix appliance installation CD image. Zabbix appliance and installation CD versions are based on AlmaLinux 8 (x86\_64). Zabbix appliance installation CD can be used for instant deployment of Zabbix server (MySQL). ::: noteimportant You can use this Appliance to evaluate Zabbix. The Appliance is not intended for serious production use. :::

en	#### Quick start

en	##### Pre-requisites 1. Make sure the host machine has sufficient resources to meet the virtual machine's system requirements: - *RAM*: 4 GB - *Disk space*: at least 8 GB should be allocated for the virtual machine - *CPU*: 2 cores minimum 2. If not yet installed, install the virtualization software for booting the appliance image (for example, [VirtualBox](https://www.virtualbox.org)). 3. [Download](https://www.zabbix.com/download_appliance) the appliance in the format supported by your virtualization software. 4. Check network settings to ensure that DHCP is enabled on the host machine.

en	##### Installation 1. Boot the appliance virtual machine from the downloaded image. 2. Configure virtual machine network settings to allow access from a browser on the host machine. This can be achieved by enabling *Bridged mode*. 3. Log in to the virtual machine using default system [credentials](#system). 4. To retrieve the IP address, run the following command on the virtual machine: ``` ip addr show ``` 5. Open a browser on the host machine and point it to the IP address the appliance has received over DHCP. 6. Log in to Zabbix using default [credentials](#zabbix-frontend) and start monitoring.

en	#### Configuration This section describes frequently required default configuration settings along with available customization options.

en	##### Credentials ###### System - Username: root - Password: zabbix ###### Zabbix frontend - Username: Admin - Password: zabbix After logging in, you can change default password in the [user profile settings](/manual/web_interface/user_profile#user-profile) or [create new users](/manual/config/users_and_usergroups/user) and delete the default one. ###### Database Passwords for all database users are randomly generated during the installation process. The following users are defined for the database: *Root:* - Username: root - Password: the password is stored in the `/root/.my.cnf` file. It is not required to input a password under the root account. *Zabbix server:* - Username: zabbix_srv - Password: the password is stored in the `/etc/zabbix/zabbix\_server.conf` *Zabbix frontend:* - Username: zabbix_web - Password: the password is stored in the `/etc/zabbix/web/zabbix.conf.php` To change a database user password, modify it in MySQL and the corresponding configuration file.
nb-no	##### - Credentials (login:password) System: - root:zabbix Zabbix frontend: - Admin:zabbix Database: - root:<random> - zabbix:<random> ::: noteclassic Database passwords are randomly generated during the installation process.\ Root password is stored inside the /root/.my.cnf file. It is not required to input a password under the "root" account. ::: To change the database user password, changes have to be made in the following locations: - MySQL; - /etc/zabbix/zabbix\_server.conf; - /etc/zabbix/web/zabbix.conf.php. ::: noteclassic Separate users `zabbix_srv` and `zabbix_web` are defined for the server and the frontend respectively. :::

en	##### Frontend access Zabbix frontend can be accessed at *http://<virtual machine's IP>*. By default, access is allowed from anywhere. To limit the access, modify `/etc/nginx/conf.d/zabbix.conf`. After saving the edited file, restart Nginx by logging in via SSH as [root user](#system) and executing: ``` systemctl restart nginx ```
nb-no	#### - Frontend access By default, access to the frontend is allowed from anywhere. The frontend can be accessed at *http://<host>*. This can be customized in **/etc/nginx/conf.d/zabbix.conf**. Nginx has to be restarted after modifying this file. To do so, log in using SSH as **root** user and execute: systemctl restart nginx

en	##### Static IP address By default, the appliance uses DHCP to obtain the IP address. To set a static IP address: - Log in as [root user](#system). - Run the following commands, replacing values with your custom IP addresses: ``` nmcli connection modify eth0 ipv4.addresses 192.168.1.10/24 # Appliance IP address/CIDR prefix nmcli connection modify eth0 ipv4.gateway 192.168.1.1 # Gateway IP address nmcli connection modify eth0 ipv4.dns 8.8.8.8 # DNS server IP address nmcli connection modify eth0 ipv4.method manual systemctl restart network ``` Alternatively, you can open the file `/etc/NetworkManager/system-connections/eth0.nmconnection` and add the following lines: ``` [ipv4] address1=192.168.1.10/24,192.168.1.1 dns=8.8.8.8 method=manual ``` After saving the edited file, run the command `systemctl restart network`.
nb-no	##### - Using a static IP address By default the appliance uses DHCP to obtain the IP address. To specify a static IP address: - Log in as root user; - Open */etc/sysconfig/network-scripts/ifcfg-eth0* file; - Replace *BOOTPROTO=dhcp* with *BOOTPROTO=none* - Add the following lines: - *IPADDR=<IP address of the appliance>* - *PREFIX=<CIDR prefix>* - *GATEWAY=<gateway IP address>* - *DNS1=<DNS server IP address>* - Run **systemctl restart network** command. Consult the official Red Hat [documentation](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/deployment_guide/s1-networkscripts-interfaces) if needed.

en	##### Firewall configuration To manage firewall settings, the appliance uses iptables with predefined rules: - Open SSH port (22 TCP) - Open Zabbix agent (10050 TCP) and Zabbix trapper (10051 TCP) ports - Open HTTP (80 TCP) and HTTPS (443 TCP) ports - Open SNMP trap port (162 UDP) - Open outgoing connections to NTP port (123 UDP) - Limit ICMP packets to 5 packets per second - Drop all other incoming connections To open additional ports, modify `/etc/sysconfig/iptables` file and reload firewall rules: ``` systemctl reload iptables ```
nb-no	##### - Firewall configuration The appliance uses iptables firewall with predefined rules: - Opened SSH port (22 TCP); - Opened Zabbix agent (10050 TCP) and Zabbix trapper (10051 TCP) ports; - Opened HTTP (80 TCP) and HTTPS (443 TCP) ports; - Opened SNMP trap port (162 UDP); - Opened outgoing connections to NTP port (53 UDP); - ICMP packets limited to 5 packets per second; - All other incoming connections are dropped.

en	##### Repositories Zabbix appliance uses *zabbix-release* package from the Zabbix [repository](https://repo.zabbix.com/zabbix/7.4/release/alma/8/). Repositories are configured in `/etc/yum.repos.d/*` directory.
nb-no	##### - Repositories Official Zabbix [repository](/manual/installation/install_from_packages/rhel) has been added to */etc/yum.repos.d*: [zabbix] name=Zabbix Official Repository - $basearch baseurl=http://repo.zabbix.com/zabbix/7.0/rhel/8/$basearch/ enabled=1 gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-ZABBIX-A14FE591

en	##### Time zone By default, the appliance uses UTC for the system clock. To change the time zone, copy the appropriate file from `/usr/share/zoneinfo` to `/etc/localtime`, for example: ``` cp /usr/share/zoneinfo/Europe/Riga /etc/localtime ``` :::noteclassic Zabbix [frontend time zone](/manual/web_interface/time_zone) is set separately and can be changed in the frontend settings. The default time zone for Zabbix frontend is Europe/Riga. :::
nb-no	##### - Changing time zone By default the appliance uses UTC for the system clock. To change the time zone, copy the appropriate file from */usr/share/zoneinfo* to */etc/localtime*, for example: cp /usr/share/zoneinfo/Europe/Riga /etc/localtime

en	##### File locations - Configuration files are located in `/etc/zabbix` - Zabbix server, proxy, and agent log files are located in `/var/log/zabbix` - Zabbix frontend is located in `/usr/share/zabbix` - The home directory for *zabbix* user is `/var/lib/zabbix`
nb-no	##### - File locations - Configuration files are located in **/etc/zabbix**. - Zabbix server, proxy and agent logfiles are located in **/var/log/zabbix**. - Zabbix frontend is located in **/usr/share/zabbix**. - Home directory for the user **zabbix** is **/var/lib/zabbix**.

en	##### System services Systemd services are available. To see the list of Zabbix services, run the following command on the virtual machine: ``` systemctl list-units zabbix* ```
nb-no	#### - System Services Systemd services are available: systemctl list-units zabbix*

en	#### Image format-specific notes
nb-no	#### - Format-specific notes

en	###### VMware The images in *vmdk* format are usable directly in VMware Player, Server, and Workstation products. For use in ESX, ESXi, and vSphere they must be converted using [VMware vCenter Converter](https://support.broadcom.com/group/ecx/productfiles?subFamily=VMware%20vCenter%20converter&displayGroup=Standard&release=6.6.0&os=&servicePk=203348&language=EN) (authentication required for download). If you use VMware vCenter Converter, you may encounter issues with the hybrid network adapter. In that case, you can try specifying the E1000 adapter during the conversion process. Alternatively, after the conversion is complete, you can delete the existing adapter and add an E1000 adapter.
nb-no	##### - VMware The images in *vmdk* format are usable directly in VMware Player, Server and Workstation products. For use in ESX, ESXi and vSphere they must be converted using [VMware converter](http://www.vmware.com/products/converter/). If you use VMWare Converter, you may encounter issues with the hybrid network adapter. In that case, you can try specifying the E1000 adapter during the conversion process. Alternatively, after the conversion is complete, you can delete the existing adapter and add an E1000 adapter.

en	###### HDD/flash image (raw) To boot the image, run: ``` dd if=./zabbix_appliance_7.4.0.raw of=/dev/sdc bs=4k conv=fdatasync ``` Replace `/dev/sdc` with your Flash/HDD disk device path.
nb-no	##### - HDD/flash image (raw) dd if=./zabbix_appliance_7.0.0.raw of=/dev/sdc bs=4k conv=fdatasync Replace */dev/sdc* with your Flash/HDD disk device.

en	###### Hyper-V If the appliance fails to start up in Hyper-V, try pressing **Ctrl+Alt+F2** to switch a TTY session.

en	#### Troubleshooting If you encounter the error message *Access denied for user 'replace_user'@'localhost' (using password: YES)* while trying to log in to the frontend, it may indicate that the installation is still in progress. ![](../../assets/en/manual/appliance_troubleshoot.png) If the error persists after waiting a few minutes, or if you observe any other unexpected behavior, it likely means that the installation process has not completed successfully. In this case, we recommend deleting the current appliance and redeploying it by following the same installation instructions. This step typically resolves the issue. Note that attempting to manually fix a broken installation is not recommended, as it may lead to further complications.