SolidCP

Connect SolidCP to manage Windows hosting accounts and their hosting packages from WISECP.

Accessing the Screen

Open Products / Services → Servers, then click Add New Server. In Server Automation Module, select SolidCP. The address is {admin}/products/servers-add.

Before You Connect

Use a working SolidCP Enterprise Server and a Serveradmin or Reseller Portal account with assignable hosting plans. WISECP requires PHP SOAP support. IIS bindings and the firewall must allow WISECP to reach the Enterprise Server. A localhost-only binding cannot accept a remote connection.

Prepare the Portal address separately. The module needs an available WISECP module license, an active server record and a hosting product priced in your chosen currency. Existing server records also 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 reads the connecting account through SOAP. Success does not prove package creation or resource management permissions.
3. Complete Identity and Capacity and click Add New Server; check the saved record. For an existing record, use Save Changes.

Mapping a Product

1. In a hosting product, open Automation → Module Assignment and select SolidCP.
2. Under Server Configuration, select Single Server or Server Group. Choose Module Configuration → Hosting Plan.
3. Review Resource Limits and pricing. Keep the first product hidden and Automatic Setup disabled.
4. Click Save Changes; confirm the server and plan mapping.

Plan selection fills disk, bandwidth and domain limits where available. Other shared limits default to unlimited; this does not grant resources absent from the SolidCP plan. Provisioning creates a Portal user and a hosting package. It does not separately create a website, mailbox or database.

Linking Existing Accounts

On the saved server, click Import → List Results. Only customer accounts appear; matching uses the username. The domain is blank. Passwords, hosting plan and package identifiers are not imported. Connection errors can also produce an empty list.

Select accounts and map their customer, product, billing period and dates. Click Import below the list; check them under Linked Services. A user with several packages can resolve to its first package. Verify that association in SolidCP before enabling automation.

Managing the Service

Supported operations cover creation, suspension, reactivation, termination and password changes. Suspension targets both package and user. In Management → Settings → Hosting Plan, select a plan and click Save Changes. Product upgrades also apply a plan to the existing package.

Administrators and customers use enabled tools in the service’s Management tab. Server Preferences and service restrictions can hide them.

• Databases: create/delete databases and users, change user passwords and assign database access. User renaming is unavailable. The package needs an allocated SQL service; MySQL takes precedence when multiple engines exist.
• FTP accounts: create, edit and delete. Per-account quotas are unavailable.
• Email accounts and the DNS zone editor: list, create, edit and delete within the package. DNS requires the service domain to exist in the package.

Disk and bandwidth are collected in MB. The domain counter comes from package quotas. Email/database zeros in the overview are not verified usage counts. Failed quota reads can also show zero usage and unlimited capacity.

Prices, add-ons and order requirements are not created automatically. Plan selection is not periodic catalog synchronization. Before enabling automation, compare an existing test service’s Management → Overview with SolidCP.

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