For stable Hytale server performance, high CPU clock speed is especially important, as the game relies heavily on single-core and high-frequency CPU performance. For this reason, we recommend servers with high per-core frequency rather than simply a large number of cores.

Recommended Servers

Recommended configuration for most Hytale servers

For the majority of Hytale game servers, the following configuration is a solid choice:

• AMD Ryzen 5 3600
• 6 cores / 3.6 GHz
• 64 GB DDR4
• 2 × 512 GB NVMe (configurable)
• 1 Gbps, unlimited traffic

Server link:
https://dashboard.unihost.com/cart.php?a=add&pid=974

Servers with DDoS protection

If DDoS protection is critical (for example, for a public server), we recommend considering a more powerful solution:

• AMD Ryzen 7 9800X3D
• 8 cores / 4.7 GHz
• 64 GB DDR5 ECC
• 2 × 960 GB NVMe
• 1 Gbps, unlimited traffic

Server link:
https://dashboard.unihost.com/cart.php?a=add&pid=998

VPS option for small groups

If you plan to play with a small group of players, a VPS can also be a suitable option.

Recommended VPS configuration:

• 6 vCPU (Intel)
• 12 GB RAM
• 100 GB NVMe
• 1 Gbps, unlimited traffic

VPS link:
https://dashboard.unihost.com/cart.php?a=add&pid=2124

Installing the Hytale Server on Windows Server 2022

We start by downloading the official Hytale server files.

Open the official Hytale Server documentation page:
https://support.hytale.com/hc/en-us/articles/45326769420827-Hytale-Server-Manual

This page contains all the required tools to run a Hytale server.
Download the latest server files and prepare them for installation.

After downloading the hytale-downloader.zip archive, extract it to a convenient directory.
Inside the archive, you will find several files, including downloader versions for Windows and Linux.

For Windows, use the following file:

hytale-downloader-windows-amd64.exe 

Run it from the command prompt. The downloader will automatically fetch the latest Hytale server version and verify the integrity of the downloaded files.

After the download is complete, an archive containing the server files will appear in the directory (for example, 2026.01.15-c04fdfe10.zip).

Extract this archive into a separate directory — this will be the server’s working directory.

Installing Java 25

The Hytale server requires Java 25 (LTS) to run.

Visit the official Adoptium website:
https://adoptium.net/temurin/releases

Select JDK 25 (LTS) and download the Windows (x64) installer.

After the download is complete, run the installer and follow the standard installation steps.

To verify that Java is installed correctly, open Command Prompt (CMD) and run:

java -version

If OpenJDK 25 is shown in the output, Java has been installed successfully and you can proceed with launching the server.

First Launch of the Hytale Server

For the next steps, we will use Command Prompt (CMD).

Navigate to the directory containing the Hytale server files. In our example, the server files are located in the Server directory.

To start the server, run the following command:

java -jar HytaleServer.jar --assets ..\Assets.zip

During the first launch, the server will begin initializing and loading all required components. You will see various log messages in the console — this is expected behavior.

Server Authentication (OAuth)

After the first launch, the server will require authentication and display a message indicating that login is required.

In the server console, run the following command:

/auth login device

The server will generate an authentication URL. Open this link in your browser, sign in to your Hytale account, and approve the access request.

Once authentication is completed successfully, the server will be properly linked to your Hytale account.

Persisting Authentication Data

To avoid re-authenticating the server after every restart, you need to persist the authentication credentials.

Run the following command in the server console:

/auth persistence Encrypted

This method stores authentication tokens in an encrypted format and is recommended for long-term server operation.

After this step, the server is ready for further configuration and for players to connect.

Opening Port 5520 (Windows Server)

To allow players to connect, you need to open the server port 5520 (UDP).

Open PowerShell as an administrator and run the following command:

New-NetFirewallRule -DisplayName "Hytale Server UDP 5520" -Direction Inbound -Protocol UDP -LocalPort 5520 -Action Allow

After executing this command, a new firewall rule will be added and the server will be accessible from external connections.

