Skip to navigation

Networking for VMs

Each VM has a network setup that lets you decide two things: who can reach the VM (anyone on the internet, or only your other VMs), and what the VM itself can reach. You choose the setup when you create the VM, and you can change most of it later on the VM’s Settings tab. A firewall group then decides which ports are open.

Which network mode to choose

ModeWho can reach the VMCan the VM reach the internet?Use it for
Public IP (default)Anyone on the internet, on the ports the firewall allowsYesWebsites, APIs, anything you SSH into from your laptop
Private + NATOnly machines in the same VPCYes, outgoing onlyBackground workers and databases that must download updates but never accept connections from the internet
Private onlyOnly machines in the same VPCNoDatabases and internal services that must never touch the internet

Terms used on this page:

  • Public IP: an internet address other computers use to reach the VM.
  • VPC (virtual private cloud): a private network of your own. VMs in the same VPC talk to each other on private addresses.
  • NAT (network address translation): lets private VMs share one public address for outgoing traffic, while blocking incoming connections.
  • Reserved IP: a public address you own separately from any VM, so you can keep it when you replace the VM.

How it works

  1. At creation, you pick a mode under Network Configuration. With Public IP, IBEE assigns an address (or uses a Reserved IP you pick).
  2. At first boot, the VM’s address, gateway and DNS servers are written into its network settings by cloud-init (the first-boot setup tool). The VM uses a fixed address, not DHCP.
  3. A firewall group is attached: one you choose, or IBEE’s default group.
  4. Traffic arrives at the VM only if the firewall group allows it. The VM’s own firewall (for example ufw) applies as well.

Before you begin

  • For Private + NAT or Private only, create a VPC and a subnet in the same location first. Private + NAT needs a VPC with a NAT gateway.
  • For a fixed public address, create a Reserved IP in the same location.
  • You need write access to the workspace to change networking.

Set up networking when you create a VM

1

Pick the mode

On the Deploy page, under Network Configuration → VM network → Internet and VPC access, choose Public IP, Private + NAT or Private only.

2

Pick a VPC and subnet (if needed)

With a private mode, pick a VPC and a Subnet. With Public IP, you can keep No VPC · public interface only, or pick a VPC to give the VM a private address too. Only VPCs that fit the mode, in the VM’s location, are listed.

3

Choose the public address (Public IP only)

Under Reserved public IP, keep Allocate automatically, or pick one of your unattached Reserved IPs in this location. A Reserved IP can be on one VM at a time, so picking one limits the deploy to one VM. A private VPC needs a Reserved IP for public access.

4

Choose a firewall group

Under Firewall, pick a group or click Create Group. If you pick none, the default firewall group is attached.

Firewalls

A firewall group is a list of rules that decides which incoming connections reach the VM. The default firewall group has these rules:

DirectionAllowedPort
InboundSSHTCP 22
InboundHTTPTCP 80
InboundHTTPSTCP 443
InboundRemote Desktop (RDP)TCP 3389
InboundCommon app portsTCP 8000–8080
InboundEverything else, including ping (ICMP)Dropped
OutboundAll trafficAll

The default group is shared by every VM that has no group of its own. To open other ports, or to allow SSH only from your own address, create your own firewall group and attach it to the VM. Attaching your own group replaces the default for that VM; detaching it puts the default back.

Firewalls inside the VM (ufw, firewalld, Windows Defender Firewall) apply too. A port must be open in both to be reachable.

Inside the VM

Check the VM’s addresses and routes:

ip -4 addr show
ip route

The network settings are written once, at first boot. If you change them by hand and lose the connection, you can’t fix it from a browser console yet, so test on a snapshot copy first.

Change networking after creation

Open the VM, then the Settings tab.

IPv4 & Reserved IP

  • Main VM address: the address IBEE assigned, Managed with VM. If the VM also has a NAT VPC as its default route, Keep as Reserved opens Remove direct public network: the address is kept as a Reserved IP, and the VM switches to the NAT VPC for outgoing traffic. Direct inbound traffic to the address stops.
  • Attach IP / Attach or Move IP: attach one of your Reserved IPs in the same location, or move one from another VM.
  • Detach IP: public traffic to that address stops; the address stays in Reserved IPs (and stays billed).
  • Repair network: shown only for an older VM that has no active network interface.

VPC Networks

Lists the VM’s VPC interfaces with their private IP, subnet and VPC ID.

  • Attach VPC: pick the VPC and Subnet, choose Private IP assignment (Automatic, or Specific address), then click Attach VPC. For a NAT VPC you can choose Use VPC for internet (it becomes the default route) or Private traffic only.
  • Detach VPC: removes an interface. A VM always keeps at least one interface, so the main one can’t be removed until another route exists.

Reach a private VM

Private + NAT and Private only VMs can’t be reached from the internet. Overview → Connection Details shows the private SSH or RDP command to run from inside the VPC, for example from another VM in the same VPC that has a public IP (a “jump host”):

ssh -J ubuntu@203.0.113.10 ubuntu@10.10.0.5

Point a domain at the VM

At your DNS provider, add an A record for your domain with the VM’s public IP, and a CNAME for www if you need one. Use a Reserved IP so the address doesn’t change when you replace the VM.

Bandwidth

Value
Inbound dataFree
Outbound data included1 TB to 16 TB per VM per month, depending on the plan. See Instance types.
Outbound data above the allowanceCharged per GB
Where to see usageMonitoring → Network Traffic → Monthly outbound

Load balancing

To spread traffic across several VMs, put a Load Balancer in front of them. A load balancer has no region and isn’t attached to a VPC: it reaches each VM on the VM’s public IPv4 address. So each backend VM needs Public IP networking, and its firewall group must allow the port your app listens on. See Attach VMs.

Limits

Value
Public IPv4 addresses with Public IP mode1 per VM, plus any Reserved IPs you attach
A Reserved IPOn 1 VM at a time, in the same location
VPCsIn the same location as the VM
Default DNS servers1.1.1.1 and 8.8.8.8, unless the network provides others

Troubleshooting

You seeWhat it meansWhat to do
ssh: connect to host … port 22: Connection timed outA firewall blocks port 22, or the VM is privateCheck the VM’s firewall group allows TCP 22 from your address. For private VMs, connect through a VM in the VPC.
ping gets no reply, but SSH worksThe default firewall group drops ping (ICMP)Expected. Add an ICMP rule in your own firewall group if you need ping.
Your app works on curl http://localhost:3000 inside the VM, but not from outsidePort 3000 is closed in the firewall groupRun the app on port 80, 443 or 8000–8080, or add a rule for its port in your own group. Check ufw status too.
No address in the IP Address columnPrivate + NAT and Private only VMs have no public IP; or the VM is still being createdExpected for private modes. Otherwise wait for Running, then check Activity logs.
Deploy says a Reserved IP is requiredYou chose Public IP with a private VPCCreate a Reserved IP in the same location, or pick No VPC.
A private VM can’t download updatesIt’s Private only, which has no internet routeUse Private + NAT, or attach a NAT VPC with Use VPC for internet.