How to Configure Additional IP Addresses on Your AVIOX Cloud VPS

How to Configure Additional IP Addresses on Your AVIOX Cloud VPS

untitled-design-17.png

As your projects grow, you may eventually need more than one IP address on your AVIOX Cloud VPS. Whether you’re hosting multiple websites, running isolated applications, setting up SSL certificates, or managing advanced network configurations, additional IP addresses give you greater control and flexibility. AVIOX Cloud makes it easy to attach secondary IPs to your VPS—allowing you to expand your server’s capabilities without upgrading your entire system.

In this guide, you'll learn what additional IPs are used for, how to request and assign them through AVIOX Cloud, and how to configure them on your Linux server so everything functions smoothly.


1. Why You May Need Additional IP Addresses

An additional IP address allows you to assign unique network identities to different services running on a single VPS. This becomes especially useful when you want to:

✔ Host multiple websites

Each domain can be mapped to a dedicated IP, often required for legacy systems or separate SSL certificates.

✔ Separate applications

If you have projects that must remain isolated, different IPs help segment traffic.

✔ Run game servers or APIs

Some applications need dedicated IPs for inbound connections.

✔ Improve email deliverability

Using a clean, isolated IP for outbound mail reduces spam risks.

✔ Improve security

Multiple IPs allow filtered access control, firewalls, or segmented services.

Whatever your use case, AVIOX Cloud offers flexible network expansion without needing multiple servers.


2. Requesting Additional IP Addresses on AVIOX Cloud

Before configuring extra IPs inside the OS, you first need to assign them from your AVIOX Cloud dashboard.

Step 1: Log in to your AVIOX Cloud account

Go to the dashboard and open the server you want to modify.

Step 2: Navigate to the IP Management section

Here you'll find your primary IP and available networking tools.

Step 3: Request additional IPs

Select “Add IP Address” or “Request Additional IP.”
Your new IP(s) will be assigned and appear under your server’s list of IP addresses.

Once assigned, the IP is routed to your VPS but not yet active inside the operating system. You must configure it manually to make it usable.


3. Preparing Your Server for Additional IPs

After AVIOX Cloud assigns the IP, log in to your Linux VPS using SSH.

You will need:

  • The newly assigned IP
  • The subnet mask (usually /32 or /24 depending on configuration)
  • The gateway (your main server gateway)

Your hosting dashboard usually displays these details.


4. Configuring Additional IPs on Linux

The steps depend on the Linux distribution. Below are the most common ones.


A. Ubuntu / Debian (Netplan)

  1. Locate your network configuration file:

     
    /etc/ netplan / 50 - cloud - init .yaml 
  2. Edit the file:

     
    nano /etc/ netplan / 50 - cloud - init .yaml 
  3. Add your secondary IP under the addresses: section:

    Example:

     
    network:   version: 2   ethernets:     ens3:       dhcp4: yes       addresses:         - 203.0.113.10 /32         - 203.0.113.11 /32  
  4. Apply changes:

     
    netplan apply 

Your extra IPs are now active.


B. Ubuntu/Debian (Legacy /etc/network/interfaces)

  1. Open the interfaces file:

     
    nano /etc/network/interfaces 
  2. Add each additional IP as an alias:

     
    auto ens3: 0 iface ens3: 0 inet static    address 203.0.113.10    netmask 255.255.255.255 auto ens3: 1 iface ens3: 1 inet static    address 203.0.113.11    netmask 255.255.255.255  
  3. Restart networking:

     
    systemctl restart networking 

C. CentOS / AlmaLinux / Rocky Linux

  1. Navigate to the network-scripts directory:

     
    cd /etc/sysconfig/network-scripts/ 
  2. Create an alias file:

     
    nano ifcfg-ens3: 0  
  3. Add:

     
    DEVICE =ens3: 0 BOOTPROTO =static ONBOOT = yes IPADDR = 203.0 . 113.10 NETMASK = 255.255 . 255.255  
  4. Restart the network:

     
    systemctl restart network 

Your secondary IP is now configured and active.


5. Verifying Your Additional IP Configuration

To ensure your additional IPs are working correctly, run:

Check IP list:

 
ip addr 

Ping test:

 
ping - c 4 your - secondary - ip 

Check connectivity from outside

Use a remote machine to ping or run:

 
curl http://your-secondary-ip 

If configured properly, you should receive responses immediately.


6. Assigning Additional IPs to Different Services

Once your extra IPs are active, you can map them to specific:

  • Apache or Nginx virtual hosts
  • Docker containers
  • Mail servers
  • Game servers
  • Applications listening on custom ports
  • SSL certificates

Example for Nginx:

 
server {     listen 203.0.113.10:80 ;     server_name example.com; } 

Each IP can host entirely separate environments.


7. Common Issues and Fixes

✔ Additional IP not responding

Likely causes:

  • IP not added to OS configuration
  • Firewall blocking new IP
  • Networking service not restarted

✔ Cannot route traffic

Ensure gateway is correct and not duplicated.

✔ Cloud-init overwriting your configuration

Disable cloud-init networking:

 
touch /etc/cloud/cloud-init.disabled 

✔ Firewall blocking access

Allow traffic:

 
ufw allow from any to 203.0.113.10  

8. Final Thoughts

Configuring additional IP addresses on your AVIOX Cloud VPS is a powerful way to enhance flexibility, scalability, and security. Whether you're hosting multiple sites, running isolated applications, or building complex infrastructures, extra IPs allow your server to function like multiple independent systems. The process is simple: request new IPs from your AVIOX dashboard, configure them inside your server, verify connectivity, and map them to your applications. Once set up, your VPS becomes more dynamic, secure, and capable of handling advanced workloads with ease.


Share:


Your experience on this site will be improved by allowing cookies Cookie Policy