Virtualizor server groups collect slave servers that should be treated as one pool, such as all servers in one data centre. New VPSs created for a group are placed on a server inside it, which is how you offer locations and keep hardware classes apart.
Before you start
- A Virtualizor master with one or more slave servers (add a slave server).
- A naming plan, for example Germany, USA, Singapore NVMe.
Create Virtualizor server groups
- In the admin panel go to Servers → Server Groups → Add Server Group.
- Enter a name and a short description customers may see.
- Choose how a server is selected for new VPSs (for example the server with the most free resources), if your version offers the option.
- Save.
Assign servers to groups
- Go to Servers → List Servers and edit a server.
- Select its server group and save.
- Keep each group to one location and similar hardware so customers get consistent performance.
Tip: Lock or disable a nearly full server for new VPSs so existing customers keep room to upgrade.
IP pools per group
Each server needs IPs available for new VPSs. Link IP pools to the servers in the group, or creation fails even with free RAM (IP pools and templates).
Offer locations in WHMCS
- Create one product per location with its server group set in the module settings, or
- Use a configurable option for location mapped to the server groups, as the Virtualizor module supports.
- Place a test order for each location.
Troubleshooting
- VPS created on the wrong server: the product or plan uses the wrong group.
- "No server available": every server in the group is full, locked or lacks IPs.
Frequently asked questions
Can a server belong to more than one group?
A server belongs to one group, which keeps placement predictable.
Can customers move to another location?
It requires migrating the VPS, usually with new IPs (migrate a VPS).
Do groups affect plans?
Plans define resources; groups decide where VPSs run. Use them together.