{"article":{"id":"171ecc7a26834cb021c8dec8b5d5eaf9","categorySlug":"cloud-vps","slug":"private-networks","title":"Connect servers with private networks","excerpt":"Create an isolated private network, attach your cloud servers to it, and let them talk to each other without touching the public internet.","body":"A private network is an isolated network that only your own cloud servers can join. Traffic between the attached servers stays inside our platform — it never crosses the public internet. That makes private networks the right tool whenever your servers need to talk to each other: an application server reaching its database, background workers sharing a queue, or any service you would rather not expose publicly at all.\n\nEach server keeps its normal public IP address; the private network is added alongside it as a second connection.\n\n# What you need first\n\nPrivate networks connect cloud servers: Cloud VPS, GPU VPS and Cloud Instances. You need at least one active cloud server before you can create a network — if you have none yet, the create window shows a notice and points you to ordering one. See [Deploy a server and connect](/kb/deploy-and-connect-vps) if you are starting from scratch.\n\n# Create a private network\n\n1. In the portal sidebar, click **Private Networks**.\n2. Click **Create network** in the top right.\n3. In the \"Create a private network\" window, type a **Network name** — for example \"production\" (up to 64 characters).\n4. Click **Create**.\n\nAddressing is assigned automatically — the name is the only thing you choose. A confirmation shows the network's address range, and the new network appears in the list with its name, status, range and member count.\n\n# Attach a server\n\n1. On the **Private Networks** page, click a network card to expand it.\n2. In the row at the bottom of the card, pick a server from the **Select a server…** dropdown. It lists your active Cloud VPS, GPU VPS and Cloud Instance servers.\n3. Click **Attach server**.\n\nThe private interface is added to the server live — no restart is needed. The server first appears in the members list with an \"attaching\" status and flips to \"active\" shortly after (the list refreshes automatically while this happens).\n\n![An expanded private network card with two attached servers and the attach-server row](/assets/kb/cloudnet/private-networks.png)\n\nThe members table shows each attached server with its **Private IP**, MAC address and status. Use the private IP to reach a server from the other members — for example, point your application at the database server's private IP instead of a public address.\n\n\u003e A server on a private network still has its public IP. If a server should only be reachable privately — a database, for instance — enable the [cloud firewall](/kb/vps-cloud-firewall) on it and leave its public ports closed.\n\n# Detach a server\n\n1. Expand the network card and find the server in the members table.\n2. Click **Detach** in its row and confirm.\n\nIf the server is currently a backend of a load balancer, detaching is refused — remove it from the load balancer first. See [Set up a load balancer](/kb/load-balancers): load balancers deliver traffic to your servers over a private network, so the two features work together.\n\n# Delete a network\n\n1. Expand the network card.\n2. Click **Delete network** in the card footer and confirm. Every attached server is detached automatically.\n\nA network cannot be deleted while a load balancer still uses it — delete the balancer first.\n\nIf a server stays in the \"attaching\" state or a member shows an error status, open a ticket from **Tickets** in the portal and we will take a look.","status":"published","position":7,"createdAt":"2026-07-15T11:11:28Z","updatedAt":"2026-07-15T11:11:28Z"},"related":[{"id":"d8103957296579e9e635fc7800bda7a2","categorySlug":"cloud-vps","slug":"choosing-a-vps-line","title":"Choose a line: Standard, 100 Gbps, GPU or hourly Cloud Instances","excerpt":"Understand the difference between fixed Cloud VPS and GPU VPS plans and build-your-own Cloud Instances, and pick the right line and billing mode for your workload.","position":1,"status":"published"},{"id":"c9cf35dfb5bb44829ae9715fe04d2446","categorySlug":"cloud-vps","slug":"deploy-and-connect-vps","title":"Deploy a server and connect","excerpt":"Create a cloud server, follow the build, find its IP address and root password, then log in over SSH or through the web console in the portal.","position":2,"status":"published"},{"id":"0c8ceb77aec6974293a8891d6f1cfd91","categorySlug":"cloud-vps","slug":"vps-snapshots-backups","title":"Snapshots and backups","excerpt":"Take and restore snapshots of your VPS, and enable the Backups add-on for full copies stored separately from your server.","position":3,"status":"published"},{"id":"d0b4b2a67b8b95c63cbf6cfc1eb4bc21","categorySlug":"cloud-vps","slug":"vps-resize-plan-change","title":"Resize or change plan","excerpt":"Scale a cloud server up or down — resize a Cloud Instance's vCPU and memory, or move your Cloud VPS or GPU VPS to a bigger or smaller plan.","position":4,"status":"published"},{"id":"0485ae6dd65a367370dbbed64cad33f3","categorySlug":"cloud-vps","slug":"vps-cloud-firewall","title":"Use the cloud firewall","excerpt":"Enable the per-server cloud firewall, open only the ports you need with presets or custom rules, and deploy changes safely without locking yourself out.","position":5,"status":"published"}]}