How networking works on Cloud VMs

Private addresses, the shared public address, your port range, and what a VM can and can't reach.

Updated 6 November 2026

A VM has no public address of its own. It sits on a private network, and the internet reaches it through ports you open on an address it shares with everyone else on Cloud. Once that makes sense, most connection problems explain themselves.

The path traffic takes

The Ports tab draws this for each port you've opened:

Step Example What it does
Public address and port 203.0.113.10:40001 The address everyone shares, and a port that's yours
Firewall Your VM's rules Decides whether the traffic is allowed in
Your VM 10.250.7.2:40001 Your system answers, if something is listening

Those addresses are examples. Yours are on the panel, and on the Cloud page under Your public address and Your ports.

Your project's private network

Every project gets its own network, a block of 256 addresses (a /24).

  • The gateway is the address ending in .1.
  • Your VMs get addresses from .2 to .254. A VM keeps its address when you restart it, reinstall it or restore a backup.
  • VMs in the same project reach each other directly on their private addresses, subject to each VM's firewall.

The address is set for you when the VM is built, so you don't need to configure anything. If you change it inside the system, your port forwards will still point at the old one and the VM will drop off the internet.

The project's Addresses tab shows what's in use. Networking across your projects on the main Cloud page shows your ports, addresses and firewalls all in one place.

Your ports

The public address is shared, so ports are shared out. Your tier sets how many you get, and you get a range the first time you need one, such as 40000-40009. You can't choose a port outside it, which rules out ports like 80 and 443.

Each VM takes one port automatically, usually the lowest you have free: SSH on Linux, or Remote Desktop on Windows. Anything you open yourself uses the same allowance, so five VMs on a tier with ten ports leaves five for your own services.

That port leads to port 22 on the VM, or 3389 on Windows. Every other port you open keeps the same number on both sides.

Going out to the internet

VMs can reach the internet with nothing to set up, apart from these limits:

  • Email is blocked. Ports 25, 465 and 587 are dropped on the way out, and this will never change. Send through an outside email API instead. These ports do still work between VMs inside the private network.
  • Your network speed is limited by your tier.
  • There's no IPv6. Cloud networks are IPv4 only.
  • Private addresses outside your project are off limits. Other projects, and our own equipment, are blocked.

DNS is set for you when a VM is built, using a public resolver. If names stop resolving, check you haven't overwritten /etc/resolv.conf or your system's network settings.

Other projects

Projects can't see each other, even when they're both yours. To connect two of yours, peer them.

Hosting a website

Ports 80 and 443 aren't available, so use a Cloudflare Tunnel. It connects outward from your VM, needs no open ports, and gives you proper HTTPS on your own domain.