Private Network Between Your VPS
Connect your CR Servers VPS over a private 1 Gbps network, isolated from other clients, with one charge per network, billed with your VPS.
The private network connects your VPS to each other through a second network card, separate from your public connection. Use it for your application to talk to its database, for replication or for backups between servers, without going over the internet or using your public connection.
What's Included
- One network per account, one charge. It's billed on one of your VPS and we connect your other VPS at no extra cost.
- Isolated from other clients. Only your VPS see the network.
- Up to 1 Gbps per VPS on the private card. Your public connection doesn't change.
- Added without restarting your servers.
- Fixed addresses in your own
10.240.N.0/24segment (we tell you which). No gateway, no DNS and no internet access through it. MTU 1500.
The private network is available between VPS on the same account.
Order the Private Network
Message us on WhatsApp, call us or open a ticket with your VPS hostnames. We add the private network to one of your VPS and send you the invoice.
- Price: $10 a month per network. Quarterly, semi-annual or annual billing gets the same discount as your VPS: $28.50 a quarter, $54 every six months or $96 a year. Prices exclude tax; if VAT (13%) applies to your account, the invoice shows it.
- Billed with your VPS. The private network uses the same billing cycle as that VPS (monthly, quarterly, semi-annual or annual) and renews on the same day.
- The first invoice is prorated: you only pay for the days left until your VPS's next renewal. From then on it renews together with it.
- Order it only once, even with several VPS: it covers every VPS on your account.
What Happens Next
- Once the invoice is paid, we follow up in the ticket to confirm which VPS to connect (by default, all active ones) and a time that suits you. Nothing restarts.
- We add the private card to each VPS. Inside the server it shows up as a new interface, usually
ens19on Ubuntu. - We send you each VPS's private address. You apply the setting inside the server or, if you authorize it in the ticket, we set it up for you.
Set the Address Inside the VPS
Use the address and MAC we send you. In the examples, replace bc:24:11:xx:xx:xx and 10.240.N.11 with your values.
Ubuntu (and other systems with netplan). Create the file /etc/netplan/60-crs-private.yaml:
network:
version: 2
ethernets:
crs-private:
match:
macaddress: 'bc:24:11:xx:xx:xx'
set-name: ens19
addresses: [10.240.N.11/24]
mtu: 1500
dhcp4: false
dhcp6: false
accept-ra: false
Then:
sudo chmod 600 /etc/netplan/60-crs-private.yaml
sudo netplan try
netplan try applies the change and reverts it unless you confirm with Enter. It only touches the new card: your public connection stays as it is. Keep this in its own file and don't edit 50-cloud-init.yaml.
Rocky Linux, AlmaLinux or Fedora (NetworkManager):
IFACE=$(ip -br link | awk -v mac='bc:24:11:xx:xx:xx' 'tolower($3)==tolower(mac){print $1}')
sudo nmcli con add type ethernet con-name crs-private ifname "$IFACE" \
ipv4.method manual ipv4.addresses 10.240.N.11/24 ipv4.never-default yes \
ipv6.method disabled 802-3-ethernet.mtu 1500
sudo nmcli con up crs-private
Test the connection from one VPS to another:
ping -c3 10.240.N.12
If you run a system firewall (ufw, firewalld), allow traffic on the private interface or from your 10.240.N.0/24 segment for the services you need.
Add or Remove a VPS
- New VPS on the network: open a ticket with its hostname. We assign the next address. No extra charge.
- Take a VPS off the network: delete the file (
sudo rm /etc/netplan/60-crs-private.yaml && sudo netplan apply, orsudo nmcli con delete crs-private) and let us know so we remove the card. - Cancelling the VPS that carries the network charge: if your other VPS still use the private network, tell us first. We move the charge to another of your VPS so the network keeps running.
Before a Reinstall or IP Change
If you plan to use Rebuild or need to change the public IP of a VPS on the private network, write to us first. We check that the private card stays in place. After a reinstall, create the configuration file again. Resetting the root password, rebooting, and powering off and on don't affect the private network. Neither does restoring a backup, unless the backup is from before the private network was connected: then write to us and we add the card back.
Security
The network is isolated from other clients, but traffic inside it isn't encrypted. For sensitive data, keep using encrypted connections (TLS, SSH or WireGuard), as on any network.
Need Help?
Message us on WhatsApp, call us or open a ticket with your VPS hostnames.
On this page