VestaCP

Connect VestaCP to automate hosting accounts and manage supported hosting resources from WISECP.

Accessing the Screen

Open Products / Services → Servers and click Add New Server. Select VestaCP under Server Automation Module. Address: {admin}/products/servers-add.

Before You Connect

Prepare a working VestaCP server, an administrator account and a hosting package. Allow WISECP to reach its API. This module uses the administrator’s username and password, as described in the VestaCP API guide; it does not use an access key.

WISECP needs an available module license, an active server record and a hosting product priced in your selected currency. Saved servers provide Preferences, Linked Services and Import.

Connection and Product Settings

Tasks

Connecting the Server

1. Complete Connection Details and click Test Connection.
2. The test requests the account list. It does not prove account creation or hosting tool permissions; an empty response is not an end-to-end result.
3. Complete Identity and Capacity, then click Add New Server. Check the saved record; editing uses Save Changes.

Mapping a Product

1. In the hosting product, open Automation → Module Assignment and select VestaCP.
2. Under Server Configuration, select Single Server or Server Group. Choose Module Configuration → Package.
3. Check Resource Limits and pricing. Keep the first product hidden and Automatic Setup disabled.
4. Click Save Changes; verify the saved server and package.

Package selection fills available disk, bandwidth, email, database, web-domain and alias limits. Disk and bandwidth use MB. Shared limits without a matching VestaCP setting do not create additional panel capabilities.

Provisioning creates the user, applies selected shell access and adds the primary web domain. VestaCP assigns an available IP. Initial provisioning replaces stored passwords containing special characters with a generated alphanumeric password. A later step can fail after creating the user; inspect the account and domain before retrying.

Linking Existing Accounts

On the saved server, click Import → List Results. Administrator accounts are excluded. Each account uses its first listed web domain; check it carefully when several domains exist. Matching uses the domain. Passwords and package settings are not imported.

Select accounts and map their customer, product, period and dates. Click Import below the list; review Linked Services. This links records without moving files. Empty lists or domains can also indicate API errors.

Managing the Service

Account actions include creation, suspension, reactivation, termination and password changes. In Management → Settings → Package, select a package and click Save Changes. Product upgrades also reapply package limits.

Service limit overrides support disk, bandwidth, email accounts, databases and web domains. A later package change replaces those overrides. Resetting limits needs a saved package; imported services may not have one.

Administrators and customers use enabled tools in Management. Server Preferences and service restrictions control visibility:

• FTP: create/edit/delete, without per-account quota. Databases: create/delete and change the bound user’s password; no independent users or privilege editor.
• Addon domains and subdomains: create/delete, without renaming or custom document roots. DNS records: create/edit/delete.
• Email accounts and forwarders: create/edit/delete. Webmail opens the mail login page.
• Cron jobs: create/edit/delete, without a notification email field. Backups: create/restore/delete whole-account archives; no browser download.
• SSL: list certificates, request Let’s Encrypt or remove SSL. Custom certificate upload and reinstallation are unavailable.

Panel links open normal login, without automatic sign-in. The overview shows disk, bandwidth and resource counts. Automatic metrics collect disk, bandwidth, emails, databases and all web domains. The addon-domain gauge excludes the primary domain and its subdomains; its limit still shares VestaCP’s web-domain pool. Do not treat that gauge as the metric’s count.

No product prices or order requirements are generated. Shell Access requires a separately configured add-on; it is not created automatically. Package selection is not periodic catalog synchronization. Before enabling automation, compare an existing test service’s Management → Overview and resources with VestaCP.

Important Notes

Required Permissions

Server settings require MODULES_SERVERS_SETTINGS; product editing requires PRODUCTS_OPERATION. Service actions require their corresponding service permissions.

Related Articles

• Adding a Server
• Product Automation
• Service Management