# CyberPanel https://docs.wisecp.com/en/cyberpanel Connect CyberPanel to manage hosting websites and offer clients hosting tools inside WISECP. ## Opening the Screen Open **Products → Hosting & Servers → Server Settings → Add New Server**. Under **Server Automation Module → Web Hosting**, select **CyberPanel**. `{admin}/products/servers-add`. To edit a server, click its name in Server Settings. ## Before You Connect Use a CyberPanel administrator account. In CyberPanel, open **User → API Access**, select that user and **Enable**, then click **Save Changes**. Permit access from your WISECP server to the panel port. Client tools also require CyberPanel cloud API access. [CyberPanel API instructions](https://cyberpanel.net/KnowledgeBase/home/cyberpanel-api-access-2/). Prepare an active WISECP server record and a Hosting product. Create website packages in CyberPanel first. This module does not import provider prices; set product prices and billing currency in WISECP. ## Connection and Product Settings - **Address / Hostname**: Required. Enter a reachable panel host without a URL path. CyberPanel uses Hostname before Address. Both module port defaults are 8090. - **Username / Password**: Required. Use the administrator credentials with API access. This module has no separate API Token field. Keep password dots unchanged when editing. - **Verify SSL Certificate**: On for new records. Keep HTTPS and certificate verification enabled. Use Custom Port enables a different panel port. - **Identity and Capacity**: Monthly Cost starts at zero; choose its currency. Empty Maximum Accounts becomes 200. Occupancy alerts use that limit. Nameservers accepts four lines. ### Module Configuration The product’s **Automation → Module Configuration** section shows these controls after selecting the server. - **Package**: Select an existing website package by name. Opening the selector loads CyberPanel packages. An empty list can indicate an API failure. - **Reseller Account**: Off by default. Enable it to create an administrator/reseller account instead of a website; the website package does not control this account. - **Reseller ACL**: Appears for reseller accounts. Default: Reseller. User and Admin are also available; Admin grants broad panel access. - **Website Limit / Security Level**: Reseller controls. Defaults: 10 websites and High security; Low is available. ## Tasks ### Connect the Server 1. Complete **Connection Details**, then click **Test Connection** in the server summary. 2. Confirm the connection result. This checks credentials, not website creation or every cloud API tool. 3. Complete **Identity and Capacity** and click **Add New Server**. Confirm the new list entry; editing uses **Save Changes**. ### Map a Hosting Product 1. Open the Hosting product’s **Automation** tab and choose **CyberPanel** under **Module Assignment**. 2. In **Server Configuration**, choose **Single Server** or **Server Group**. Group members need matching website package names. 3. Complete **Module Configuration**. Website packages apply their own limits; selecting one does not import prices or fill WISECP resource limits. 4. Keep the initial product hidden with **Automatic Setup** off. Click **Save Changes**, reopen Automation and verify the selections. In the product’s **Requirements** tab, map **PHP Version** for website creation; the module fallback is PHP 8.0. Select a version installed on CyberPanel. No saleable requirement or add-on is created automatically, and this module has no add-on mappings. ### Import Existing Websites 1. Open the saved server’s **Import** tab and click **List Results**. The list contains websites and packages, not reseller accounts. 2. Select websites and assign their client, product, billing cycle and dates. Existing domain matches prevent duplicate service links. 3. Click **Import** below the list, then check **Linked Services**. This links existing websites without creating them again. ### Manage Services and Tools Open a service’s **Management → Overview** for actions and tools, or **Management → Settings** to change its website package. Reseller ACL and Website Limit are displayed without editing. [Service Management](https://docs.wisecp.com/en/service-management) describes the action windows and confirmations. Website actions include creation, suspension, reactivation, termination, password and package changes. Reseller suspension/reactivation does not change CyberPanel; reseller package upgrades are unsupported. Website panel sign-in uses the account credentials; reseller sign-in opens the panel login page. Under the saved server’s **Preferences → Client Area Preferences**, choose tools and click **Save Changes**. Service Preferences and product restrictions also apply. Clients open their service’s **Management** tab. Tools: FTP Accounts, Databases, Email Accounts, DNS Zone Editor, Addon Domains and Subdomains. FTP supports create/delete, without quota or custom directory. Database users are paired with databases; separate user/privilege controls are unavailable. Email supports create/delete/password changes without quota. DNS and domain tools support create/delete, without editing or custom subdomain roots. The overview shows account information, without usage gauges or usage billing. There is no automatic package-price synchronization. Check an existing test service’s details and enabled tools before allowing automatic setup. ## Things to Watch > **Data and Access** > > Termination deletes the website or reseller account. Keep an independent backup. Do not rely on WISECP suspension to disable reseller access. Hosting and optional CyberPanel services can incur provider charges. ## Required Privileges Server settings require **MODULES_SERVERS_SETTINGS**; product changes require **PRODUCTS_OPERATION**. Administrator panel sign-in requires **MODULES_ROOT_LOGIN_BUTTON**. Service actions require their corresponding service privileges. ## 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)