Rent a virtual linux server in Madrid

Currently, we do not offer a trial period.

We utilize a variety of CPU models, ranging from Intel Xeon E5-2680v2 to E5-2680v4. However, please note that we cannot guarantee or predict which specific processor will be assigned to the cluster node hosting your virtual machine.

The minimum payment period for our services is one month, ensuring flexibility and convenience for our customers.

The only way to change your default IP address is to order a new IP. It will cost you additional 3 €. Please note that IP addresses are assigned automatically it is impossible to choose a specific IP range.

“Unmetered bandwidth” indicates that there are no additional charges based on the amount of data transferred to and from your cloud server monthly. This feature enables worry-free data transfer without overage fees. Typically, personal or small business website operators do not exceed our fair usage policies. However, if you anticipate consistent, heavy bandwidth usage, our cloud servers may not be the ideal choice. In such cases, consider our dedicated servers with guaranteed channels . Note that excessive use on a cloud server can lead to bandwidth speed reduction as per our terms of service, ensuring fair usage for all clients.

Bandwidth Limits for Cloud Linux Server Solutions:

In Fujairah and Mumbai:
• 2TB/month for KVM-1-FJR, KVM-1-BOM, WIN-2-FJR, WIN-2-BOM plans.
• 4TB/month for KVM-2-FJR, KVM-2-BOM, WIN-4-FJR, WIN-4-BOM plans.
• 5TB/month for higher-tier plans.

In Lagos:
• 1TB/month for KVM-1-AF, WIN-2-AF plans.
• 2TB/month for KVM-2-AF, WIN-4-AF plans.
• 3TB/month for KVM-4-AF, WIN-6-AF plans.
• 4TB/month for KVM-6-AF, WIN-8-AF plans.
• 5TB/month for KVM-8-AF, WIN-10-AF plans.

Upon exceeding these limits, bandwidth is reduced to 10Mbit/s. For all other plans, bandwidth is up to 1Gbit/s, reduced to 100 Mbit/s if the 5TB monthly quota is exceeded.

Please open a support ticket and ask to upload own ISO image. After that the feature will be allowed.

We offer a wide range of Linux and Unix-like operating systems. If you require a Windows-based operating system, please select one of our WIN plans specifically designed for Windows environments.

Mail ports are filtered. You should contact our support if you need to open mail ports. Additional account verification may be required.

1. Login to Your Client Area and head to the Services list.
2. Select your Private Network from your service list.
3. Select the VPS from the available pool you would like to add a private network for.
4. Click on Save Changes

It will take a couple of minutes for the changes to be propagated to your vMesh network to be in Status Active / Ready.

You will find below the steps required to configure your Private Network for Linux Distribution (Netplan & Interface file). You would simply need to replicate the following setup for all the VPS defined in your network. Each VPS would need their own Private Network IP Address (e.g., 10.0.0.2, 10.0.0.3, 10.0.0.4).

Ubuntu 20.04 / 22.04 / 24.04 and Debian 11 / 12

1. Identify Your Network Interface & Naming Scheme:

ip addr

2. Edit Netplan Configuration:

sudo nano /etc/netplan/01-netcfg.yaml

3. Add the Following Configuration:

network:
  version: 2
  renderer: networkd
  ethernets:
    eth1:
      dhcp4: no
      addresses:
        - YourAssignedIP/24 # (e.g., 10.0.0.2)

4. Apply the Configuration:

sudo netplan apply

Debian Older Versions (Using /etc/network/interfaces)

1. Edit the Interfaces File:

sudo nano /etc/network/interfaces

2. Add the Following Lines:

auto eth1
iface eth1 inet static
  address YourAssignedIP # (e.g., 10.0.0.2)
  netmask 255.255.255.0

3. Restart Networking Service:

sudo systemctl restart networking

CentOS 9 Stream / AlmaLinux 8 & 9 / Rocky Linux 8.6 & 9.x

1. Navigate to Network Scripts Directory:

cd /etc/sysconfig/network-scripts/

2. Create or Edit the Interface Configuration File:

sudo nano ifcfg-eth1

3. Add the Following Configuration:

DEVICE=eth1
BOOTPROTO=none
ONBOOT=yes
IPADDR=YourAssignedIP # (e.g., 10.0.0.2)
NETMASK=255.255.255.0

4. Restart Network Service:

sudo systemctl restart NetworkManager