Connect a Virtualizor account
If your VPS provider uses the Virtualizor control panel, you can manage those servers here. For droplets, see Connect a DigitalOcean account.
1. Create an API key in your client area
- Sign in to your provider's Virtualizor client area (usually an address ending in
:4083). - Open Account › API Credentials and create a key.
- Copy the API key and API password. The password is only shown once.
- If the key screen lets you restrict IP addresses, add the portal's IP addresses shown on the connect form.
2. Connect it here
- Go to Cloud accounts › Connect account and choose Virtualizor.
- Enter:
- Account name: anything that helps you recognise it, e.g. "Production VPS".
- Panel URL: the client area address including the port, e.g.
https://panel.example.com:4083. - API key and API password from step 1.
- Tick The panel uses a self-signed certificate only if your provider's panel shows a certificate warning in the browser.
- Reach it: leave Directly over the internet, unless the panel is on a private network. Then choose a connector running in that network.
- Select Test and connect. The portal checks the key with the panel before saving.
Your instances appear on the Instances page within a minute.
If it fails
| Message | What to do |
|---|---|
| Could not reach the Virtualizor panel | Check the URL and port. Ask your provider whether API access is enabled. |
| The panel did not return API data | The URL may point to the website instead of the panel, or the key is wrong. |
| Points to a private or reserved address | The panel is on a private network. Set up a connector and choose it under Reach it. |
| The connector … has not been in touch | The agent isn't running, or can't reach the portal. See Connectors. |
| … is not on this connector's allow list | Add the panel's address and port to allow in the agent's config file and restart it. |
| Virtualizor: … | The message comes straight from the panel, for example an invalid key. |
Security
The API password is encrypted when stored and is never shown again. Every connection and every power action is recorded in the organization's audit log.