You can now connect to the server using Direct Connect, specifying your server’s IP address and port 5520.

Installing AdminUI

To simplify server management, you can install the AdminUI mod.

Download the mod from the following link:
https://www.curseforge.com/hytale/mods/adminui

After downloading the mod, place the .jar file into the following directory:

mods

Next, start the server and assign yourself as an operator.

Connect to the server using the game launcher. Once connected, return to the server terminal and run the following command:

/op add <username>

where <username> is your in-game account name.

After executing the command, you will receive an in-game notification confirming that operator privileges have been granted.

To access the administrator tools, enter the following command in the in-game chat:

/admin

The AdminUI panel will then open, giving you access to server administration features.

Installing the Hytale Server on Linux

Creating a Dedicated Server User (Recommended)

For security reasons, it is not recommended to run the Hytale server as the root user.
Best practice is to run the server under a dedicated system user.

Create a new user, for example hytale:

adduser hytale

Add the user to the sudo group if required:

usermod -aG sudo hytale

Switch to the newly created user:

su - hytale

All further server files and the Hytale server itself should be managed and launched under this user.

Installing Java 25 on Linux

The Hytale server on Linux requires Java 25 (Temurin).

Visit the Adoptium download page:
https://adoptium.net/temurin/releases

Select the following options:

• Operating System: Linux
• Version: JDK 25 (LTS)
• Package type: .tar.gz

Download the archive to continue with the installation.

After downloading the archive, you will have a file similar to:

OpenJDK25U-jdk_x64_linux_hotspot_25.0.1_8.tar.gz

Extract the archive using the following command:

tar -xvzf OpenJDK25U-jdk_x64_linux_hotspot_25.0.1_8.tar.gz

By convention, Java is usually installed in /opt or /usr/lib/jvm.
In this example, we will use /opt:

sudo mkdir -p /opt/java
sudo mv jdk-25.0.1+8 /opt/java/

Configuring JAVA_HOME and PATH (User Level)

Open the user profile file:

nano ~/.profile

Add the following lines to the end of the file:

export JAVA_HOME=/opt/java/jdk-25.0.1+8
export PATH="$JAVA_HOME/bin:$PATH"

Apply the changes:

source ~/.profile

Verify the Java installation:

java -version

If the Java version is displayed correctly, the setup is complete.

Downloading the Hytale Server (Linux)

After installing Java, proceed to download the Hytale server files.

Download the server downloader archive from the official documentation page:
https://support.hytale.com/hc/en-us/articles/45326769420827-Hytale-Server-Manual

After the download is complete, you will have the following file:

hytale-downloader.zip

Extract the archive using the command:

unzip hytale-downloader.zip

Downloading the Server Files

Inside the extracted directory, you will find several files.

For Linux, use the following downloader:

hytale-downloader-linux-amd64

Run it with:

./hytale-downloader-linux-amd64

The downloader will automatically fetch the latest Hytale server version.

The downloader will automatically fetch the latest version of the Hytale server.

After the download is complete, an archive similar to the following will appear:

2026.01.15-c04fdfe10.zip

It is recommended to extract the server files into a separate directory:

mkdir /Hytale
mv 2026.01.15-c04fdfe10.zip /Hytale
cd /Hytale
unzip 2026.01.15-c04fdfe10.zip

Opening the Server Port (Ubuntu / Debian)

To allow players to connect, you must open port 5520 (UDP).

Run the following commands:

sudo ufw allow 5520/udp
sudo ufw reload

First Server Launch

Navigate to the server directory and start the server using the following commands:

cd Server
java -jar HytaleServer.jar --assets ../Assets.zip

During the first launch, the server will request authentication — this is expected behavior.

Server Authentication

In the server console, run:

/auth login device

Open the URL displayed in the console, sign in to your Hytale account, and approve the access request.

Persisting Authentication

After successful authentication, it is recommended to persist the credentials so you don’t have to log in again after every server restart.

Use the encrypted credential store:

/auth persistence Encrypted

If needed, you can choose a different persistence method.

Connecting to the Server

