Manual to using Private networks for VPS

Private networks are a feature that allows you to connect multiple VPS servers in a single private network within one data center.
All traffic between the servers travels over a secure internal channel and does not go through the public internet.

This solution is ideal for tasks requiring high security and fast data exchange, such as:

• Building server clusters (e.g., for load balancing or high-availability systems).
• Database replication.
• Internal communication between backend, frontend, and other application components.
• Backup or data synchronization between servers.

Advantages of private networks

• Security: traffic stays within the data center, minimizing the risk of interception. No need for VPN or additional encryption for internal connections.
• Speed: internal channels provide low latency (usually <1 ms) and high bandwidth, depending on the configuration.
• Simplicity: setup is done directly in the Fornex dashboard at no extra cost. You can add any number of VPS servers to a single network.
• Optimization: reduces public traffic usage, which is beneficial for plans with traffic limits.

Private network VPS structure

How private networks work in Fornex

1. Activation in the dashboard: go to VPS → Local networks, create a new network, and add the required VPS (all must be in the same location).
2. Configuration on the servers: manually assign private IP addresses using OS configuration files or tools.
3. Data exchange after setup: once configured, servers can communicate with each other using their private IPs. All external (internet) traffic continues to use the primary public interface.

Why a private network might be unavailable and what to do

In rare cases, the feature may not be displayed or may not work due to technical reasons:

• Server location: Private networks are only supported in the locations DE-FC, NL-EF, SE-GS, and RU-3D.
  Solution: order a new VPS in one of these locations — the feature will be available automatically.

• Hypervisor type: Some hypervisors do not technically support private networks.
  Solution: create a ticket with technical support and request to migrate the server to a compatible hypervisor.

Configure the private network for different OS

After activating the network in the dashboard, proceed to configure the interface on your servers.
Choose the guide for your OS:

• Setup on Ubuntu 22.04/24.04.
• Setup on Debian 11/12/13.
• Setup on CentOS 8/9, AlmaLinux, Rocky Linux.