Search Engine: Elastic

Article ID: 116018, created on Apr 26, 2013, last review on May 8, 2014

  • Applies to:
  • Operations Automation


A customer cannot install WPB connector application on their domain in POA Control Panel, corresponding APS task fails with the error message 'Unable to connect to ssl:// Error #111: Connection refused', more detailed diagnostics is provided below:
Script execution failed: executing '/var/www/cgi-bin/php5/php -d open_basedir= -q configure.php' for APS application instance with id 1315 returned value '1' with output
'<?xml version="1.1" encoding="utf-8"?>
<output xmlns=""><errors><error><message>Internal SiteBuilder error.</message>
<system>Zend_Http_Client_Adapter_Exception: Unable to Connect to ssl:// Error #111: Connection refused
file: /var/www/vhosts/1/101247/webspace/httpdocs/
line: 148 code: 0
trace: #0 /var/www/vhosts/1/101247/webspace/httpdocs/ Zend_Http_Client_Adapter_Socket-&gt;connect('', 443, true)
#1 /var/www/vhosts/1/101247/webspace/httpdocs/ Zend_Http_Client-&gt;request()
#2 /var/www/vhosts/1/101247/webspace/httpdocs/ SB_Aps_Configurator-&gt;_requestToRestApi()
#3 /var/www/vhosts/1/101247/webspace/httpdocs/ SB_Aps_Configurator-&gt;_installCommand()
#4 /var/www/vhosts/1/101247/webspace/siteapps/ParallelsWebPresenceBuilder-1315/scripts/configure.php(90): SB_Aps_Configurator_Abstract-&gt;run()
#5 {main}
</system></error></errors></output>' and errors ''.


Configuration scripts from WPB APS application being installed in a customer's webspace cannot connect to the 'centralized' WPB instance, connection protocol and host are present in the error message shown in the failed task properties:

  • Protocol - SSL
  • Host -


1. Log into the server where customer's webspace is located, webspace ID is shown in the failed POA task.

2. Check if connection may be established to the target host and port, e.g. using the telnet utility: telnet 443
3. If connection cannot be installed then perform the following actions:

  • Check if Apache server is running on the target host (
  • Check if Apache server is listening to the port 443 on the target host
  • Check if the host resolves to the correct IP address on the host where a customer's webspace is located
  • Check firewall and routing settings and make sure connection from the server where a customer's webspace is located to the server where centralized instance of WPB is installed is allowed

4. After the problem with connectivity is solved re-run the failed task in POA Task Manager

caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF