Troubleshooting Integration Controller issues

For information about the Integration Controller installation and usage, see Installing and setting up the connector development environment and Installing and configuring sites to run on-premises connectors.

If you experience any issues with Integration Controller, refer to the following information for troubleshooting.

Common Integration Controller issues

The following table lists issues that might occur while installing and using Integration Controller, and corresponding corrective actions to fix these issues.

IssueCorrective action
Unable to install Docker Engine

Upgrade the operating system. For more information about the system requirements for Integration Controller, see Installing and setting up the connector development environment.

Docker Compose fails to pull or start containers

Verify the Docker Engine and Docker Compose versions. For more information, see Installing and setting up the connector development environment.

Cannot connect to BMC Helix Integration Service from an on-premises network that is behind a proxy. Docker login fails during installation with the following error message:

Error response from daemon: Get dial tcp getsockopt: connection refused

  1. Follow the instructions outlined in the Docker HTTP/HTTPS proxy documentation .
  2. Create an https-proxy.conf file at /etc/systemd/system/docker.service.d/https-proxy.conf with your proxy configuration.

The site goes offline, even though Integration Controller is installed and the same site was previously onlineRestart Docker from your installation directory. Alternatively, use the validation utility to determine if the environment is set up correctly. For more information, see Validating the connector development environment.

To access Integration Controller logs

For more information about the errors that might occur during Integration Controller usage, you can check the Integration Controller logs. To access them, perform the following actions:

  1. On the server where Integration Controller is installed, run the following command: docker ps 
    The list of all docker containers is displayed.
  2. Access the logs of a particular container by using the container name or the container ID, and running one of the following commands: 

    docker logs container_name


    docker logs container_ID

    The logs of the specified container are displayed.


    For more information about the Docker logs processing, see  the official Docker documentation .

Was this page helpful? Yes No Submitting... Thank you


  1. Iassen Manov

    With latest versions the installation goes to the point when possibly docker login fails with the message:

    Error response from daemon: Get dial tcp getsockopt: connection refused

    The below topic suggests that it might be due to SSL certificate problems:

    However, the connection is still unsuccessful

    and indeed

    Oct 19, 2017 11:32
    1. Iassen Manov

      Solved: When connecting from on-premise network behind proxy follow the instructions here:

      and create a file /etc/systemd/system/docker.service.d/https-proxy.conf with correct proxy configuration

      Oct 23, 2017 07:04
      1. Tashfeen Mahmud

        Thanks for finding the solution, Iassen. We will update the content soon And sorry again for the (very) late reply, strangely enough we didn't get automatic notifications for your comments like we usually do (something we're looking into).

        Apr 05, 2018 01:52
  2. Iassen Manov

    Problem 2: Controller Installation succeeded but Status is shown as Not Installed under Sites

    panama-monitor@0.1.3 heartbeat /opt/panama-monitor node lib/heartbeat

    Queue connection established. Component: panama-flowengine last heartbeat @ 2017-10-23T13:12:23.954Z

    Oct 23, 2017 08:43
    1. Tashfeen Mahmud

      Hi Iassen, somehow your comments slipped under our radar – we sincerely apologize. Do you still have problem 2? Please let us know. Sorry for the delay again.

      Jan 22, 2018 03:35