Communication error on

I've trying to connect to my apps, but I got this error message:

Server was unable to process request ---> No connection could be made because the target machine actively refused it

How can I resolve this issue?


Same for me. On <personal_environment>/LifeTimeCloudConnect I've got a warning:

Synchronization Problems  Retry Synchronization

  •  Environment Development (2 hours ago): System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it

    Server stack trace:
       at System.Net.Sockets.Socket.Connect(IPAddress[] addresses, Int32 port)
       at System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket(AddressFamily family)
       at System.Runtime.Remoting.Channels.SocketCache.GetSocket(String machinePortAndSid, Boolean openN (...)
  •  Environment Development (09:36): There was a communication problem between 'Development' and LifeTime

And I can't connect to ServiceCenter


you can try to click on Retry Synchonization and try to connect to Env. again after few minutes. If not connected yet, repeat steps.

Hi Irham and Aliaksandr,

Have you tried to contact the OutSystems support team already? If not, please do so that we can help with troubleshooting this.


Hi Vera,

Yes. I opened a support case, but while I had a lunch, everything was fixed, and now I have no warnings in LlifeTime, I can connect to ServiceCenter and can connect from Service Studio.

This exception message says you're trying to connect to the same host ( ), while you're stating that your server is running on a different host. This represents a 'loopback' . It allows the computer to communicate with itself via network protocol .

Dns.GetHostEntry(IPAddress.Loopback).HostName returns the host name of your machine. When you pass a host name to TcpClient , it will resolve it to one or more IP addresses using Dns.GetHostAddresses(hostName) . This includes the public and local IP addresses of your machine (e.g., but not (loopback address). So your client is trying to connect to any of the non-loopback addresses of your machine, while your server is listening only on the loopback address . So, no connection can be established. The solution to this problem is that connect to the same end point your server is listening on.