Skip to main content
The network is configured when the server is provisioned and works out of the box. You edit it by hand to add an IPv4 address or set up IPv6.
A mistake in the network config cuts off SSH. Change one parameter at a time and check login from a second window without closing the current one. If access is lost, log in through Console on the server card, not every server has it. The last resort is Reinstall, but it wipes all data.

Additional IPv4

There is no button in the bot, the address is issued by support @lumisup_robot. Once you get the address, netmask, and gateway, set them in the OS.
  1. Config – a file in /etc/netplan/, such as 01-netcfg.yaml or 50-cloud-init.yaml. ip a shows the interface name, often eth0 or ens3.
  2. Address – add the second one to the addresses list. Here 192.0.2.10 is the primary IP and 192.0.2.11 the added one, substitute your own:
    /etc/netplan/01-netcfg.yaml
  3. Apply – netplan try applies the config and rolls it back after 120 seconds unless you confirm. That way a typo will not cut off access:

IPv6

If you have been given an IPv6 address and gateway, set them up the same way. Add the lines to the current config, do not remove the IPv4 addresses.
/etc/netplan/01-netcfg.yaml
to: "::/0" is the default route for IPv6, like default for IPv4. Apply: netplan apply.
Check the address and connectivity:

Check

  • ip a – addresses and interfaces.
  • ip route – the routing table.
  • ping -c 4 1.1.1.1 – whether the server reaches the outside.
The connection keeps dropping – look at the route with MTR, it combines ping and traceroute:
Next: Firewall, Reverse DNS, VPS not working.