Plesk
There are two Plesk modules in WHMCS. "Plesk" and "Plesk Reseller". The latter is needed if you only have a reseller account on Plesk. The former is used when you have full admin access and can therefore create client accounts. Important to note you do not select the module based on what type of package you are trying to create.
Contents
- 1 Setting Up a Plesk Server
- 2 Setting Up a Plesk Package
- 3 Common Problems
- 3.1 The client account is getting setup but the domain is not
- 3.2 I get a blank command error from WHMCS when it tries to setup an account
- 3.3 1013 - Account Creation Failed: template does not exist
- 3.4 1014 - Parser error: Request is invalid
- 3.5 2306 - Domain adding was failed. Error: xxxxx template failed: Unable to apply limits
- 3.6 With accounts created on my Plesk server from WHMCS the www. subdomain doesn't work
Setting Up a Plesk Server
The following steps guide you through the process of setting up a server in WHMCS for Plesk Hosting Accounts.
1. Begin by going to Configuration > Manage Servers
2. Click Add New Server
3. Enter the server name, IP address, select the server type "plesk" if you have admin access or "pleskreseller" if you are only a plesk reseller, and enter the username and password as appropriate
4. Click Create Server to complete the process and add your new server
Setting Up a Plesk Package
To setup a package for your Plesk server, go to Configuration > Products/Services, proceed to the new product setup and enter the details such as name, pricing, etc... On the server settings tab you should do the following:
1. Set the Server Type to Plesk or Pleskreseller depending on what you used previously
2. Enter the Client Template and Domain Template names - these are setup directly in Plesk and allow you the full flexibility over client and domain permissions.
Common Problems
The client account is getting setup but the domain is not
This is usually due to the permissions of the domain template exceeding the server resources or containing something such as ColdFusion support when the server doesn't support it. You should always test your domain template works directly in Plesk after setting it up if it is a new setup.
I get a blank command error from WHMCS when it tries to setup an account
This happens when an account already exists for the user in Plesk or if your firewall is blocking outbound connection to port 8443. Plesk only allows a name to be used once "FirstName LastName" so if you try to add another order for a user with the same name which wasn't ordered through WHMCS originally (so WHMCS doesn't know about it) then it results in an error. As long as the original order was placed through WHMCS for that user, it should work fine.
1013 - Account Creation Failed: template does not exist
This error message is coming direct from the Plesk API. When configuring the product, you have to enter the client and domain template names. These are currently incorrect so you will need to correct them in Config > Products & Services on the Modules Settings tab
1014 - Parser error: Request is invalid
This error message indicates there is a field value missing - this can be a clients profile field or something such as no available IPs in the clients IP pool.
2306 - Domain adding was failed. Error: xxxxx template failed: Unable to apply limits
This error message comes direct from the Plesk API. It means that the template you are attempting to use exceeds your limits or has a feature your server doesn't support. You should try creating an account with the template inside Plesk itself as then you get more details about the problem.
With accounts created on my Plesk server from WHMCS the www. subdomain doesn't work
This happens due to the default DNS settings on a Plesk server and the requirement to tick a box when creating an account to enable it. To avoid that, simply follow the steps below.
- Login to Plesk
- Click "Server"
- Click "DNS Settings"
- Click "Add New Record"
- Choose "CNAME" under record type
- Enter "www" in "Enter Domain Name"
- Enter "<domain>" in "Enter Canonical Name"
- Hit OK to complete the changes
Server Modules
cPanel/WHM - DirectAdmin - Plesk - Helm 3 - Helm 4 - Ensim - InterWorx - WebsitePanel - Cloudmin
Lxadmin - Virtualmin Pro - XPanel - HyperVM - SolusVM - Cloudmin - WHMSonic - VPS.Net
CentovaCast - SCPanel - MediaCP - GameCP - TCAdmin - Reseller Central - Auto Release - Heart Internet
Registrar Modules
Enom - ResellerClub - Nominet - OpenSRS - ResellOne - OnlineNIC - PlanetDomain - Affordable Domains
TPP Wholesale - TPPInternet - Stargate - Namecheap - NetEarthOne - Bizcn - InternetBS - GMO Internet
12Register - Registercom - DotDNS - WebNIC - Dot.TK - HexoNet - Realtime Register - Registereu
RRPProxy - ResellerCamp - TransIP - Heart Internet - IPMirror - NetRegistry - OVH - VentraIP Wholesale
Email - 101Domain
Fraud Modules
MaxMind - VariLogiX FraudCall - Telesign
Gateway Modules
2CheckOut - AsiaPay - Auth.net Echeck - Authorize.net - Authorize.net CIM - Bank Transfer - BidPay
BluePay - BluePay Echeck - BluePay Remote - Boleto - CashU - CC Avenue - ChronoPay - Direct Debit
EMatters - E-Path - eProcessingNetwork - eWAY Tokens - F2B - Finansbank - GarantiBank - Gate2Shop
Inpay - InternetSecure - IP.Pay - Kuveytturk - Modulo Moip - Mail In Payment - Merchant Partners
Merchant Warrior - IDEALMollie - Moneris - Moneris Vault - Skrill 1-Tap - NaviGate - NETbilling
Netregistry Pay - NoChex - Offline Credit Card - Optimal Payments - PagSeguro - Payflow Pro - Pay Junction
Paymate AU and NZ - Payment Express - PayPal - PayPal Card Payments - PayPal Express Checkout
PayPal Payments - PayPal Payments Pro - PayPoint.net (SecPay) - Payson - Planet Authorize - ProtX VSP Form
PSIGate - Quantum Gateway - Quantum Vault - SagePay - SagePay Tokens v2 - SecurePay
SecurePay AU - Secure Trading - TrustCommerce - USA ePay - WorldPay - WorldPay Invisible