Skip this step if the server in question is not in AWS: If your Enterprise Console host is running on an EC2 instance in AWS, and the public hostname changed as a result of reboot, then validate from either AWS console or AWS CLI. This could be the case if the EIP was not attached on the EC2 instance.
What is the result after executing the below commands?
If I don’t uncover the cause with this trouble-shooting, what are the next steps?
If you complete the preceding steps and the results were all positive, with no issues observed, then the network that connects your workstation and the Enterprise Console needs an in-house inspection from your network or Unix team.
It will help continued troubleshooting if you capture some additional detail by executing the following commands to stop and then start the EC using bash -x.