# ISPmanager

https://docs.wisecp.com/de/ispmanager

Connect ISPmanager to WISECP to provision hosting accounts and let customers manage their hosting tools.

## Accessing the Screen

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

## Before You Start

Prepare a licensed ISPmanager 6 server and its root account. The API account needs user and preset management, user-context tools and session-key creation permissions. WISECP needs PHP cURL and access to the panel API.

Sales require an active server, an available module license and a hosting product priced in your chosen currency. Saved servers have **Preferences**, **Linked Services** and **Import** sections.

## Connection and Product Settings

- **Address / Hostname**: Both required. Address is the connection destination. The default port is 1500; the module adds /ispmgr itself.
- **Username / Password**: Both required. Enter the server administrator credentials. This module does not use an API token.
- **Verify SSL Certificate**: Enabled for new servers. Keep SSL and certificate verification enabled. Use Custom Port selects a different port.
- **Identity and Capacity**: Monthly Cost starts at zero; choose its currency. Maximum Accounts defaults to 200 when blank. The occupancy alert follows this limit. Nameservers accepts four lines.
- **Package (Preset)**: Required for account creation. Select an existing preset in Automation → Module Configuration. Opening the selector loads preset names; selection does not auto-fill resource limits.

## Tasks

### Connecting the Server

1. Complete **Connection Details** and click **Test Connection** in the server summary.
2. The test reads the user list. Success does not verify every hosting tool or permission to change accounts.
3. Complete **Identity and Capacity**, then click **Add New Server**; verify the list entry. When editing, use **Save Changes**.

### Mapping a Product

1. Select **ISPmanager** in the hosting product’s **Automation → Module Assignment** section.
2. Under **Server Configuration**, choose **Single Server** or **Server Group**. Set **Module Configuration → Package (Preset)**.
3. Check **Resource Limits** and prices. Keep the initial product hidden and **Automatic Setup** disabled.
4. Click **Save Changes**; verify the product’s server and plan mapping.

CPU Limit (units), Memory Limit (MiB), Process Count Limit and Email Box Quota (MiB) are optional. Blank values inherit the preset. Main IP Address Type defaults to Shared; IPv4 or IPv6 requests automatic allocation. Numeric WISECP limits override the preset; blank or unlimited values retain its defaults.

Creation applies the preset and creates the account with web and mail domain names. Presets do not import products or prices. Match a saleable **Shell (SSH) Access** addon explicitly; its activation enables shell access, suspension or cancellation disables it. The PHP Version requirement can be mapped, but account creation does not apply its response; set PHP through the hosting tool.

### Linking Existing Accounts

The list excludes the www-root system account and matches each username to its first web domain. If domain lookup fails, the username can appear instead. Verify the domain and preset before importing; passwords are not retrieved.

On the saved server, click **Import → List Results**. Select accounts and map their client, product, cycle and dates. Click **Import** below the list; verify the existing account appears in **Linked Services** without being recreated.

### Managing the Service

Create, suspend, reactivate, terminate and change account passwords from service management. In **Management → Settings → Package (Preset)**, select a preset and click **Save Changes**; it updates the existing account. Product upgrades also apply numeric resource overrides. Individual limit changes and resetting supported overrides are available.

Administrators and customers open permitted hosting tools from the service’s **Management** tab. Tools disabled in server **Preferences** are hidden. See [Service Management](https://docs.wisecp.com/en/service-management) for action dialogs.

FTP management has no per-account quota. File management supports browsing and file actions, but not upload. Databases and users, DNS records, mailboxes, forwarders, webmail, PHP versions and cron jobs are available. Addon domains and subdomains can be added or deleted; their edit action is unavailable. SSL supports Let’s Encrypt, custom and self-signed certificates.

Customer panel access uses a one-time session key. Root panel access also uses a session key and requires the separate root-login permission.

Disk, traffic, mailbox, database, subdomain and addon-domain metrics can be collected periodically. Disk usage sums databases and mailboxes; website files are excluded. Failed detail reads can report zero, so compare figures with the panel before enabling usage charges. Positive disk/traffic metric maxima change panel quotas; disabling metrics restores the configured limits or preset.

Before enabling automatic setup, compare **Management → Overview** with the panel on an existing test service. Plan selection does not periodically synchronize a product catalog or provider prices.

## Important Notes

> **Account Changes**
> 
> Termination deletes the account and its data. Preset changes, shell addons and metric settings change the remote account. Usage billing can add charges; verify quotas and usage before enabling it.

## 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](https://docs.wisecp.com/en/adding-a-server)
- [Product Automation](https://docs.wisecp.com/en/product-automation)
- [Server Groups](https://docs.wisecp.com/en/managing-server-groups)