What to do if replication agent is installed, but the machine doesn't appear in ACP

Replication agent is installed, but the machine doesn't appear in ACP

Challenge

A replication agent is installed, but the machine is not discovered in Acura.

Solution

1) If a new agent is installed on the machine that has been discovered in Acura before, configuration files from the previous installation might be still in use as long as they are 
not removed during agent's deletion. 

      To avoid this, delete the following folders manually.
For Windows Replication Agent:
C:\ProgramData\Hystax
If you can't see this folder, make sure that hidden files and folders are displayed.
After that you can install the agent. 

For Linux Replication Agent:
sudo rm -rf /etc/hystax
After that you can install the agent.

2) If this is the first time a replication agent is installed on the machine, and it is not shown in Acura Control Panel:
  1.    Make sure that the Security group that Acura instance belongs to, allows all traffic for port tcp/443.
  2.    It is also recommended to allow traffic for udp/12201 as this port is used by the logging service to send data.
  3.    Firewall on the source machine must be disabled to ensure there is nothing that blocks outgoing traffic.

3) A machine might not be discovered in ACP due to an outdated SSL certificate in the replication agent's config file which doesn't match the one used by Acura.