Virtualizor

View and configure VPS IP addresses (IPv4 and IPv6) in Virtualizor

Find your VPS IPv4 and IPv6 addresses, gateway and netmask in Virtualizor, add an extra IP inside Linux, enable IPv6 and fix networking after changes.

IntermediateVirtualizor VPS2 min read

Every VPS has at least one public IPv4 address, and many also have an IPv6 address or subnet. Virtualizor shows the addresses assigned to your server and usually configures the main one automatically during OS installation. Additional IPs sometimes need to be added inside the operating system by hand.

Before you start

  • Access to the Virtualizor panel and SSH or VNC access to the VPS.
  • Additional IP addresses are ordered from your provider; you cannot assign them yourself in Virtualizor.

Find your IP details

  1. Log in to Virtualizor and open your VPS.
  2. Look at the overview or the IPs / Network section. It lists each IPv4 address and IPv6 address or subnet.
  3. Note the netmask (or prefix, such as /24) and gateway if shown. If not, ask support or check the current configuration inside the VPS.

Inside the VPS, ip -br addr shows configured addresses and ip route shows the default gateway.

Add an extra IPv4 on Ubuntu (Netplan)

  1. Open the Netplan file, for example /etc/netplan/50-cloud-init.yaml.
  2. Under your interface (often eth0 or ens3), add the new address to the addresses list, for example - 203.0.113.11/32 next to the existing one.
  3. Test safely with netplan try; it rolls back automatically if you lose connection.
  4. Apply with netplan apply.

Add an extra IPv4 on AlmaLinux / Rocky (NetworkManager)

nmcli con mod "System eth0" +ipv4.addresses 203.0.113.11/32 && nmcli con up "System eth0"

Use nmcli con show to find the correct connection name. Keep the VNC console open while you change networking, so you can fix mistakes.

Enable IPv6

If Virtualizor lists an IPv6 address but the VPS has no IPv6 connectivity, add it with the IPv6 gateway your provider gives you. With Netplan add the address (for example 2001:db8::10/64) and a routes entry to ::/0 via the gateway. Test with ping -6 google.com. Remember to add AAAA DNS records and an IPv6 PTR if you use IPv6 for mail.

Use an extra IP

  • Websites: bind a site or SSL certificate to it in your web server or control panel.
  • Mail: configure the mail server to send from it, and set rDNS for it. See set rDNS in Virtualizor.
  • Control panels: Plesk and DirectAdmin detect new IPs after a re-read (Plesk: Tools & Settings → IP Addresses → Reread IP).

Troubleshooting

  • Lost connection after editing network files: use the VNC console to revert the change.
  • Extra IP does not respond: the address is configured with the wrong prefix, or the provider has not routed it yet. Check ip addr and ask support.
  • IP changed after reinstall: it should not; reinstalling keeps the assigned IPs. If networking is missing, check the template's configuration in VNC.
  • Check your public IP: run curl -4 ifconfig.co or use the IP checker.

Next steps

Was this guide helpful?

Still stuck?

Ask MdmHost AI for a quick answer, or open a ticket and our team will take a look. We are here 24/7.