• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

WHMCS 5.2.2 + Plesk 11.0.9: Unable to Accept Orders

Eric Pretorious

Regular Pleskian
When I manually accept the order (in WHMCS) (i.e., to "Automatically setup the product [in Plesk] when you manually accept a pending order") nginx reports this error:

Code:
502 Bad Gateway
nginx

Reloading the page displays the order along with an error - usually something like...

Order Accept Encountered Problems
Error Code: 1007 - Domain example.com already exists.

The order status (in WHMCS) has not changed but the client and the subscription has been created in the Plesk control panel.

Another user believes that the error is caused by Plesk restarting Apache:

The problem is caused by the WHMCS script trying to load the confirmation page at the exact second that apache is down while restarting. (Plesk always restarts apache after [adding] a domain).

Apache's log file (/var/log/httpd/error_log) confirms that Apache is restarted almost immediately after WHMCS begins the process of setting up the product in Plesk:

Code:
[Sat Mar 30 05:43:49 2013] [notice] caught SIGTERM, shutting down

Could the problem actually be caused by WHMCS being killed [by Apache restarting] while it's waiting for Plesk's confirmation?
 
Back
Top