If you have multiple servers at Tilaa, you can interconnect them using a Private Virtual Network (VLAN). Traffic on this interface is isolated, secure, and does not count towards your public data traffic limits.
Step 1: Create the Network in the Dashboard
- Log in to the MyTilaa Dashboard.
- Navigate to Virtual Networks and click Add.
- Give the network a name (e.g., "Database-Link").
- Go to your VPS Details page -> Network Interfaces.
- Click Add interface and select the network you just created.
Adding a network interface is a hardware change. You must reboot the VPS via the Tilaa Dashboard (not just inside the OS) for the new network card to be detected.
Step 2: Configure the IP Address (Linux)
Unlike the public interface, private networks do not have DHCP. You must manually configure a static IP from a private range (e.g., 10.0.0.x or 192.168.0.x).
First, identify the new interface name:
ip link show
Look for the interface that is currently "DOWN" or unconfigured (often eth1, ens4, or similar).
Option A: Ubuntu 18.04+ / Debian 11+ (Netplan)
Modern Ubuntu uses Netplan YAML configuration.
- Edit the config file in
/etc/netplan/(e.g.,50-cloud-init.yaml). - Add the second interface configuration:
network:
version: 2
ethernets:
eth0:
dhcp4: true
eth1: # Verify your interface name!
dhcp4: no
addresses:
- 10.0.0.1/24
Note: Use spaces for indentation, not tabs!
3. Apply changes: sudo netplan apply
Option B: CentOS / AlmaLinux / Rocky Linux
- Create a new file:
/etc/sysconfig/network-scripts/ifcfg-eth1(replace eth1 with your interface name). - Add the following content:
DEVICE=eth1
BOOTPROTO=none
ONBOOT=yes
IPADDR=10.0.0.1
NETMASK=255.255.255.0
3. Restart network: systemctl restart network (or nmcli networking off && nmcli networking on).
Step 3: Configure the IP Address (Windows)
1. Press Win+R and type ncpa.cpl to open Network Connections.
2. You will see a new "Ethernet" adapter. Right-click it and select Properties.
3. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
4. Fill in the IP details:
-
IP address:
10.0.0.1(Use unique IPs for each server!) -
Subnet mask:
255.255.255.0
Leave the Default Gateway field EMPTY.
If you enter a gateway on the private interface, Windows will get confused about how to reach the internet, and you will lose connection to your server.
Step 4: Testing
Once configured on both servers (e.g., Server A = 10.0.0.1, Server B = 10.0.0.2), try to ping each other:
ping 10.0.0.2
If ping fails, check your internal Firewall (UFW/Windows Firewall) to ensure it allows traffic from the private subnet.