bolt Valebyte VPS from $4/mo — NVMe, 60s deploy.

Get a VPS arrow_forward
eco Beginner Tutorial/How-to

Installing Zabbix Server

calendar_month Jun 13, 2026 schedule 17 min read visibility 61 views
Установка Zabbix Server на VPS: Комплексный мониторинг и алертинг
info

Need a server for this guide? We offer dedicated servers and VPS in 50+ countries with instant setup.

Need a server for this guide?

Deploy a VPS or dedicated server in minutes.

Installing Zabbix Server on a VPS: Comprehensive Monitoring and Alerting

TL;DR

In this detailed guide, we will step-by-step configure Zabbix Server version 7.0 LTS on the Ubuntu Server 24.04 LTS operating system, using PostgreSQL 16, Nginx, and PHP 8.3. You will learn how to install all necessary components, configure them for optimal operation, ensure security, and set up basic monitoring to obtain a powerful and flexible system for tracking the status of your servers and applications.

  • Install Zabbix Server 7.0 LTS on Ubuntu Server 24.04 LTS.
  • Configure PostgreSQL 16 database for Zabbix data storage.
  • Deploy the Zabbix web interface using Nginx and PHP 8.3.
  • Ensure basic server security using UFW and Fail2ban.
  • Set up automatic backups of key Zabbix data.
  • Address common problems and their solutions.

What we are configuring and why

Diagram: What we are configuring and why
Diagram: What we are configuring and why

We will be installing Zabbix Server — a powerful, versatile, and completely free open-source monitoring system. Zabbix allows collecting data on the performance and availability of virtually any network devices, servers, virtual machines, cloud services, and applications. It can track thousands of different metrics, such as CPU load, memory usage, disk space, network traffic, process status, application logs, and much more.

Ultimately, the reader will get a fully functional monitoring system capable of collecting data, visualizing it on dashboards, analyzing trends, and most importantly, generating alerts when parameters exceed predefined thresholds. This will allow for prompt reaction to problems before they affect end-users and help maintain a high level of availability for your services.

There are various approaches to monitoring. Cloud-managed solutions (e.g., AWS CloudWatch, Google Cloud Monitoring, Datadog) can be used, offering convenience and scalability for a subscription fee. However, deploying Zabbix on your own VPS or dedicated server has several advantages:

  • Full Control: You have complete control over data, configuration, and security.
  • Cost Savings: No monthly monitoring fees; only the server itself is paid for.
  • Flexibility: Ability for deep customization to meet the specific needs of your infrastructure.
  • Privacy: Your monitoring data does not leave your infrastructure, which is critical for some projects.

Thus, Zabbix on a VPS is an ideal solution for those seeking a powerful, flexible, and cost-effective monitoring tool with full control over their data.

What VPS configuration is needed for this task

Diagram: What VPS configuration is needed for this task
Diagram: What VPS configuration is needed for this task

The choice of VPS configuration for Zabbix Server depends on the scale of monitoring. The more devices, data items, and triggers you plan to track, the more powerful the server should be. Zabbix is quite resource-intensive, especially its database, so it's not advisable to skimp on resources.

Minimum requirements for Zabbix Server (for small infrastructures, up to 50 devices):

  • CPU: 2 vCPU. Zabbix Server actively uses the processor for data processing and checks.
  • RAM: 4 GB. RAM is critical for the database (PostgreSQL or MySQL) and Zabbix Server processes.
  • Disk: 80 GB SSD. SSD significantly speeds up database operations, which is important for Zabbix performance. The volume depends on the depth of historical data storage.
  • Network: 100 Mbps or 1 Gbps. For data transfer from agents and access to the web interface.

Recommended VPS plan for medium tasks (up to 200 devices, several thousand metrics):

For more serious tasks requiring monitoring of up to 200 devices with frequent data collection, more powerful resources are needed. For example, you can opt for a VPS with 4 vCPU, 8 GB RAM, and 200 GB SSD. This will ensure stable Zabbix operation, allow storing more historical information, and processing more requests without delays. Make sure your provider offers a stable and fast SSD (NVMe is preferable) and sufficient network bandwidth.

When a dedicated server is needed, not a VPS

A dedicated server becomes preferable when:

  • Very large infrastructure: Monitoring hundreds or thousands of devices, collecting millions of metrics per minute.
  • Long-term data storage: The need to store years of historical data, requiring terabytes of disk space.
  • High database performance: A VPS might have IOPS limitations, which is critical for high-load Zabbix databases. A dedicated server provides guaranteed disk subsystem performance.
  • Isolation requirements: Complete physical isolation from other provider clients.

For most tasks, especially at the initial stage, a powerful VPS will suffice, but as the infrastructure grows, it's worth considering a transition to a dedicated server.

Location: what it affects

The choice of VPS location is also important:

  • Latency: Place the Zabbix Server as close as possible to the monitored objects (agents) to minimize data collection delays. High latency can lead to false trigger activations or missed metric collections.
  • Geographical distribution: If your infrastructure is distributed across different continents, consider deploying multiple Zabbix Proxies in regions to collect data and then forward it to the central Zabbix Server.
  • Legislation: Consider data retention laws in the chosen location if this is critical for your project.

Server preparation

Diagram: Server preparation
Diagram: Server preparation

Before installing Zabbix, it is necessary to perform basic security configuration and update the operating system. We will be using Ubuntu Server 24.04 LTS.

1. SSH Connection and User Creation

Connect to your VPS via SSH as the root user or the user provided by your hosting provider. Then, create a new user with limited privileges for daily work and add them to the sudo group.


# Создаем нового пользователя (замените 'youruser' на желаемое имя)
sudo adduser youruser

# Добавляем пользователя в группу sudo
sudo usermod -aG sudo youruser

# Переключаемся на нового пользователя
su - youruser

Going forward, all commands will be executed as this user using sudo.

2. System Update

Always start by updating the package list and the system itself to ensure you have the latest versions of all components and security fixes installed.


# Обновляем список пакетов
sudo apt update

# Обновляем установленные пакеты
sudo apt upgrade -y

# Перезагружаем сервер, если требуется обновление ядра
sudo reboot

After rebooting, reconnect via SSH.

3. Firewall Configuration (UFW)

Enable Uncomplicated Firewall (UFW) and allow only the necessary ports. For Zabbix, we will need SSH (port 22), HTTP (port 80), and HTTPS (port 443), as well as the Zabbix Server port (10051) and Zabbix Agent port (10050) for interaction with the server itself and agents.


# Разрешаем SSH (порт 22)
sudo ufw allow ssh

# Разрешаем HTTP (порт 80)
sudo ufw allow http

# Разрешаем HTTPS (порт 443)
sudo ufw allow https

# Разрешаем порт Zabbix Server (для входящих соединений от агентов/прокси)
sudo ufw allow 10051/tcp

# Разрешаем порт Zabbix Agent (если Zabbix Agent будет установлен на этом же сервере и мониторить его)
sudo ufw allow 10050/tcp

# Включаем UFW
sudo ufw enable

Confirm firewall activation by typing y. You can check the UFW status with the command sudo ufw status.

4. Install Fail2ban

Fail2ban helps protect the server from brute-force attacks by blocking IP addresses that make too many failed login attempts.


# Устанавливаем Fail2ban
sudo apt install fail2ban -y

# Включаем и запускаем сервис Fail2ban
sudo systemctl enable fail2ban
sudo systemctl start fail2ban

Fail2ban is configured by default to protect SSH. You can add additional rules if needed.

5. Install Basic Utilities

Install several useful utilities that will come in handy during setup and administration.


# Устанавливаем curl, wget, git, htop, nano
sudo apt install curl wget git htop nano -y

Software Installation — Step-by-step

Software Installation — Step-by-step

Diagram: Software Installation — Step-by-step
Diagram: Software Installation — Step-by-step

In this section, we will install all the necessary components for Zabbix Server 7.0 LTS to work: PostgreSQL 16 database server, Nginx web server, PHP 8.3, and Zabbix Server itself.

1. Installing PostgreSQL Server 16

Zabbix can use various databases, but PostgreSQL is an excellent choice for performance and reliability. Ubuntu 24.04 LTS comes with PostgreSQL 16.


# Install PostgreSQL 16 and additional modules
sudo apt install postgresql postgresql-contrib -y

# Check PostgreSQL service status
sudo systemctl status postgresql

Ensure that the service is running and active.

2. Creating Zabbix Database and User

Let's create a new PostgreSQL database and user specifically for Zabbix, and set a password for this user. Use a strong password!


# Switch to postgres user to work with the DB
sudo -u postgres psql

# Create zabbix database
CREATE DATABASE zabbix ENCODING 'UTF8' LC_COLLATE 'en_US.UTF-8' LC_CTYPE 'en_US.UTF-8' TEMPLATE template0;

# Create zabbix user and set password (replace 'your_db_password' with a strong password)
CREATE USER zabbix WITH PASSWORD 'your_db_password';

# Grant all privileges to zabbix user for zabbix database
GRANT ALL PRIVILEGES ON DATABASE zabbix TO zabbix;

# Exit psql
\q

3. Installing Zabbix Server 7.0 LTS

Let's add the official Zabbix repository for Ubuntu 24.04 and install the necessary packages.


# Download and install Zabbix 7.0 LTS repository for Ubuntu 24.04
wget https://repo.zabbix.com/zabbix/7.0/ubuntu/pool/main/z/zabbix-release/zabbix-release_7.0-1+ubuntu24.04_all.deb
sudo dpkg -i zabbix-release_7.0-1+ubuntu24.04_all.deb

# Update package list after adding the repository
sudo apt update

# Install Zabbix Server with PostgreSQL support, Zabbix Frontend with Nginx, and Zabbix Agent
sudo apt install zabbix-server-pgsql zabbix-frontend-php zabbix-nginx-conf zabbix-agent -y

This command will install Zabbix Server, the web interface, Nginx configuration for Zabbix, and Zabbix Agent (which will monitor the Zabbix server itself).

4. Importing Initial Database Schema

Now it is necessary to import the initial Zabbix schema and data into the created database. When prompted for a password, enter the password for the zabbix user that you set earlier.


# Import schema and data (password for zabbix user will be prompted)
sudo -u zabbix psql -h localhost zabbix < /usr/share/zabbix-sql-scripts/postgresql/server.sql

If the command executes without errors, the Zabbix database schema will be successfully imported.

5. Configuring PHP for Zabbix Frontend

Zabbix Frontend requires specific PHP settings. By default, Zabbix-Nginx-Conf installs PHP-FPM, but we need to ensure that all parameters meet the requirements.


# Open PHP-FPM configuration file (for PHP 8.3)
sudo nano /etc/php/8.3/fpm/php.ini

Find and modify (or add, if missing) the following parameters:


max_execution_time = 300
max_input_time = 300
memory_limit = 256M
post_max_size = 16M
upload_max_filesize = 16M
date.timezone = Europe/Moscow ; Replace with your timezone

Save changes (Ctrl+O, Enter, Ctrl+X).

6. Configuring Nginx

The zabbix-nginx-conf package has already provided a configuration file for Nginx. It is usually located in /etc/nginx/conf.d/zabbix.conf or /etc/nginx/sites-available/zabbix.conf. Ensure that Nginx is configured to listen on the correct PHP-FPM port.


# Check Nginx configuration file for Zabbix
sudo nano /etc/nginx/conf.d/zabbix.conf

Ensure that the location ~ \.php$ section points to the correct PHP-FPM socket (for PHP 8.3, this is usually /run/php/php8.3-fpm.sock):


# Example zabbix.conf content (ensure fastcgi_pass matches your PHP version)
server {
    listen 80;
    server_name your_domain_or_ip; # Replace with your VPS IP or domain name

    root /usr/share/zabbix;
    index index.php;

    location / {
        try_files $uri $uri/ =404;
    }

    location ~ /\.ht {
        deny all;
    }

    location ~ \.php$ {
        fastcgi_pass unix:/run/php/php8.3-fpm.sock; # Ensure this matches your PHP-FPM version
        fastcgi_index index.php;
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
        include fastcgi_params;
        fastcgi_buffers 16 16k;
        fastcgi_buffer_size 32k;
    }
}

Save changes if any were made.

Configuration

Diagram: Configuration
Diagram: Configuration

After installing all components, it is necessary to perform the final configuration of Zabbix Server, Nginx, and PHP-FPM, as well as ensure security using TLS/HTTPS.

1. Configuring Zabbix Server

Edit the main Zabbix Server configuration file to specify database connection parameters.


# Open Zabbix Server configuration file
sudo nano /etc/zabbix/zabbix_server.conf

Find and modify the following lines, using the password you set for the zabbix user in PostgreSQL:


DBHost=localhost
DBName=zabbix
DBUser=zabbix
DBPassword=your_db_password ; Replace with your strong password

Save changes (Ctrl+O, Enter, Ctrl+X).

2. Starting and Enabling Services

After all configurations, you can start Zabbix Server, Nginx, and restart PHP-FPM.


# Restart PHP-FPM to apply changes in php.ini
sudo systemctl restart php8.3-fpm

# Enable and start Zabbix Server
sudo systemctl enable zabbix-server
sudo systemctl start zabbix-server

# Enable and start Nginx
sudo systemctl enable nginx
sudo systemctl start nginx

# Check status of all services
sudo systemctl status zabbix-server
sudo systemctl status nginx
sudo systemctl status php8.3-fpm

Ensure that all services are in active (running) state.

3. Configuring TLS/HTTPS with Certbot (Let's Encrypt)

It is highly recommended to use HTTPS to access the Zabbix web interface. We will use Certbot to obtain free SSL/TLS certificates from Let's Encrypt.

Prerequisite: Your VPS must have a domain name pointing to its IP address. For example, zabbix.yourdomain.com.


# Install Certbot for Nginx
sudo apt install certbot python3-certbot-nginx -y

# Obtain and install SSL certificate
# Replace 'zabbix.yourdomain.com' with your domain name
sudo certbot --nginx -d zabbix.yourdomain.com

Certbot will ask a few questions: your email, agreement to the terms of service, and possibly offer to redirect HTTP traffic to HTTPS. It is recommended to choose automatic redirection (option 2).

Certbot will automatically modify the Nginx configuration and set up automatic certificate renewal.

4. Initial Zabbix Frontend Configuration via Web Interface

Open your browser and go to https://zabbix.yourdomain.com (or http://your_vps_ip if you haven't configured HTTPS yet). You will see the step-by-step Zabbix Frontend installation wizard.

  1. Welcome: Click "Next step".
  2. Check of pre-requisites: Ensure all items are marked green. If there are warnings, go back to configuring PHP (php.ini) and Nginx.
  3. Configure DB connection:
    • Database type: PostgreSQL
    • Database host: localhost
    • Database port: 5432
    • Database name: zabbix
    • User: zabbix
    • Password: your_db_password (the one you set)
    Click "Next step".
  4. Zabbix server details:
    • Host: localhost
    • Port: 10051
    • Zabbix server name: (optional, but useful, e.g., "Main Zabbix Server")
    Click "Next step".
  5. Pre-installation summary: Check all settings and click "Next step".
  6. Install: Installation is complete. Click "Finish".

Now you can log in to the Zabbix Frontend. Standard credentials:

  • Username: Admin
  • Password: zabbix

Be sure to change the default password immediately after the first login!

5. Verifying Functionality

After logging into the Zabbix web interface:

  • Go to "Administration" -> "Servers". Ensure your Zabbix Server is displayed as "Available" (green icon).
  • Go to "Monitoring" -> "Hosts". You should see the "Zabbix server" host with "Available" status.
  • Check Zabbix Server logs:
  • 
    sudo tail -f /var/log/zabbix/zabbix_server.log
    

    There should be no critical errors.

Your Zabbix Server is successfully installed and ready to use!

Backups and Maintenance

Diagram: Backups and Maintenance
Diagram: Backups and Maintenance

Regular backups and timely maintenance are key to the stable operation of Zabbix Server and the safety of your monitoring data.

1. What to Back Up

For a full recovery of Zabbix Server, the following components need to be backed up:

  • Zabbix Database: This is the most important component, containing all collected metrics, host configuration, templates, triggers, users, and history.
  • Zabbix Server Configuration Files: /etc/zabbix/zabbix_server.conf.
  • Zabbix Agent Configuration Files (if installed on the same server): /etc/zabbix/zabbix_agentd.conf and /etc/zabbix/zabbix_agentd.d/.
  • Web Server Configuration Files: For example, /etc/nginx/conf.d/zabbix.conf and /etc/nginx/sites-available/zabbix.yourdomain.com (if you are using Certbot).
  • PHP-FPM Configuration: /etc/php/8.3/fpm/php.ini.
  • SSL Certificates: Certbot usually stores them in /etc/letsencrypt/.

2. Simple Database Auto-Backup Script

Let's create a simple script for daily PostgreSQL database backups using pg_dump.


# Create backup directory (if it doesn't exist yet)
sudo mkdir -p /var/backups/zabbix_db

# Create backup script
sudo nano /usr/local/bin/backup_zabbix_db.sh

Insert the following content, replacing your_db_password with your Zabbix user password:


#!/bin/bash

# Database settings
DB_NAME="zabbix"
DB_USER="zabbix"
DB_PASS="your_db_password" # IMPORTANT: Storing the password in the script is not a best practice for production.
                          # For production, use a .pgpass file or environment variables.
                          # For this guide, we use a simple approach.
BACKUP_DIR="/var/backups/zabbix_db"
TIMESTAMP=$(date +%Y%m%d%H%M%S)
BACKUP_FILE="${BACKUP_DIR}/${DB_NAME}_${TIMESTAMP}.sql"

# Create backup
PGPASSWORD="${DB_PASS}" pg_dump -h localhost -U "${DB_USER}" "${DB_NAME}" > "${BACKUP_FILE}"

# Check backup success
if [ $? -eq 0 ]; then
    echo "Zabbix database backup created successfully: ${BACKUP_FILE}"
else
    echo "Error creating Zabbix database backup."
    exit 1
fi

# Delete old backups (e.g., older than 7 days)
find "${BACKUP_DIR}" -name "${DB_NAME}_*.sql" -mtime +7 -delete
echo "Old backups cleaned up."

exit 0

Save and close the file. Make the script executable:


sudo chmod +x /usr/local/bin/backup_zabbix_db.sh

3. Configuring Cron for Automatic Backups

Let's add a Cron job for daily execution of the backup script.


# Open crontab for the root user
sudo crontab -e

Add the following line to the end of the file so that the script runs every day at 03:00 AM:


0 3 * * * /usr/local/bin/backup_zabbix_db.sh >> /var/log/zabbix_db_backup.log 2>&1

Save and close the file.

4. Where to Store Backups

Storing backups on the same server as the original data is extremely risky. It is recommended to use external storage:

  • S3-compatible Cloud Storage: Use utilities like awscli, rclone, or s3cmd to automatically upload backups to an S3 bucket.
  • Separate VPS or NAS: Transfer backups via SSH using rsync to another server.
  • External Hard Drive: If it's a dedicated server and connection is possible.

The same rsync can be used to transfer configs and SSL certificates.


# Example rsync command to transfer backups to a remote server (replace with your data)
# rsync -avz /var/backups/zabbix_db/ youruser@your_remote_server:/path/to/remote/backups/

5. Updates: Rolling vs. Maintenance Window

Keeping Zabbix and the operating system up-to-date is critical for security and stability.

  • OS Updates: Regularly run sudo apt update && sudo apt upgrade -y. For minor updates, this can be done without stopping Zabbix. For major kernel updates or critical OS components, it is recommended to plan a "maintenance window" and restart the server.
  • Zabbix Updates: For minor Zabbix updates (e.g., from 7.0.0 to 7.0.1), it is usually sufficient to stop Zabbix Server, update the packages zabbix-server-pgsql zabbix-frontend-php zabbix-nginx-conf zabbix-agent, and start it again. Zabbix will automatically update the DB schema if necessary. For major updates (e.g., from 6.0 LTS to 7.0 LTS), more careful planning, documentation review, and testing on a separate test environment are required. Always perform a full backup before a major update.

Plan a maintenance window to minimize impact on monitoring, especially if you use Zabbix for critical systems.

Troubleshooting + FAQ

This section contains answers to frequently asked questions and solutions to common problems that may arise during the installation and operation of Zabbix Server.

What is the minimum VPS configuration suitable for Zabbix?

For a small environment (up to 50 hosts, several hundred metrics), a VPS with 2 vCPU, 4 GB RAM, and an 80 GB SSD disk will be minimally sufficient. However, if you plan to store data history for more than a month or monitor more objects, it is strongly recommended to increase RAM to 8 GB and disk space to 200 GB SSD. Using an SSD is critically important for Zabbix database performance.

What to choose — VPS or dedicated for this task?

For most beginner and medium-sized projects (up to 200-300 hosts), a VPS is the optimal choice due to its flexibility and cost. It allows for quick system deployment and resource scaling as needed. A dedicated server becomes advisable for very large monitoring scales (hundreds and thousands of hosts, millions of metrics), when maximum disk subsystem performance, guaranteed CPU/RAM resources, and complete physical isolation are required. A dedicated server may also be preferable for long-term storage of large volumes of historical data.

Zabbix Server is not starting, or there are "cannot connect to database" errors in the logs?

What to check:

  1. Make sure PostgreSQL is running: sudo systemctl status postgresql.
  2. Check the Zabbix Server configuration file: sudo nano /etc/zabbix/zabbix_server.conf. Ensure that the DBHost, DBName, DBUser, and DBPassword parameters are specified correctly and match the created database and user.
  3. Make sure the zabbix user in PostgreSQL has the correct password and permissions for the zabbix database. You can try connecting manually: sudo -u zabbix psql zabbix (will require a password).
  4. Check Zabbix Server logs: sudo tail -f /var/log/zabbix/zabbix_server.log for more detailed error information.

Zabbix web interface is inaccessible (502 Bad Gateway or 404 Not Found)?

What to check:

  1. Make sure Nginx is running: sudo systemctl status nginx.
  2. Make sure PHP-FPM is running: sudo systemctl status php8.3-fpm.
  3. Check the Nginx configuration file for Zabbix (e.g., /etc/nginx/conf.d/zabbix.conf). Ensure that root /usr/share/zabbix; is specified correctly and fastcgi_pass points to the correct PHP-FPM socket (unix:/run/php/php8.3-fpm.sock).
  4. Check Nginx logs: sudo tail -f /var/log/nginx/error.log.
  5. Make sure all necessary PHP packages are installed (e.g., php-pgsql, php-gd, php-xml).

Zabbix Agent on the Zabbix server is not sending data?

What to check:

  1. Make sure Zabbix Agent is running: sudo systemctl status zabbix-agent.
  2. Check the agent configuration file: sudo nano /etc/zabbix/zabbix_agentd.conf. Ensure that Server=127.0.0.1 or the IP address of your Zabbix Server, and Hostname matches the host name specified in the Zabbix web interface.
  3. Check that port 10050 is open in UFW on the server where the agent is running: sudo ufw status.
  4. Check the agent logs: sudo tail -f /var/log/zabbix/zabbix_agentd.log.

"PHP time zone not set" warning in the Zabbix web interface?

What to check:

This means that the time zone is not specified or is incorrectly specified in the php.ini file. Open sudo nano /etc/php/8.3/fpm/php.ini, find the line ;date.timezone = and uncomment it, specifying your time zone, for example: date.timezone = Europe/Moscow. After the change, restart PHP-FPM: sudo systemctl restart php8.3-fpm.

How to change the Admin password in Zabbix?

After logging into the Zabbix web interface, go to "Administration" -> "Users". Select the "Admin" user, and click on it. In the opened window, find the "Password" field and click "Change password". Enter a new strong password and confirm it. Then click "Update". This is a crucial step to ensure the security of your monitoring system.

Conclusions and Next Steps

Diagram: Conclusions and Next Steps
Diagram: Conclusions and Next Steps

Congratulations! You have successfully installed and configured Zabbix Server 7.0 LTS on your VPS, creating a powerful and flexible platform for monitoring your entire infrastructure. You now have full control over data collection, analysis, and an alert system, which will allow you to quickly respond to any issues and maintain a high level of availability for your services.

Further development of your monitoring system may include:

  1. Deploying Zabbix Agent on other servers: Install Zabbix Agent on all hosts you want to monitor and add them to Zabbix Server.
  2. Using Zabbix Proxy: For monitoring remote offices, cloud environments, or very large infrastructures, consider deploying Zabbix Proxy to reduce the load on the central server and decrease network traffic.
  3. Configuring Alerts: Integrate Zabbix with your notification system (email, Telegram, Slack, PagerDuty) to receive real-time alerts about problems.
  4. Creating Custom Templates and Scripts: Develop your own monitoring templates for specific applications or services, utilizing Zabbix's capabilities for extensible monitoring.
  5. Performance Optimization: As the number of monitored metrics grows, explore options for optimizing the PostgreSQL database, Zabbix Server settings, and scaling VPS resources.

Was this guide helpful?

Zabbix server installation on VPS: comprehensive monitoring and alerting
support_agent
Valebyte Support
Usually replies within minutes
Hi there!
Send us a message and we'll reply as soon as possible.