Once the setup is complete, the server is ready to use.

To connect, use Direct Connect in the Hytale client and enter your server’s IP address.

Installing Mods (Optional)

If you want to install mods:

1. Download the desired mod (for example, AdminUI) from CurseForge
2. Navigate to the Server directory of your Hytale server
3. Place the mod .jar file into the mods directory
4. Restart the server

After the restart, the mod will be loaded automatically.

The post Installing a Hytale server on Unihost (Windows and Linux) with the AdminUI plugin appeared first on Unihost.FAQ.

The installation process is based on the official documentation: Self-Hosting with Docker.
Docker was already pre-installed on our VPS, so the installation step is omitted in this guide. When placing your order, you can also choose an operating system image with Docker pre-installed — simply select the desired OS in the configurator.

Now let’s proceed with installing Supabase.

Once you have received the credentials to access your server, connect to it via SSH using the following command:

ssh root@SERVER_IP

After connecting to the VPS, make sure to update the system by running:

apt update && apt upgrade -y

Next, follow the steps from the official Docker-based installation guide:

Clone the Supabase repository:

git clone --depth 1 https://github.com/supabase/supabase

Create a directory for the project:

mkdir supabase-project

Resulting directory structure should look like this:

├── supabase

└── supabase-project

Copy the necessary Docker files:

