Routers and VPSs without public IPv4

A VPS without a public IPv4 sits only on your private network: it can't be seen from the internet, but it reaches the internet (updates, APIs, outgoing mail) through a router. It's the right way for databases, queues and internal services.

You find the router on the Routers page, if your service includes it.

Creating one

1. Routers › New router: name, private network (the default one, or another one without a router) and location. It's ready in 2–3 minutes.
2. Create the VPSs with the Without public IPv4 option and choose the router's network. The VPS gets an address on the network and uses the router as its gateway.
3. To reach a service of one of these VPSs from outside, on the router page use Forward a port: for example public port 443 to port 443 of the website VPS. The VPSs see the real IP of whoever connects.

To websites and services on the internet, the VPSs behind the router have the router's IP. One router per network.

Good to know

• VPSs without public IPv4 are reached from the panel console, from the other VPSs on the private network or over IPv6 if they have it.
• They don't work for Windows, first-boot apps or additional IPs.
• From inside the network use the VPS's private address, not the router's IP.
• The internet traffic of the VPSs behind the router goes through the router.
• If you delete the router, the network's VPSs stay without internet until you create another one on the same network.