https://docs.whmcs.com/9-1/tags/provisioning/Recent content in provisioning onHugo -- gohugo.iohttps://docs.whmcs.com/9-1/troubleshooting/troubleshoot-servers/troubleshooting-server-issues/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-servers/troubleshooting-server-issues/Index page covering general provisioning troubleshooting steps using the Module Queue, Module Log, and cron status, and linking to cPanel & WHM, Plesk, and WP Squared server module issue articles.https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-servers/406-not-acceptable-errors/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-servers/406-not-acceptable-errors/Documents the “406 Not Acceptable” provisioning error caused by the server’s mod_security rules blocking WHMCS requests, with the fix of checking the mod_security log for the triggered rule.https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-servers/account-creation-failures/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-servers/account-creation-failures/Explains hosting account creation failures during provisioning, shown as Pending Module Actions in the Module Queue, with troubleshooting and retry steps based on the Module Queue error message.https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-php/allowed-memory-exhausted-errors/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-php/allowed-memory-exhausted-errors/Documents the “Allowed memory size of xxxxx bytes exhausted” PHP error, explains it is caused by the server’s memory_limit setting, and gives steps to check PHP Info and increase memory_limit.https://docs.whmcs.com/9-1/troubleshooting/general-troubleshooting/curl-couldnt-connect-to-host-errors/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/general-troubleshooting/curl-couldnt-connect-to-host-errors/Addresses “Curl Error - Couldn’t connect to host (7)” and “Curl Error: Connection refused - Code 7” messages caused by a firewall blocking port 443 or an IP address not whitelisted with the domain registrar, with fixes to open inbound/outbound ports and whitelist the WHMCS server IP found under License Information for the domain sync task.https://docs.whmcs.com/9-1/troubleshooting/general-troubleshooting/curl-couldnt-resolve-host-errors/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/general-troubleshooting/curl-couldnt-resolve-host-errors/Covers “Curl Error - Couldn’t resolve host (6)” and the server command variant, caused by DNS failing to resolve the WHMCS licensing server or a product lacking an associated hosting server, with checks of the server/server group settings under Products/Services and Servers plus DNS and zone file verification.https://docs.whmcs.com/9-1/troubleshooting/general-troubleshooting/curl-timeout-errors/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/general-troubleshooting/curl-timeout-errors/Covers “Curl Error - 28 connect() timed out” and “cURL error 28: Operation timed out” during server provisioning (busy server, 150-second provisioning limit, IP mismatch) or the Automatic Updater downloading from releases.whmcs.com, with fixes for firewalls, SSL mode under Servers settings, and retrying updates via the browser or command line.https://docs.whmcs.com/9-1/addon-modules/webpros-partner/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/addon-modules/webpros-partner/Details activation, product setup, ordering/provisioning, and client-area management for the WebPros Partner addon module’s cPanel license and WebPros Cloud services such as WHMCS Cloud, Nova, WP Squared Cloud, and Riva, including license/group/package management, autoscaling, and the Product Configuration Drift banner.https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-addon-modules/webpros-partner/webpros-partner-provisioning-errors/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-addon-modules/webpros-partner/webpros-partner-provisioning-errors/Lists causes of the WebPros Partner “Provisioning Error: This service is not provisioned yet” message (License Package mismatch, insufficient Manage2 permissions, or exceeded license quota), with fix steps: check the Module Log, match Service Type and License Package, then click Refresh License Status.