cp -rf supabase/docker/* supabase-project

Copy the sample environment variables file:

cp supabase/docker/.env.example supabase-project/.env

Navigate to the project directory:

cd supabase-project

At this stage, you need to change the default Supabase password to your own. To do this, edit the .env file:

nano .env

In the opened .env file, find the following line:

DASHBOARD_PASSWORD=...

Replace the default password with your own, save the changes, and close the editor.

After that, continue with the installation:

Pull the Docker images:

docker compose pull

Start Supabase in detached mode:

docker compose up -d

Wait until all Supabase services are fully up and running. Then, open your browser and go to:

http://SERVER_IP:8000

Enter the username and password you specified in .env — you will then be taken to the Supabase dashboard.

The post Installing Supabase on a VPS from Unihost appeared first on Unihost.FAQ.

When you access the service control panel, you will see the familiar Start, Stop, and Reboot buttons — they allow you to quickly power on, shut down, or reboot your VPS.

If you encounter network connection issues or suspect that the VPS is not accessible through standard methods, use the Console feature. It allows you to connect directly to the server, bypassing network settings.

You can also reinstall the OS on your VPS — simply select the corresponding button and follow the on-screen prompts.

To view your IP addresses and update RDNS records, go to the IP addresses section.

Now you know how to manage your UNE VPS in the Unihost panel: monitor the server status, track traffic, reset the password, access the console, and reinstall the system.

If you have any questions or encounter any issues, the Unihost support team is always ready to help — just create a ticket through your client area.

The post Managing a UNE VPS through the Unihost Client Area appeared first on Unihost.FAQ.

When you access the VPS control panel, you’ll get convenient tools for managing your server — from basic actions like powering it on and off to rebooting and resetting the password.

To reset the password, click the corresponding button in the control panel. After the reset is complete, the new password will be available in the Server Information section under Password.

If you’re experiencing network connection issues or suspect that the VPS is not accessible through standard methods, use the Console feature. It allows you to connect directly to the server, bypassing any network configuration.

To reinstall the operating system, use the Rebuild section — simply select the desired OS, and the system will automatically perform the installation. The new password will be provided immediately after the OS installation process begins.

You can also boot the server from an ISO image. The ISO images section contains ready-to-use images of various operating systems — simply attach the required ISO and start the installation.
If you want to install Windows, follow our dedicated guide.

You can configure the reverse DNS zone (rDNS) in the Reverse DNS section of the control panel.

To access Rescue Mode, click the corresponding button in your VPS control panel. After that, enter your SSH key in the field that appears — it will be required to connect to the server in recovery mode.
Once the mode is activated, you can connect to the VPS using this key via SSH or through Console Access in the control panel.

Now you know how to manage your UNH VPS in the Unihost panel: monitor the server status, track traffic, reset the password, access the console, and reinstall the system.

If you have any questions or encounter any issues, the Unihost support team is always ready to help — simply create a ticket through your client area.

The post Managing a UNH VPS through the Unihost Client Area appeared first on Unihost.FAQ.

When you access the service control panel, you will see the familiar Start, Stop, and Reboot buttons — they allow you to quickly power on, shut down, or reboot your VPS.

To check the traffic used by your service, go to the Network section.

The Traffic Usage section on the service page displays the current traffic consumption, making it convenient for monitoring.

To reset the password, use the Reset Password function and follow the instructions in the pop-up windows. After the reset is complete, the new password can be found in the Credentials section.

To access your VPS, you can use Console Access — this allows you to connect to the server even if network access is unavailable.

All connection details for your VPS are available in the Credentials section.

Through the control panel, you can also reinstall the operating system. To do this, select the Reinstall button, choose the desired OS, and click Reinstall OS.

After the installation is complete, the login credentials will be available in the Credentials section.

To boot your VPS into rescue mode, select the corresponding button in the control panel and follow the instructions. Then use Console Access to connect to the VPS in Rescue Mode.

Now you know how to manage your LVP VPS in the Unihost panel: monitor the server status, track traffic, reset the password, access the console, and reinstall the system.
If you have any questions or encounter any issues, the Unihost support team is always ready to assist — simply create a ticket through your client area.

The post Managing an LVP VPS through the Unihost Client Area appeared first on Unihost.FAQ.

In this article, we will explore how to organize backups on Unihost servers — from simple bash scripts to integration with control panels and container-based solutions.

1. Script-based approach: requires basic command-line knowledge

For those who prefer flexibility and full control over the process, it is possible to set up backups using a bash script.

This method does not require a control panel — you just need to create a script that will archive files, databases, and automatically remove old backups.

You can learn more about configuration and find a ready-to-use script example in a separate article:

Simple backup script (bash)

This option is suitable for administrators who want a reliable and simple solution without third-party tools.

2. Portainer and container backups

For projects running in a Docker environment, there is a ready-to-use solution based on Portainer — it allows you to manage backups of containers and their data in just a few clicks.

You can learn more about the configuration in the following article:

Installing Duplicati with Portainer

The solution is based on integration with Duplicati, which provides the ability to:

• perform automated backups of Docker volumes and configurations;

• store backups in S3-compatible cloud storage or on a local server;

• configure encryption and scheduling through a convenient web interface.

This approach is ideal for users whose infrastructure is based on containers and who require centralized and reliable backup management.

3. Control panels: a convenient interface for administration

If you use a server control panel, you can set up automated backups directly through its interface.

Plesk

Plesk provides a powerful built-in backup system:

• supports incremental backups (only changes are saved);

• allows storing backups in Amazon S3, Google Cloud, or an FTP storage;

• offers automated restoration of individual websites, mailboxes, or databases.

cPanel

In cPanel, the backup system is available out of the box. You can configure:

• daily or weekly backups;

• selective restoration directly from the panel;

• uploading copies to a remote server via SCP or Amazon S3.

Free alternative

For small projects or testing environments, HestiaCP is a great lightweight and free control panel with a basic backup system. It allows you to:

• perform automatic backups of websites and databases;

• configure a schedule and storage location;

• restore required components in just a couple of clicks via the panel.

4. Backup best practices

To ensure that backups actually help you in a critical situation, follow these basic principles:

• The 3-2-1 rule: keep 3 copies of your data, stored on 2 different media types, with 1 copy stored offsite.

• Test restoration: a backup without recovery testing is just a copy of unknown state.

• Encrypt and secure access: especially important when using cloud storage.

• Automate: use cron, systemd timers, or built-in schedulers in control panels.

5. Conclusion

The choice of a backup approach depends on your tasks, scale, and the level of control you want to maintain.

• For standalone solutions, a classic bash script is a great option — it is simple, reliable, and does not require additional tools.
• For containerized environments, the combination of Portainer + Duplicati is the optimal choice, providing automation and centralized management of backup data.
• For servers with control panels, it’s more convenient to use built-in tools in Plesk, cPanel, or HestiaCP, where everything is handled through the interface without manual configuration.

The most important thing is not to postpone setting up backups “for later.” Even the simplest solution launched today may one day save your project from downtime and data loss.
Regular backups, recovery testing, and a properly organized backup strategy are not a luxury, but the foundation of a stable and secure infrastructure.

The post Reliable Backup: Overview of Solutions and a Practical Approach appeared first on Unihost.FAQ.

Requirements:

• A VPS with Portainer installed using the Unihost script;
  
• A deployed NPM (Nginx Proxy Manager).

After installing Portainer, log in using your credentials.

As soon as you log in to Portainer, go to the local section and select the Odoo template.

Fill in all the required fields. Note: for security reasons, the password must be strong — use uppercase and lowercase letters, numbers, and special characters to minimize the risk of unauthorized access.

After that, a new stack odoo-app will appear in the Stacks section. Inside this stack, the containers required for its operation will be deployed.

To access Odoo, you need to configure proxying through Nginx Proxy Manager (NPM). For proper operation, you can use your own domain — add it to NPM and point it to your server’s IP address via DNS by creating an A record.
You can also use a local domain by adding it to the hosts file and configuring NPM as shown in the screenshot.

You can now use the specified domain, enter the administrator credentials (default credentials: user – admin, password – admin), and access the Odoo interface.

We now have access to all the features of the ERP and CRM systems.

Conclusion
Using the ready-made Odoo template in Portainer allows you to quickly deploy a full-featured business platform without complex manual configuration. Combined with Nginx Proxy Manager (NPM), you get convenient domain access and automatic SSL. As a result, you have a ready-to-use “out-of-the-box” ERP system that saves time and simplifies company management.

The post Installing Odoo with Portainer appeared first on Unihost.FAQ.

To create a project in GitLab:
Go to “New Project” > “Create blank Project.”

Fill in all the required information to create your new project.

Once the repository is created, you need to create a test branch to add the WordPress files.

Click the + icon and select “New Branch.”

Name the branch wp-test (as an example — you can choose any name) and click “Create branch.”

After that, switch to this branch:

Go to your test branch and add the file
.gitlab-ci.yml

Then create a Docker/ directory and add the following files inside it:
wp-traefik.prod.yml and .env

Example:
.gitlab-ci.yml

Example: wp-traefik.prod.yml

Example: .env

Now go to your production server to create a GitLab Runner, which will be used to upload your code to the target server.
On the production server, add the Docker image for the GitLab Runner:

docker run -d --name gitlab-runner --restart always \

  -v /var/run/docker.sock:/var/run/docker.sock \

  -v /gitlab-runner/config:/etc/gitlab-runner \

  gitlab/gitlab-runner:latest

Also, create a network on the production server:
docker network create web

To register the GitLab Runner, you need to obtain a token.
To do this, go to the following path:
GitLab → Settings > CI/CD > Runners > Create project runner

After that, start the registration of the GitLab Runner.

docker exec -it gitlab-runner gitlab-runner register

Enter the following information:

URL: https://gitlab.example.net
Token: <token> obtained from GitLab
Description: prod-runner
Executor: docker
Default image: php:8.2-apache

Verify the registration by running:

docker exec -it gitlab-runner gitlab-runner verify

The output should be:

Verifying runner… is valid

Once our runner has passed validation and successfully connected to GitLab, proceed to merge the test branch with main — click “Create merge request.”

After that, the tests and code deployment to the production server will start. Once the process is complete, you’ll have a fully functional WordPress website.

Conclusion

By following all the steps, you have set up a fully functional CI/CD pipeline in GitLab for your project.
The created pipeline automatically builds and deploys the application with every change in the repository, while the GitLab Runner executes tasks without manual intervention.
This approach speeds up development, reduces the risk of errors, and ensures stable code deployment to the server.
You can now expand your pipeline configuration by adding testing, security checks, or automatic Docker container updates — depending on your project’s needs.

The post Setting up a basic project deployment (CI/CD) appeared first on Unihost.FAQ.

1. Starting a local Docker Registry

Docker provides an official registry image for creating a local registry.

docker run -d -p 5000:5000 --name registry registry:2

• -d — runs the container in detached mode (in the background).
• -p 5000:5000 — maps port 5000 (the default port for the registry).
• –name registry — sets the container name.
• registry:2 — the official Docker Registry image.

Now the local registry is available at localhost:5000.

2. Configuring storage

By default, images are stored in the container’s memory. To enable persistent storage, add a volume:

docker run -d -p 5000:5000 --name registry -v registry-data:/var/lib/registry registry:2

-v registry-data:/var/lib/registry — Mounts the registry-data volume to store images.

3. Working with the local registry

Tagging an image:

1. To push an image to the local registry, you need to tag it with the prefix localhost:5000/.

   docker tag my-image:latest localhost:5000/my-image:latest

2. Pushing an image to the registry:

   docker push localhost:5000/my-image:latest
   

3. Pulling an image from the registry:

   docker pull localhost:5000/my-image:latest

4. Configuring Docker to work with a local registry

If you’re using HTTPS or working on a remote machine, make sure Docker is configured to work with insecure registries. Add the following to the /etc/docker/daemon.json file:

{

  "insecure-registries": ["localhost:5000"]

}

Restart Docker:

sudo systemctl restart docker

5. Additional settings (optional)

Authentication: To secure the registry, set up HTTP authentication using htpasswd:

docker run -d -p 5000:5000 --name registry \
  -v $(pwd)/auth:/auth \
  -e "REGISTRY_AUTH=htpasswd" \
  -e "REGISTRY_AUTH_HTPASSWD_PATH=/auth/htpasswd" \
  -e "REGISTRY_AUTH_HTPASSWD_REALM=Registry Realm" registry:2

Create an htpasswd file using the following command:

htpasswd -Bc auth/htpasswd <username>

TLS: For a production environment, configure TLS certificates to ensure a secure connection.

6. Checking the contents of the registry

To view the available images, use the registry API:

curl http://localhost:5000/v2/_catalog

Conclusion

Dependence on cloud registries and public Docker images can become a weak point for your service. However, proper strategies — such as using a local registry, caching, custom images, and redundancy — help minimize risks. Setting up a local mirror and using private registries give you control over your infrastructure, while monitoring and automation ensure stability. These measures help prevent service interruptions even in case of issues with external resources.

The post Docker Registry appeared first on Unihost.FAQ.

Requirements:

• A VPS with Portainer installed using the Unihost script

• A deployed NPM (Nginx Proxy Manager)

After connecting to Portainer, go to the Application section, select OpenProject, and fill in the required fields.

Go to NPM and create a proxy for your OpenProject.

If you have your own domain, add it to NPM and create an A record pointing to your server’s IP address.

For testing purposes, you can use a temporary domain by adding it to the hosts file in advance.

Example:

<server_ip>   myopenproject.com

Go to the specified domain and log in to OpenProject using the administrator account:

Username: admin
Password: admin

After the mandatory password change, the system will be ready for use — you can start working with OpenProject.

Note: For security reasons, your new password should be strong — use uppercase and lowercase letters, numbers, and special characters to minimize the risk of unauthorized access.

You can now create your first project.
To do this, go to the Projects section and click + Project.

After filling in all the required fields, click Save — your project will appear in the list of active ones.

Conclusion

Using a ready-made OpenProject template in Portainer allows you to deploy a full-featured project management system without complex manual configuration. Combined with Nginx Proxy Manager (NPM), you get convenient domain access and the ability to issue SSL certificates, while OpenProject’s built-in tools provide task planning, deadline tracking, and team collaboration. As a result, you get an out-of-the-box solution that saves time and simplifies the launch of your own project management workspace.

The post Installing OpenProject with Portainer appeared first on Unihost.FAQ.