WHost

Connect WHost to WISECP to open, suspend and remove hosting accounts and to give customers their WHost tools. The module ships with WISECP 5.0-beta.4.

Accessing the Screen

Open Products → Servers → Add New Server. Select WHost under Server Automation Module. Edit existing records from the server list.

Before You Start

In WHost, create an API key under Settings → API Access. Copy its secret; WHost shows it only once. WISECP connects over HTTPS only and refuses port 80 before sending anything.

If the panel sits behind Cloudflare, allow the WISECP server IP there. Otherwise enter the origin IP as Panel Address and turn off Verify SSL Certificate. Five wrong keys within five minutes block the WISECP IP in WHost for 30 minutes. New accounts stop when the account limit of the WHost license is reached.

Connection and Product Settings

Tasks

Connecting the Server

1. Fill Connection Details and click Test Connection in the server summary. A successful test fills Hostname and the nameservers.
2. Set Maximum Accounts and click Add New Server; check the record in the server list.

Mapping a Product

1. Select WHost in the hosting product’s Automation → Module Assignment section.
2. Under Module Configuration, choose the Plan and the optional settings.
3. Check Resource Limits and click Save Changes; verify the server and plan mapping.

A count limit of 0 stops account creation with an error, because 0 means unlimited in WHost. Enter 1 or more, or mark it unlimited. The addon-domain limit does not count the main domain.

Linking Existing Accounts

On the saved server, click Import → List Results. Each row brings the domain, username, email, creation date and status. Passwords and plans are not imported; set the plan on the service.

Managing the Service

Activation, suspension, reactivation and cancellation run in WHost. The suspension reason stays in WISECP and is not sent to WHost.

In Management → Settings → Module Configuration, choose another plan and click Save Changes; the WHost package changes at once. With Override Product Limits off, the service keeps the product limits in WISECP. Shell access for a single service is also set here.

Seventeen tools cover files, FTP, backups, databases, domains, DNS, email, webmail, PHP, cron jobs and SSL. Redirects do not separate the www form of a domain. An edited DNS record gets a new ID. Remote database access does not cover databases created later. Extracting an archive overwrites files with the same names.

Panel Login opens the WHost sign-in page; the customer signs in with the username and password on the service card. Password changes, phpMyAdmin and IP blocking are not offered. Node.js and Python apps are managed in the WHost panel.

Disk usage is metered in GB. Enabling the disk metric with a maximum sets that WHost disk quota; disabling it restores the plan quota. WHost does not measure or enforce traffic yet, so there is no traffic gauge or metric.

Through the admin API, send module settings inside configuration.creation_info; a top-level creation_info does not reach WHost.

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