How to Resize Your VPS Without Losing Your IP Address
Resizing a VPS is one of the most common scaling tasks developers face — and the most common fear is losing the IP address tied to DNS records, firewalls, or payment gateway whitelists. The good news: on a well-architected cloud platform, your IP stays put when you resize. Here is exactly how it works, what to watch out for, and how CM Cloud’s Cloud VPS handles it.
Why Your IP Address Matters When Resizing
Your server’s public IP address is woven into your infrastructure in ways that are easy to forget until something breaks:
- DNS A records pointing your domain to that IP
- Firewall allowlists on databases or third-party APIs
- Payment gateway whitelists (Stripe, PayPal, MTN MoMo)
- SSL certificate SANs in some configurations
- SSH known-hosts entries on your team’s machines
If a resize forces an IP change, every one of those entries needs updating — often under pressure, often causing downtime. Avoiding that is the entire point of this guide.
How Cloud VPS Resizing Works (The Short Version)
Modern cloud virtualisation (KVM/hypervisor-based) separates compute resources from network identity. Your IP address is assigned to a virtual NIC, not to the physical CPU or RAM. When the hypervisor reallocates vCPUs and memory, the NIC — and its IP — stays attached to your VM.
This means a vertical resize (more CPU, more RAM, more disk) typically preserves your IP automatically. You get a brief reboot window, not a new machine.
Horizontal scaling (spawning extra VPS instances behind a load balancer) gives new instances new IPs by design — that is expected and managed separately.
Step-by-Step: Resize Your CM Cloud VPS Without Losing Your IP
1. Log in to the CM Cloud Portal
Head to the Cloud VPS section of your dashboard. You will see your active instance, its current plan, and a Resize or Upgrade Plan option.
2. Snapshot or Backup First (Best Practice)
Before any resize operation, take a snapshot of your current disk state. This is not strictly required for an IP change — resizing does not wipe your disk — but it is professional hygiene. If something goes wrong mid-resize (rare but possible on any platform), you restore from snapshot rather than rebuild.
3. Select the New Plan
Choose the target plan. CM Cloud’s Cloud VPS Starter is 2 vCPU / 4 GB RAM / 80 GB NVMe at $7.99/mo (XAF 5,000 / €7.40). If you need more resources, contact the support team for custom specs — cloud infrastructure scales vertically as your load grows.
4. Confirm and Reboot
The portal will confirm that your IP address will be preserved. The instance powers down, the hypervisor reallocates resources, and the instance boots back up — typically within 60–90 seconds. Your IP, hostname, and all data remain intact.
5. Verify After Reboot
SSH back in using the same IP. Run ip addr show to confirm the address. Check that your web server, database, and any background services have resumed. If you use a process supervisor like systemd (which CM Cloud configures for App Hosting runtimes), services restart automatically.
What Can Cause an IP Change During a Resize?
IP loss during resize is almost always caused by one of these scenarios:
- Provider migrates you to a different physical host — some budget providers do not guarantee IP persistence across host migrations. Always confirm with your provider before resizing.
- You accidentally destroy and recreate the instance — a resize and a rebuild are different operations. Never delete your VPS if you only want to scale it.
- Floating IP not configured — on platforms that use floating IPs, if your IP is not attached to a floating address, a host migration can change it. CM Cloud assigns IP directly to the instance and maintains it through resize operations.
- IPv6 prefix delegation changes — IPv6 can behave differently from IPv4 during migrations. If IPv6 connectivity matters, test it post-resize.
CM Cloud VPS vs Competitors: Pricing at a Glance
| Provider | Starter VPS Price (USD) | XAF | EUR | IP on Resize |
|---|---|---|---|---|
| CM Cloud | $7.99/mo | XAF 5,000 | €7.40 | Preserved |
| DigitalOcean | $6.00/mo | ~XAF 3,750 | ~€5.55 | Preserved (same droplet) |
| Hostinger VPS | $7.99/mo (promotional) | ~XAF 5,000 | ~€7.40 | Preserved |
| Vultr | $6.00/mo | ~XAF 3,750 | ~€5.55 | Preserved (same instance) |
Key difference: CM Cloud prices are transparent, renew at the same rate, and are quoted directly in XAF — no currency conversion surprises for Cameroonian and West African customers. Competitors quote USD only, and renewal prices often jump after the promotional period.
See full plan details at cmcloudhosting.com/pricing.
DNS: Update Records After a Resize (Only If IP Changed)
If — in the unlikely event — your IP did change (for example, you migrated providers), here is the fast recovery checklist:
- Update DNS A records at your domain registrar. CM Cloud has the cheapest domain registration prices on the market — if your domain is registered with CM Cloud, you update DNS directly in the same portal.
- Wait for TTL to expire — if your previous TTL was 3600 (1 hour), traffic will fully propagate within that window. Set TTL to 300 before future maintenance windows.
- Update firewall rules at any third-party service that whitelists your server IP.
- Update SSH known_hosts on team machines to avoid false host-key warnings.
Pro Tip: Use a Domain or Subdomain as Your Canonical Address
Instead of hardcoding an IP address anywhere in your stack, point a subdomain (e.g., api.yourcompany.com) to your VPS IP. Every internal service, every partner integration, every firewall rule uses the domain name. If the IP ever changes — migration, provider switch, disaster recovery — you update DNS in one place and everything else heals automatically.
This is the single most effective practice to eliminate IP-dependency pain.
Cloud VPS on CM Cloud: What You Get
The Cloud VPS Starter plan at $7.99/mo (XAF 5,000 / €7.40) includes:
- 2 vCPU — dedicated virtual cores
- 4 GB RAM — suitable for Node.js APIs, Django apps, Laravel backends, or headless WordPress
- 80 GB NVMe SSD — fast read/write for databases and application files
- Full root SSH access — install any software, configure any service
- IP persistence on resize — no surprise address changes
- Pricing in USD, XAF, and EUR — billed in your local currency with no hidden FX fees
For developers already using CM Cloud App Hosting for managed runtimes, the Cloud VPS is the natural complement when you need full OS-level control — custom kernel modules, direct PostgreSQL installs, or self-hosted services that go beyond the App Hosting runtime model.
Explore the full plan at cmcloudhosting.com/pricing.
Summary
Resizing your VPS does not have to mean losing your IP address. On CM Cloud Cloud VPS — and any reputable KVM-based provider — your public IP is tied to your virtual NIC, not to raw hardware. Upgrade your plan, reboot, and come back to the same address your DNS, firewalls, and clients already know.
The keys to a clean resize:
- Snapshot before you start
- Use the Resize action, never delete-and-recreate
- Use a domain name (not a raw IP) in all integrations
- Verify IP and services immediately after reboot
Get Started with CM Cloud VPS
Ready to scale without the IP headache? CM Cloud Cloud VPS starts at $7.99/mo (XAF 5,000 / €7.40) with transparent renewal pricing, NVMe storage, and full root access.
👉 View Cloud VPS plans at cmcloudhosting.com/pricing
Questions about migrating from another provider or resizing an existing instance? The CM Cloud support team is available to walk you through it — no ticket queue runaround.