Search Engine: Elastic

Article ID: 121822, created on May 30, 2014, last review on May 30, 2014

  • Applies to:
  • Operations Automation 5.4


All MX Logic related tasks fail with an error like below:

Task name   MX Logic: Update EDS product (subscription_id = 10112451, quantity = 5)
Output  SOAP Error: Client, EOF was observed that violates the protocol. The client probably provided invalid authentication information.: SSL connect failed in tcp_connect().


POA uses a Privacy Proxy server to access hosts in external network. This includes the MX Logic API endpoint The error like in the task above may come from the fact that IP that Privacy Proxy server uses to connect to is rejected on MX Logic side.


There is currently no way to explicitly define which IP the Privacy Proxy server will use for connecting to external network servers, but a request to improve on this functionality is already submitted - ID POA-75053.

To resolve this issue, you need to clarify with MX Logic what IP do they expect you to connect from and add it to the routing rules on the Privacy Proxy server:

[root@proxy ~]# ip route add dev venet0 scope link src

where venet0 is the interface that is used to connect and is the IP that should be used. Be sure to also add it to the corresponding networking script, so it will survive any server reboots:

[root@proxy ~]# grep /etc/sysconfig/network-scripts/route-venet0 dev venet0 scope link src

ac82ce33439a9c1feec4ff4f2f638899 caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae 2554725ed606193dd9bbce21365bed4e e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF