PanelAlpha

38 vues Markdown

Connect PanelAlpha to WISECP to track WordPress hosting customers, service plans and usage from one service record.

Accessing the Screen

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

Before You Start

In PanelAlpha administration, obtain an administrator token through Configuration → Admins → Enable API Token. Access to plans, users, user services and usage information is required. The PanelAlpha API documentation explains authentication.

One WISECP service maps to one PanelAlpha user and their plan-based service. Creation requires the customer’s email address and a valid plan. Create WordPress sites and manage site features inside PanelAlpha.

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

Connection and Product Settings

Address / HostnameBoth required. Enter the panel domain without a URL path in Address. The port is 443 with SSL or 80 without SSL.
API TokenRequired. Enter the administrator token here. The current server form also requires nonempty Username and Password fields; the API connection uses the token.
Verify SSL CertificateEnabled for new records. Keep SSL and certificate verification enabled. Use Custom Port selects a different port.
Identity and CapacityMonthly Cost starts at zero; choose its currency. Maximum Accounts defaults to 200 when blank. The occupancy alert follows this limit. Nameservers accepts four lines.
PlanRequired for creation. Select its name under product Automation → Module Configuration; the matching panel plan is resolved during the action. Selection fills disk and traffic limits.

Tasks

Connecting the Server

  1. Complete Connection Details and click Test Connection.
  2. The test reads the plan list. Success does not prove user creation, site access or deletion permissions.
  3. Complete Identity and Capacity, then click Add New Server; verify the record in the list. Existing records use Save Changes.

Mapping a Product

  1. In the hosting product, select PanelAlpha under Automation → Module Assignment.
  2. Choose Single Server or Server Group under Server Configuration. Set Module Configuration → Plan.
  3. Check Resource Limits and prices. Keep the first product hidden with Automatic Setup disabled.
  4. Click Save Changes; verify the server and plan mapping.

Disk and traffic limits use MB; missing, zero or negative values appear unlimited. Shared email, FTP and database limits have no matching plan settings. Do not confuse per-site panel quotas with a user’s aggregate usage.

Provisioning creates the user, then their plan-based service; it does not automatically create a WordPress site. A failed second step can leave the user created. A retry can reuse the stored user and their first existing service. Check the target first when a user has multiple services.

Linking Existing Accounts

On the saved server, click Import → List Results. Email shows the email address; User ID shows the PanelAlpha user identifier. Matching uses the user identifier; the displayed email is not a website domain.

Select accounts and map their client, product, cycle and dates. Click Import below the list; check the user and plan under Linked Services. The list supplies neither passwords nor plans; a connection error can also produce an empty list.

Managing the Service

Suspension and reactivation affect the linked PanelAlpha service. Password changes update the user account. Change Management → Settings → Plan, then click Save Changes; verify the plan in the panel. Product upgrades also change the linked service’s plan.

Administrators and customers can open the panel login link from Management. It requests an automatic login token; without suitable login information, it returns the normal panel address. WISECP provides no file, FTP, email, database, DNS, cron, SSL or PHP tools here; manage them in PanelAlpha.

Management → Overview shows disk, account email, status, creation date, WordPress instances and remote backups. Usage is aggregated across the user’s sites. Disk, traffic, WordPress count and remote backup size metrics are available; usage billing also requires product settings and prices.

Usage connection errors can display zero; compare values and units with the panel before the first invoice. Plan selection does not periodically synchronize prices or create addons and order requirements. Before enabling automatic setup, verify the user, plan and panel access on an existing test service.

Important Notes

Termination Scope

Termination deletes the PanelAlpha user, affecting their services and sites as well as the linked service. Take a backup first. Do not assign other services belonging to that user to separate customers.

Required Permissions

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

Cet article vous a-t-il été utile ?

Merci pour votre retour !

Besoin d'aide supplémentaire ?

Notre équipe d'assistance est disponible 24h/24 pour tout ce que vous ne trouvez pas ci-dessus.