A cloned replica is not reachable after network change

[CarlosGaviria]

Hello,

We cloned the primary and the replica instances in order to build a Laboratory environment. We changed the network configuration of the primary and works, but even if we changed the network configuration in the replica and respond ping, we can´t access the replica through the HTTPS link. We suspect the problem is that the connection between the replica and the primary can´t be done because the change of the FQDN in the primary instance, but we are not sure. Please help us.

[EdwardDavis · Accepted solution]

You'll likely need to open a support case for this, to dig into the situation. Https connection to the replica has nothing to do with it's ability to reach the primary or any other system. Web browser access to any one RSA Authentication Manager is handled directly by that machine and doesn't hinge on any other RSA servers being in the picture. Your issue lies on investigating the running services, and log files from the command line in /opt/rsa/am/server/logs directory.